Skip to content
ChangeBoth sidesTemplate

Project Change Request Template

Use this when a request may add, remove, exchange, or defer work covered by an existing project. First decide whether the request is a correction under the agreement or genuinely changed scope.

Source: assistedfreelance.com/templates/project-change-request

Context and limits

Before you use it

  • Reference the accepted scope and quote the relevant baseline accurately.
  • Do not begin changed work until the agreement’s required approval step is complete.
  • A change can affect dependencies and acceptance criteria even when its immediate fee is zero.

Blank reusable version

Copy, edit, and verify.

Project Change Request

Project and original scope reference

[Project name, agreement/SOW reference, date, and relevant original scope.]

Requested change

[Describe the request in neutral, concrete terms.]

Reason for the request

[Business, user, technical, or scheduling context.]

Work added, removed, exchanged, or deferred

Added: [work] Removed: [work] Exchanged or deferred: [work]

Price and expense impact

[Added credit or fee, currency, expenses, invoice/payment trigger, or no-price-impact explanation.]

Schedule impact

[Changed milestones, delivery date, review window, or no-impact explanation.]

Dependency and responsibility impact

[New content, access, people, decisions, third parties, or risks.]

Acceptance impact

[New or changed deliverables, tests, approver, and acceptance criteria.]

Decision

[Approve / decline / revise / defer, plus any conditions.]

Approval and effective date

[Authorized names, roles, approval method, date, and when changed work may begin.]

Completed fictional example

Two additional bakery landing pages

Use this to understand the level of specificity, not as facts, pricing, tax treatment, or agreement wording for your project.

Project Change Request — HSB-WEB-01-CR02

Fictional educational example · approved November 7, 2026

Original scope reference

Harbor Street Bakery website, SOW HSB-WEB-01. The original scope contains five responsive pages; campaign landing pages are excluded.

Requested and approved change

Add Wedding Catering and Corporate Catering responsive landing pages using the approved visual system. Added work includes two layouts, build, supplied-content entry, navigation links, and agreed checks. No original work is removed or exchanged.

Reason

The bakery decided to give two catering audiences separate entry points after the original site structure and design direction were approved.

Price and payment impact

Additional fixed fee: $1,200 USD. $600 is triggered by written change approval; $600 is included in the final invoice after the two pages pass their acceptance checks. These are fictional figures.

Schedule impact

The target launch moves from November 21 to December 2, 2026, provided Sam supplies approved copy and images by November 8 and consolidated feedback within three business days.

Responsibilities and acceptance

Sam supplies approved copy and images. Jordan confirms whether existing licensed assets cover the added use. Both pages must use approved content, link from the agreed navigation, pass the project’s mobile, desktop, keyboard, browser, and accessibility checks, and route inquiry links correctly.

Decision

Sam and Jordan approve CR02 through the agreement’s recorded approval method on November 7. Added work begins after approval and the first $600 payment trigger. All unchanged SOW terms continue.

Field by field

Adapt it deliberately

Baseline
Identify the exact scope or requirement being changed so the comparison is traceable.
Changed work
List added, removed, exchanged, and deferred items rather than recording only the new request.
Price and schedule
Show credits, fees, expenses, milestones, and dependency-driven date changes.
Responsibilities
Name new inputs, access, approvals, and third-party decisions.
Acceptance
Update observable checks to match the changed result.
Authority
Follow the actual agreement’s approval method and state when work may begin.

Important considerations

Common mistakes

  • Do not use a change request to charge for correcting work that already fails the accepted criteria.
  • Do not describe only the fee; record schedule, responsibility, and acceptance effects as well.
  • Do not treat silence or an informal suggestion as approval when the agreement requires something else.