Describe
Capture the field condition with a unique ID, location, date, photographs, original contract reference, and the person who raised it.
Capital project control tool
Capital Project Change Order Register
A change request should explain the field condition, scope, price, schedule effect, risk, authority, and proof of completion before it disappears into the next payment application.
Quick answer
Use one numbered register from request to closeout.
Record the original contractual baseline, the observed reason for change, the proposed work, itemized cost, time effect, funding source, professional review, and written approval. Keep emergency stabilization identifiable from permanent work.
Do not equate an approved price with verified completion. Inspect quantities and quality, reconcile invoices and the schedule, and collect updated drawings, permits, warranties, and records before closing the item.
25 controlsFrom intake to closeout
8 stagesOne controlled register
1 ownerFor each open change
Decision sequence01 02 03 04
Separate the question from the approval.
Evaluate
Ask for a defined scope, itemized price, credits, schedule logic, permit implications, safety and quality review, and funding forecast.
Authorize
Confirm the decision maker, specialist recommendation, and written direction before nonemergency work begins.
Verify
Inspect the work, reconcile quantities and invoices, update the schedule and controlled drawings, and close the records gap.
Filterable control library
Find the next review point.
These controls are a management framework. The executed contract, governing documents, professional scope, and site conditions determine the actual process and authority.
25 items shown
| Stage | Control | Evidence and owner | Escalate when |
|---|---|---|---|
| Intake | Assign a unique change request ID | Numbered register and submission dateOwner: Project manager | Work is directed outside the register |
| Intake | Describe the observed condition | Site report and location photographsOwner: Field lead | Condition is undocumented |
| Intake | Identify who initiated the change | Request and authority recordOwner: Project manager | Requester lacks authority |
| Intake | Separate emergency stabilization from permanent work | Safety instruction and temporary scopeOwner: Owner representative | Immediate safety action is delayed |
| Scope | State the original contract requirement | Executed scope and drawing referenceOwner: Contract administrator | Baseline requirement cannot be found |
| Scope | Describe added deleted and changed work | Marked-up scope and quantitiesOwner: Design professional | Change scope is ambiguous |
| Scope | Record assumptions and exclusions | Written proposal qualificationsOwner: Project manager | Material exclusion is hidden |
| Scope | Check affected permits and inspections | Permit and inspection reviewOwner: Design professional | Approval path is unclear |
| Scope | Assess warranty and system interfaces | Manufacturer and specialist inputOwner: Facilities lead | Change compromises existing coverage |
| Price | Request itemized labor material equipment and markup | Price breakdownOwner: Cost reviewer | Lump sum lacks support |
| Price | Compare unit rates with contract terms | Rate schedule and quantity checkOwner: Contract administrator | New rate conflicts with agreement |
| Price | Check credits for deleted work | Original scope value and credit scheduleOwner: Cost reviewer | Deleted scope is billed in full |
| Price | Update contingency and funding forecast | Cost-to-complete forecastOwner: Treasurer | Available funding is uncertain |
| Schedule | Quantify time and sequencing effect | Updated schedule with logicOwner: Project manager | Delay claim lacks critical-path basis |
| Schedule | Review impacts on residents and access | Access plan and communication draftOwner: Property manager | Occupied areas are affected without plan |
| Risk | Document safety and quality consequences | Risk review and inspection hold pointsOwner: Design professional | Unreviewed condition affects safety |
| Risk | Check insurance and bonding implications | Contract and coverage reviewOwner: Risk liaison | Coverage position is unclear |
| Approval | Confirm decision authority and quorum | Delegation and board recordOwner: Board secretary | Work is approved by the wrong role |
| Approval | Record professional recommendation and limits | Written recommendationOwner: Owner representative | Decision relies on unverified assumption |
| Approval | Issue written authorization before nonemergency work | Signed change order or written directionOwner: Contract administrator | Work starts without written authority |
| Execution | Update drawings logs and site instructions | Current controlled documentsOwner: Project manager | Crews use superseded direction |
| Execution | Verify installed quantities and quality | Inspection and measurement recordsOwner: Field lead | Payment precedes verification |
| Execution | Reconcile invoice and schedule updates | Payment application and updated forecastOwner: Treasurer | Change is billed twice or early |
| Closeout | Collect warranties permits and as-built changes | Closeout indexOwner: Records custodian | Final documents omit the change |
| Closeout | Record final cost schedule and lessons learned | Approved final register and variance explanationOwner: Owner representative | Change remains open after acceptance |
Worked example
A concealed facade condition changes the repair scope.
During restoration, the contractor documents a condition that was not visible in the original survey. The owner representative gives the request an ID and preserves photographs and drawing references. A qualified design professional evaluates the condition and defines the required scope before the board considers cost or schedule.
The proposal separates added work from credits for deleted work and states unit rates, assumptions, permit implications, resident access effects, and time impact. The authorized party records a written decision. At completion, field measurements, inspection evidence, the payment application, updated drawings, and warranty records close the same register entry.
The scenario is illustrative; the contract and project professionals control the actual technical and approval process.
Scope and judgment
Use the contract and qualified project team.
Change orders can affect safety, design, permitting, insurance, funding, and contractual rights. This register helps leaders organize evidence and decisions; it does not replace the engineer, architect, contractor, lawyer, insurer, or other qualified adviser responsible for a particular issue.
Working method
Test the complete effect of a proposed change
A change is more than its quoted price.
Compare the proposed work with the signed scope and drawings, then record the cause, quantities, labor and material basis, exclusions, markup, and whether another contractor or warranty is affected. Ask for a revised schedule showing critical milestones, access restrictions, and inspection dependencies. If a change saves money, document what performance or warranty is surrendered.
For example, a wall repair discovered after demolition may require temporary protection before the final detail is designed. Record temporary work separately from permanent work and define the authorization limit for each. Keep field direction, board approval, contract amendment, and payment certification linked, so no invoice becomes the first evidence of an expanded scope.
Need independent oversight of project changes?
Request a focused review
Hypothetical worked example
Several small changes hide cumulative exposure
A fictional project has several approved variations plus a pending proposal. Reviewing each in isolation conceals the total commitment and the uncertain exposure.
Original fictional example · no completed client assignment or property inspection is represented.
| Record to obtain | Review question or calculation |
|---|---|
| Base agreement | Keep pending amounts separate from approved commitments |
| Approved and pending change register | Show cumulative cost and schedule effects |
| Time and funding implications | Confirm the scope and approval route for each change |
Useful working output: A change decision supported by a complete cumulative register.
Adapt the record request to authorized access, governing documents and the actual property. The example does not verify any unknown input or replace a professional conclusion.
Capital Project Payment Evidence and Milestone Review · More capital projects and building safety examples
Before acting on this guide
Set the review boundary and the acceptance test.
When to use it
A contractor requests added cost or time.
What the evidence does not prove
Do not approve the same obligation twice through an allowance and change.
What to verify before acceptance
Compare baseline, prior changes, credits and pending exposure; retain separate field direction and financial approval.
Original proposed coordination checks · adapt to authorized access, the actual obligation and the appropriate professional review. These are not findings about your property.
Follow the related handoff workflow · Read the review definitions
A number, its evidence and the decision
Show commitments and remaining work in the same forecast
A paid-to-date figure is not the expected final cost. Distinguish paid invoices, unpaid commitments and uncommitted remaining work so each amount appears once in the forecast.
Baseline
Record the authorized scope and budget.
Commitment
Include paid and unpaid committed cost once.
Forecast
Estimate uncommitted remaining work separately.
Control
Review headroom and changes before commitment.
A worked example with visible assumptions
A fictional project has a $300,000 authorized budget, $220,000 in commitments including invoices already paid, and $65,000 of uncommitted remaining forecast cost. Expected final cost is $285,000 and headroom is $15,000. Do not add paid invoices again. Headroom excludes any risk allowance not entered in the remaining forecast.
Original hypothetical arithmetic example. The amounts describe a fictional scenario, not observed property performance or a recommended target.
Continue with Capital Project Change Order RegisterExplore the calculation
Enter non-negative values using the same scope and period. This calculation stays in your browser tab.
A change needs a baseline
Identify what changed against the executed scope, including price, time, dependencies and acceptance effects.
Avoid double counting
If a commitment includes a paid invoice, adding both inflates the forecast. Track payment status within the commitment.
Closeout starts before the last invoice
Commissioning, permits, punch-list work and warranty records belong in the plan while the delivery team can still resolve them.
Put the guidance to work
Reconcile the change against the approved baseline
A request for additional work may duplicate an allowance or an obligation already included in the contract. Compare the original scope, drawings, exclusions, allowance ledger, and previously approved changes before reviewing price.
Ask for quantities, unit rates, credit for deleted work, schedule effects, and evidence of the condition creating the request. Mark a field instruction separately from a financially approved change.
Track cumulative approved changes and pending exposure against the remaining contingency. Close the change only after the installed work, revised documents, and payment support have been reconciled.
Can work start before a change order is approved?
Follow the contract and delegated authority, including any documented emergency process. Record field direction separately from financial approval and reconcile scope, cost, and schedule before payment.
Apply the next operating control
- Capital Project Warranty Tracking and Defect Follow-Up
- Capital Project Resident Access and Disruption Planning
Find checklists and data definitions · Explore capital projects and building safety