← LibraryChange Request FormTemplates & Examples · Project TemplatesLesson 14/22← PrevNext →
TemplatePublished 14 Jul 20264 min readBy Kevin Joginchange managementchange requestproject controltemplate
KEVOS®
Templates & Examples · Project Templates
Templates & Examples / Project Templates

Change Request

Formally propose, assess, and disposition project changes with this structured request form template and worked example.

4 min read 3 sections Document Template Worked Example
Proposal Assess IMPACTS Scope Cost Schedule Decision
Doc № KEV-TPL-095 Sec 4 Sheet 1/1 Drawn KEVOS® 14 Jul 2026

In this resource

  1. Purpose of the Change Request
  2. Blank Template
  3. Worked Example: Mary's Consulting

§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.

Relationship to the Change Log Every Change Request form generated on a project must be immediately registered in the Change Log. The log acts as the central index, while these forms serve as the detailed dossiers for each individual item (e.g., CR-001, CR-002).
Contents

§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

Project Title [Insert Project Name]
Date Prepared [YYYY-MM-DD]
Change Request ID [CR-###]
Requestor [Name and Role]
Category (Select all that apply)
Scope
Cost
Schedule
Quality
Requirements
Documents
Detailed Description of Proposed Change
[Provide a clear, specific description of exactly what is being requested. What is being added, removed, or modified? Define the boundaries of the change.]
Justification for Proposed Change
[Why is this change necessary or beneficial? What business value does it drive? What is the risk of not implementing this change?]
Impacts (Summary)
[Detail the assessed impacts on the project constraints.
Scope: ...
Requirements: ...
Cost: ...
Schedule: ...
Quality: ...]
Disposition
Approve
Defer
Reject
Justification (CCB / Sponsor)
[Record the rationale behind the disposition decision. Note who authorized the decision, the date, and any conditions (e.g., funding source, schedule adjustments).]
Contents

§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.

Example Context This request follows CR-007 (adding a Press section). The sponsor approved this change because the $400 impact could be absorbed by the remaining project contingency, and it aligned with previously established strategic goals.

CHANGE REQUEST

Project Title Mary's Consulting - New Company Website
Date Prepared Oct 15, 2026
Change Request ID CR-008
Requestor Marketing Lead
Category
Scope
Cost
Schedule
Quality
Requirements
Documents
Detailed Description of Proposed Change
Add LinkedIn profile icons to each consultant's bio card in the consultant directory. Each bio card would display a small LinkedIn icon that links to the consultant's public LinkedIn profile (URL supplied by the consultant).

Affects ~50 launch-tier consultant cards. Out of scope: any other social platforms; LinkedIn data scraping; sign-in-with-LinkedIn functionality.
Justification for Proposed Change
Marketing Lead reports that prospects researching consultants typically check LinkedIn profiles. Providing direct links from each bio reduces friction and reinforces credibility. Sales Lead supports: current process requires prospects to search consultant names manually. Low-effort, high-perceived-value change.
Impacts (Summary)
Scope: +1 small element on bio card; +1 data field collected from consultants (LinkedIn URL).
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.
Disposition
Approve
Defer
Reject
Justification (CCB / Sponsor)
Approved by Mary (Sponsor), Oct 17, 2026. Sponsor reviewed alongside the Marketing Lead's broader launch-readiness brief. Cost ($400) drawn from remaining contingency ($11,200 → $10,800). Sponsor noted the LinkedIn-link addition as consistent with the F500-credibility theme that drove CR-007. Marketing Lead notified; Christine to begin collecting LinkedIn URLs immediately.

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.

Contents

Continue learning

NEXT LESSON →Requirements Documentation Template & ExampleTemplate · Project TemplatesChange LogTemplate · Project TemplatesWBS Dictionary Template & ExampleTemplate · Project TemplatesChange Request AssessmentTemplate · Project Templates