What should a project change log include?

Record a request ID, requester, proposed change and rationale, impacts on scope, schedule, cost, and deliverables, decision authority, disposition, decision and effective dates, baseline updates, and follow-through owner.

Is a change request the same as an approved change?

No. A request proposes a change. The team assesses its effects before the named authority approves, rejects, or defers it. Only an approved change should update the project baseline.

Do small projects need formal change control?

Use a process proportionate to the project. Even a short record should show what changed, who decided, when the decision took effect, and which commitments need updating.

Project change log template. Keep the decision clear.

Inside the free Excel change log

Preserve the request, assessment, and decision.

Download an editable workbook with instructions, a blank change log, and a fictional worked example. Record the request before assessing its effects, then capture the named decision and baseline changes.

Request	Impact assessment	Decision	Baseline update
CR-014: add mobile approval screen	Two weeks and an estimated $8,000 vendor cost	Sponsor approved on 12 October	Scope v3, milestone plan v5, and cost forecast updated

The example is fictional. Replace its authority, dates, costs, and baseline references with your project’s agreed process.

What belongs in a project change log?

Give each request a stable ID, requester, description, and rationale. Assess scope, schedule, cost, and deliverable effects before recording the decision authority, disposition, effective date, and next action.

What happens after approval?

Update the affected project baselines, assign the follow-through, and communicate the new commitment. Keep rejected and deferred requests with a short decision reference.

Download the free template

Compare the approved charter · Report the change in project status · Connect decisions to RAID