Construction Change Order Log Template: Track Requests, Decisions and Cost Context

A construction change order log template gives the team one view of proposed, developing, rejected, and authorized changes. Its purpose is control and visibility—not to turn every site conversation into an approved change.

The log should connect scope, evidence, decision status, schedule context, and cost context without replacing the contract’s notice, instruction, valuation, approval, or dispute processes. Obtain project-specific contractual and legal guidance where required.

Define what enters the change log

Agree which events create an entry: client requests, design revisions, unforeseen conditions, contractor proposals, authority requirements, substitutions, corrections, or scope clarifications with possible time or cost effect. Do not wait for perfect information if early visibility matters.

At the same time, avoid logging routine coordination as a commercial change without basis. The originator should state what changed from the controlled baseline and link the source revision, instruction, or observed condition.

Copyable construction change order log template

Use project-approved status labels. Similar-sounding labels can have materially different contractual meanings.

Give every change a stable identity

Assign a unique ID when the item enters the process and do not recycle it. Keep the short title factual: “Relocate Level 2 cable tray around revised duct route” is more useful than “Electrical change.”

Link related requests, RFIs, drawings, meeting items, photos, and notices rather than duplicating their full content. Preserve superseded records and revision history according to the project’s document-control rules.

Use parent and child references when one originating event produces several separately assessed changes. For example, a design revision may affect electrical routing, ceiling access, and fire stopping under different owners. Keeping distinct entries allows each assessment to progress without losing the common source. Do not merge them merely to reduce row count if their authorities, evidence, or implementation dates differ.

Describe the baseline and proposed difference

A defensible entry explains the starting requirement, the proposed or observed difference, affected location, and source. Without a baseline reference, reviewers cannot tell whether the item is a change, correction, clarification, or original obligation.

Use neutral wording where responsibility is unresolved. For a site condition, record what was observed and by whom. The construction daily report template can provide dated factual context, while the change log tracks the governance path.

Use statuses that cannot imply false approval

Create a status dictionary and publish it with the log:

Never use a green colour or a meeting comment as a substitute for an approval reference.

Separate scope, cost, and schedule assessments

These dimensions mature at different speeds. A technical solution may be understood before its price is checked; a cost may be estimated before schedule analysis is complete. Track each state separately.

Label monetary values clearly: rough order, contractor quotation, assessed amount, negotiated amount, or authorized amount. Do not sum unlike values into a misleading forecast. For schedule, identify affected activities, assumptions, mitigation, and analysis status without making unsupported entitlement conclusions.

Record whether values include tax, overhead, contingency, escalation, or allowances only when the applicable process requires and defines those fields. Keep source currency and valuation date visible on multi-currency projects. If quantities or rates remain provisional, identify the measurement needed to replace them. Precision in the label matters more than displaying an apparently exact number built from unresolved assumptions.

Track notices and decision deadlines

Contractual notice periods, content, delivery methods, and authority vary. The log can flag a deadline and link a notice, but it should not be assumed to satisfy the notice itself. Assign a competent owner to check the applicable contract promptly.

Use reminders for information due, quotation due, review due, decision needed, and implementation dates. When a deadline changes, preserve the previous date and the authority for the update.

Connect decisions to accountable authority

For each decision, record who had authority, what exactly was decided, limits or conditions, date, and source document. A project discussion may recommend a change without authorizing it.

The decision log template helps preserve rationale and review triggers. Use construction progress meeting minutes as a communication record, but route approvals through the defined controlled process.

Manage work-at-risk and urgent conditions carefully

Sometimes work must pause while information is resolved; sometimes an urgent condition requires immediate protective action. Record the safe operational response separately from later commercial assessment. Safety and emergency decisions should follow competent site procedures, not wait for pricing.

If someone proposes proceeding before formal authorization, document the request, authority, limits, evidence, and risk through the project’s approved route. The log itself does not authorize work-at-risk.

Review the log as a management tool

Sort views by urgent decision, owner, aging, affected area, status, forecast exposure, or start-blocking condition. A weekly review should focus on items needing action rather than reading every closed row.

Add an aging rule that fits the project’s decision cycle. Aging should begin from a defined event—such as identification, complete submission, or receipt by the decision-maker—so the metric is not misleading. Review items that repeatedly move between statuses, because this often signals unclear evidence requirements or authority. Record the reason for a reset instead of erasing elapsed time.

Use a concise review sequence:

1. New items have a baseline and owner.
2. Required notices and deadlines are visible.
3. Missing information has an accountable supplier.
4. Cost and schedule states are labelled accurately.
5. Decisions cite authority.
6. Authorized changes reach drawings, plans, and field teams.
7. Closed items have implementation evidence.

Turn authorized change discussions into structured draft updates. Kuno can support consented capture and draft notes, but a responsible project professional must verify scope, status, values, dates, and authority. Explore Kuno

Example change log entry

ID: PCO-027
Title: Relocate Level 2 cable tray at grid E4
Origin: Design coordination response RFI-014, revision 1
Baseline: Electrical drawing E-221, revision C
Status: Under assessment; not authorized
Scope: Review 12-metre route adjustment and support changes
Cost context: Contractor quotation requested; no value recorded as approved
Schedule context: Potential effect on ceiling inspection; analysis pending
Action: Electrical contractor to submit method and quotation by 22 July
Decision required from: Authorized contract representative under project procedure
Field note: No installation under revised route until controlled instruction is issued

This entry is useful because it states what is known, what remains uncertain, and what is not authorized.

Close the loop into delivery records

Once authorized, update relevant drawings, schedules, work packages, permits, inspection plans, and field briefings. Track completion and acceptance rather than closing the item at signature. A construction punch list template may capture residual defects, while meeting follow-up supports owner-dated actions.

Audit the log periodically for duplicate items, stale estimates, missing authority, broken links, and status drift. Protect commercially sensitive and personal information with appropriate access and retention.

Keep the log controlled, evidence-linked, and explicit about uncertainty. Use recording only where authorized and appropriately disclosed, then require human review before changing any commercial or contractual record. See Kuno for change notes