Master register of all change orders / variations on the project. Tracks scope, cost, schedule + approval status of each change. Critical for project commercial + schedule control.
CO Register Summary: Total 23 COs, 18 approved (₹15.2 cr, +33 %), 3 in review, 2 rejected. Cumulative time impact: +90 days. Top 3 by value: Client scope addition L+7 building (₹8 cr), MEP upgrade (₹3.5 cr), Architectural finishing change (₹2 cr).
Even well-defined contracts undergo scope changes during execution — client adds features, design errors emerge, site conditions differ from design, statutory requirements update. Each change must be formally processed via Change Order (CO) to avoid scope creep + cost overruns + commercial disputes.
The Change Order Register is the project-level master log of all COs — proposed, approved, rejected, and their cost + schedule impacts. Without this register, end-of-project reconciliation becomes a nightmare; contractor + client argue over what was changed + paid for.
Indian government contracts (NHAI, MoRTH, CPWD) and FIDIC-based contracts all have formal CO procedures. The register operationalizes these procedures.
Per-change: 1. Change Request raised — by client / consultant / contractor; describes proposed change + reason 2. Impact assessment — designer evaluates technical impact + cost + schedule implications 3. Cost quotation — contractor submits rate + total impact 4. Negotiation — both parties agree on cost + time impact (or escalate) 5. Formal CO instrument — signed by both parties 6. Implementation — change actually executed 7. Closeout — actual cost + time recorded; vs negotiated 8. Register entry — CO ID, description, dates, decisions, impacts
Per-CO register fields: - CO number + sequential ID - Initiator (client / contractor / consultant) - Description of change - Trigger (design defect / scope addition / site condition / statutory update / value engineering) - Cost impact (rupees increase / decrease) - Schedule impact (days increase / decrease) - Status: Proposed / Under Review / Approved / Rejected / Withdrawn / Implemented - Approval references - Linked NCRs / RFIs
1. No formal process — verbal change requests → site executes; reconciliation impossible. 2. Scope creep — many small changes individually below threshold; cumulatively significant. 3. Cost negotiation delays — months of back-and-forth on rates while contractor works ahead; later disputes. 4. Schedule impact mis-assessed — contractor accepts schedule extension but doesn't consider downstream activity impact. 5. Pricing disputes — new-item rates not in BOQ; market rates differ from contractor's claim. 6. No traceability — CO references contract clause but contract doesn't have such clause; baseless claim. 7. No statutory linkage — change driven by new regulation; documentation insufficient; client refuses payment. 8. End-of-project chaos — many open COs at handover; settlement complex + disputed.
Companion PMC formats: - Design Change Request (PMC-DES-FRM-002) — design-side changes - Contract Amendment Log (PMC-BIL-LOG-004) — contract-level amendments - RFI Review (PMC-MTG-MOM-012) — design clarifications - Dispute Register (PMC-RSK-REG-005) — for disputed COs - Deductions Register (PMC-BIL-REG-002) — financial impact tracking
Contract frameworks: - FIDIC General Conditions — Clause 13 (Variations) - NHAI / MoRTH / CPWD standard contracts — Indian government CO procedures - Indian Contract Act 1872 — alteration of contracts (Section 62-63) - GFR 2017 — government procurement variations