Write a change request when scope changes

Project: {{project_name}}
The change being requested: {{change_description}}
Requested by, and when: {{requested_by}}
Why they want it: {{reason}}
Who approves changes: {{approver}}
My recommendation: {{recommendation}}

Current agreed plan (scope, key dates, budget, contingency left):
"""
{{baseline}}
"""

What the team has estimated about the impact so far:
"""
{{impact_notes}}
"""

Task:
Write a change request that documents this change and its effect on time, cost and scope, so that {{approver}} can approve, reject or defer it from one page without a meeting.

Use these headings:
Change request: a short title, the requester and the date.
What is being asked: two or three sentences in plain words.
Why: the reason and the benefit, as the requester describes them.
Impact: one line each for scope, schedule (which dates move and by how much), cost (amounts, and how much contingency would remain), people and workload, quality and risk, and other projects or teams affected.
Options: at least approve, reject and defer, plus a partial option if the notes suggest one, each with its consequence. Rejecting has consequences too; say what they are.
Recommendation: mine, with its reason. If I gave none, write "No recommendation; for the approver to decide."
Decision needed by: the date, and what happens to the schedule if the decision comes later.
Approval: lines for the decision, name, signature and date.

Requirements:
- Under 500 words.
- Use only the estimates in my notes, and copy figures exactly. Where an impact has not been estimated, write "Not yet estimated" and who will estimate it, never zero or "minimal", because an unestimated impact is the one that causes trouble later.
- Keep the tone neutral. The document records the trade-off; it does not argue for or against the change outside the Recommendation.
- Show schedule changes as old date and new date, for example "Go-live: May 14 to June 4", so nobody has to work it out.

If the change is described vaguely enough that the team could estimate it in different ways, say so at the top and list the questions to put to the requester before it goes for approval.