Change Request Generator — illustrative example

INPUT
Approved site scope has three pages. Client requests a fourth FAQ page. Content, effort and delivery impact have not yet been estimated. Draft a change record.

RESULT
Baseline: three agreed pages.
Requested change: add one FAQ page.
New inputs needed: approved questions and answers, design requirements and acceptance criteria.
Impact to assess: content preparation, implementation, review effort and delivery date.
Decision required: approve the added scope and its estimated commercial and schedule effects before work begins.
Status: proposed; no approval or estimate is implied.

REVIEW
A change request should explain the baseline, requested difference and effect. Approval should cover the impact, not merely acknowledge the new idea.

This is a teaching example, not a live execution record.