Change Request Form and Log


Phase: Execution | Audience: Shared | Project: WEB-2026-01 Corporate Website Development


Understand it first

In simple words: The Change Request Log records every change asked for and its decision. The Change Request Form captures one change in detail: what, why, impact on cost and time, and who approved it.

Think of it like: A renovation contractor's notebook: 'Client asked for an extra shelf: ₹5,000, 1 day, approved on 3 Nov.'


When is it created?

Execution, whenever a change is requested

Who prepares it?

Project Manager

Who approves or uses it?

Client Head of Marketing for billable changes

What happens next?

Approved changes update scope, schedule, budget and invoices


How it connects to other documents

  1. Follows the Change Management Plan.
  2. Decisions are also recorded in the Decision Log.
  3. Approved CR-001 appears in the Invoice Tracker and UAT Test Cases.


The sample document

Below is the actual document for project WEB-2026-01. Read the purpose first, then go through each numbered section.

Issued by: [Your Company] Technologies Pvt. Ltd.

Purpose: All change requests raised on the project, with a completed form for CR-001 as an example.


Item


Detail


Document no.

WEB-2026-01/CR

Version

1.0

Date

6 Nov 2026

Owner

Project Manager

Audience

Shared with client

Phase

Execution


1. Change request log

CR no.


Raised


Requested by


Description


Cost (₹ + GST)


Schedule impact


Decision


Decided on


CR-001

3 Nov

Marketing Executive

Add a Careers page with job listings

12,000

None

Approved

6 Nov

CR-002

4 Nov

Head of Marketing

Hindi version of the whole website

85,000

+3 weeks

Deferred

6 Nov

CR-003

5 Nov

Marketing Executive

Live chat widget with 24×7 chatbot

38,000

+1 week

Rejected

6 Nov


2. Change request form: CR-001

Item


Detail


CR number

CR-001

Date raised

3 Nov 2026

Requested by

Marketing Executive

Priority

Medium


Description of change

Add an 11th page, Careers, listing open positions that the marketing team can add and remove from the CMS, with an Apply button linking to the HR email.


Reason

The client is hiring for three roles in January and wants applicants to find openings on the website.


Impact assessment

Area


Impact


Scope

One new page and a Jobs post type in the CMS

Effort

16 hours (design 4, frontend 6, backend 4, QA 2)

Cost to client

₹12,000 + GST ₹2,160 = ₹14,160 (rate card: additional page)

Schedule

No change to go-live if approved by 6 Nov; built in parallel

Risk

Low


Decision

Approved on 6 Nov 2026 by the Head of Marketing. To be invoiced with milestone M3. Scope Statement updated to v1.1 and schedule to v1.1.

Signed for


Signature


Date


Approved by: Head of Marketing, [Client Name]

Name and signature: ____________

Date: ________

Project Manager

Name and signature: ____________

Date: ________


WEB-2026-01/CR · v1.0 · Shared with client. Bracketed items such as [Client Name] are placeholders.


Key takeaways

  1. Changes can be approved, rejected or deferred to a later phase.
  2. Impact assessment comes before the decision.
  3. A logged change is extra revenue, not extra free work.


Common mistakes to avoid

  1. Doing the work before approval.
  2. Not checking schedule impact.
  3. Losing track of deferred requests.


Next lesson: 27. Issue Log