Change Request
Formally propose, assess, and disposition project changes with this structured request form template and worked example.
In this resource
§1 Purpose of the Change Request
The Change Request form is the formal mechanism for proposing modifications to any baselined project artefact, encompassing scope, schedule, cost, or quality requirements.
Before any adjustment to the project baseline can occur, a formal request must be articulated, assessed for impacts, and presented to the Change Control Board (CCB) or project sponsor. This form structures that articulation. It forces the requestor to justify the change and the project team to quantify its secondary effects before a decision is rendered.
§2 Blank Template
A standardized structure for capturing and assessing proposed changes, ready for use on active projects.
This form should be completed iteratively. The Requestor typically completes the description and justification, while the Project Manager or technical leads complete the impact assessment prior to the final disposition decision.
CHANGE REQUEST
Scope: ...
Requirements: ...
Cost: ...
Schedule: ...
Quality: ...]
§3 Worked Example: Mary's Consulting
A completed example demonstrating the assessment of a minor scope addition late in the project lifecycle.
This example details Change Request CR-008 from the "New Company Website" project. It illustrates how a seemingly small request (adding LinkedIn icons) must still be formally assessed for its compounding impacts on cost, requirements traceability, and team effort.
CHANGE REQUEST
Affects ~50 launch-tier consultant cards. Out of scope: any other social platforms; LinkedIn data scraping; sign-in-with-LinkedIn functionality.
Requirements: Adds F-08 LinkedIn-link display to RTM.
Cost: Estimated +$400 (Bob: 4 hrs frontend; Christine: 2 hrs to collect URLs from launch-tier consultants). Drawn from contingency.
Schedule: No critical-path impact. Work fits in existing build buffer.
Quality: No additional accessibility or performance concerns; LinkedIn icon is a well-understood pattern.
Defining Boundaries
Notice how the description explicitly states what is out of scope (scraping, SSO). This prevents the minor addition from spiralling into a major technical feature.
Holistic Impact
The impact assessment recognized that it wasn't just a 4-hour coding task for Bob; it also required 2 hours of administrative effort from Christine to gather the data.
Financial Traceability
The disposition records exactly where the $400 is coming from, ensuring the project contingency balance is accurate and traceable.
Handbook application: from concept to controlled practice
Purpose. This expanded section turns the original page into a practical handbook. It preserves the supplied material and adds a repeatable way to apply, check and review Change Request Form. It does not replace a contract, legislation, a controlled standard, competent engineering judgement or specialist advice.
The operating aim is to make the blank artefact usable by explaining what belongs in each field, who supplies it and how it is reviewed. Read the original explanation first, then use the workflow and checks below to convert knowledge into evidence.
Use Change Request Form as a decision instrument rather than an administrative form. The subject terms—change, request, template, example, form—need an explicit connection to the project objective, business value and stakeholder commitments. Before completing the artefact, write one sentence stating who will use it, what decision it supports and when that decision is required.
Apply a disciplined information model. Separate facts supported by evidence, forecasts derived from a method, assumptions awaiting validation, constraints that limit choice, risks that may occur, issues that already exist and actions assigned to people. Each material entry should have an owner, date, status and next review point. Where probability or impact scores are used, define the scale so different reviewers interpret it consistently.
A baseline is useful only when changes are visible. Give the artefact an identifier, version, approval state and effective date. Define which changes require reapproval, how superseded versions are retained and where supporting evidence is stored. During reviews, focus on exceptions, decisions and trends rather than reading every field aloud. Record the decision and rationale, not merely that a meeting occurred.
Close the loop beyond delivery. Confirm acceptance criteria, unresolved items, transferred responsibilities and operational ownership. Where benefits are expected, identify the outcome measure, baseline, target, observation period and owner who remains accountable after the project team disbands. Lessons should describe the condition, consequence and reusable action; a generic statement such as “communicate better” cannot improve the next project.
Step-by-step operating method
- Name the decision. Write the decision, approval, handover or control activity the completed template must support.
- Assign ownership. Nominate one accountable owner and identify contributors, reviewers and approvers.
- Gather evidence. Use records, estimates, stakeholder input and source references rather than unsupported opinion.
- Complete with discipline. Use consistent dates, units, identifiers, status values and version controls.
- Review and maintain. Check completeness and logic, approve the baseline, then update it when trigger conditions occur.
Completion and governance protocol
Start with a short drafting workshop involving the accountable owner and the people who hold the evidence. Complete high-consequence fields first: objective, scope, owner, baseline, acceptance, dependencies and escalation. Mark unknowns as assumptions or actions rather than hiding them behind vague prose. Circulate a review draft, resolve conflicting interpretations, baseline the approved version and place the next review date in an owned schedule.
| Information type | Minimum useful content | Review test |
|---|---|---|
| Outcome | Observable change and intended recipient | Not merely a deliverable or activity |
| Measure | Definition, baseline, target, frequency and source | Two reviewers would calculate it the same way |
| Ownership | One accountable role plus contributors and approver | Authority matches responsibility |
| Uncertainty | Assumption, risk or issue with response and trigger | Status reflects current reality |
| Control | Version, approval, review date and change rule | Current baseline is identifiable |
Common failure modes and recovery actions
1. Watch for
Filling every box even when a field is not applicable instead of recording why.
Recovery: Return to the governing definition or requirement and restate the decision in one sentence.
2. Watch for
Writing vague statements without an owner, measure, date or evidence source.
Recovery: Separate evidence from assumption, assign an owner and set a date for validation.
3. Watch for
Copying a previous project without revalidating assumptions and stakeholders.
Recovery: Run a small counterexample, boundary test, pilot or independent check before proceeding.
4. Watch for
Using the document as a private worksheet when it is meant to support a shared decision.
Recovery: Record the consequence, decision and rationale, then update the controlled baseline.
5. Watch for
Creating an approved baseline but failing to define who maintains it and when.
Recovery: Escalate when the issue affects safety, compliance, acceptance, material value or an agreed tolerance.
Review checklist
- Is the purpose and intended decision clear to a reader outside the team?
- Are owners, dates, measures and sources complete and internally consistent?
- Which fields are assumptions and how will they be validated?
- What event, threshold or review date causes this document to change?
- Are mandatory requirements distinguished from recommendations and illustrative values?
- Are sources, assumptions, units, dates and versions recorded closely enough to reproduce the decision?
- Have safety, legal, ethical, stakeholder and operational consequences been considered at the appropriate level?
- Is there a named owner and a trigger for review, escalation, change or retirement?
Questions for deeper application
What is the most important distinction a practitioner must preserve when applying Change Request Form?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
Which assumption about change would change the result most if it proved false?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
What evidence would allow an independent reviewer to reproduce or challenge the conclusion?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
Which boundary, exception or failure case has not yet been tested?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
What must be handed over, monitored or reviewed after the immediate work is complete?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
Authoritative references and use notes
The sources below were selected as institutional or primary guidance for the broader practice. They support the handbook method; they do not imply that every statement or clause in a source applies to every project. Confirm the current edition, jurisdiction, contract and application before treating any requirement as mandatory.
- PMI Standards and Publications — Project Management Institute. Used for project, program, portfolio and organisational project management. Accessed 2026-08-13.
- ISO 31000 family — Risk management — International Organization for Standardization. Used for principles and guidance for enterprise risk management. Accessed 2026-08-13.