PLAINREADS — CHANGE REQUEST FORM
Source: https://plainreads.com/blog/change-request-form

WORKING COPY
Project and request ID:
Requester and date:
Current approved baseline and link:
Proposed addition, removal, or replacement:
Reason and affected users:
Scope impact:
Effort estimate, estimator, and assumptions:
Calendar impact and dependencies:
Resources or cost needing approval:
Quality and acceptance checks:
Work displaced:
Alternatives, including keeping the baseline:
Decision and authorized decision-maker:
Decision date and conditions:
Implementation owner:
Verification owner and evidence:
Baseline, schedule, and communication updates:

FICTIONAL EXAMPLE — CR-04
Current: One English expense FAQ, six approved questions, Friday release.
Change: Add Spanish version and language-selection link.
Reason: Incoming colleagues would benefit from Spanish instructions.
Effort: Morgan estimates four additional hours coordinating adaptation/layout;
qualified reviewer estimates two hours checking policy wording. Total six
staff-hours, not six elapsed hours. Reviewer's slot is not yet confirmed.
Dependency: Lee confirms qualified reviewer and availability.
A: Keep Friday English release; separately schedule translation after review confirmation.
B: Release both together on a revised agreed date.
C: Retain baseline and record translation as a separate future request.
Decision: Casey approves A, conditional on Lee confirming reviewer.
Owner: Morgan updates plan and communicates separate release commitments.
Translated release date remains uncommitted until review availability is confirmed.
If the English-only release cannot serve its intended users, reassess Option A.

AFTER APPROVAL
- Preserve original commitment in change history.
- Update current baseline and working schedule.
- Confirm authority, capacity, dependencies, and verification.
- Tell affected people what changed and what did not.
- Record completed implementation separately from approval.