Change Log

A change log is the running record of every approved change to an engagement’s scope, budget, timeline, or deliverables, linking each change to its authorization and cost impact.

It answers the question “how did we get from the original agreement to where we are now?” without having to dig through email threads or compare document versions side by side.

What belongs in a change log entry

Every approved change order generates one entry. A complete entry includes:

• Change ID: a sequential reference number (CO-001, CO-002, etc.)
• Date approved: the date the change was signed off, not the date it was requested
• Description: what specifically changed, such as a new deliverable, extended timeline, or additional resource days
• Reason: client request, scope gap, assumption proven false, or regulatory requirement
• Cost impact: the delta to the original engagement budget, positive or negative
• Schedule impact: the delta to the original timeline in days or weeks
• Requested by: the client contact or the internal delivery team
• Approved by: the named client sponsor or authorized approver
• Change order reference: the document number of the formal change order

Why the change log matters for margin

Scope creep is the primary driver of margin erosion in professional services. The change log makes cumulative scope drift visible. A delivery team that reviews its change log monthly can catch the pattern of small, informal additions before they total to a meaningful budget overrun with no corresponding revenue.

Without this record, scope disputes at project close become difficult to resolve. Both parties end up reconstructing the history from email, which is slow, incomplete, and adversarial. A well-maintained change log is neutral ground: it records what was agreed and when.

Using the change log in status reporting

A one-line summary of the change log belongs in every status report: total approved changes, total budget delta, and total schedule delta. This keeps the client sponsor informed and creates a paper trail if a dispute arises at engagement close.

The change log should be shared with the client sponsor at each status review so both sides hold a shared, current picture of how the engagement has evolved from its original baseline.

Who owns it

The engagement manager owns the change log. Ownership means keeping it current after each change order is signed, not reconstructing it at the end of the project. A log that is updated in arrears loses the audit trail value that makes it useful for dispute resolution.