Skip to main content
Skip to main content

📝 Change Order Workflow Playbook

Document scope changes, get approvals, and track cost/schedule impacts properly. The #1 rule of change orders: document first, execute second. Work performed without written authorization is work you may never get paid for.


Why Change Order Management Matters

Without a ProcessWith a Process
"We told you verbally" — disputed verbal directionsWritten COR with documented direction
Performed extra work with no approval — unpaidWork authorized before execution
No cost backup — GC disputes your pricingDetailed pricing with backup documentation
Schedule impact ignored — you absorb the delayDocumented time impact included in COR
Lump-sum negotiation with no leverageCost breakdown supports fair negotiation
The Golden Rule

Never perform extra work without written authorization. If you're told verbally, confirm in writing before starting. If you're forced to start due to schedule pressure, send a written notice of intent to claim the cost within 24 hours.


Roles and Responsibilities

RoleResponsibilities
Field PersonnelIdentify changed conditions, document immediately (photos, notes), notify foreman
ForemanReport potential change to superintendent, track extra labor/equipment/materials separately
SuperintendentNotify PM of potential change, document field conditions, review COR for accuracy
Project ManagerDraft COR, prepare pricing, submit to owner/GC, negotiate, track approval
Project EngineerMaintain change order log, assemble backup documentation, track status
EstimatorPrepare detailed cost estimates for COR pricing

Types of Changes

TypeTriggerExample
Owner-directed changeOwner requests additional or different work"Add 6 electrical outlets to Conference Room B"
Design error / omissionDrawings or specs are wrong or incompleteStructural conflict discovered — RFI confirms redesign needed
Differing site conditionsActual conditions differ from contract documentsUnderground rock not shown on geotech report
Regulatory changeBuilding code or permit requirement changesInspector requires additional fire stopping not in original scope
Schedule accelerationOwner requests earlier completion"We need to move in 2 weeks earlier"
Scope reduction (credit)Owner removes work from your scope"Delete the interior painting from your contract"

Step-by-Step Process

Step 1: Identify the Change (Immediately)

The moment anyone on your team identifies potential extra work:

  1. Stop and evaluate — Is this in our contract scope? Check the contract documents.
  2. Do NOT proceed with the extra work unless there's a safety or emergency reason
  3. Notify the superintendent and PM — immediately, verbally + in writing
  4. Document the condition — Photos, measurements, descriptions
  5. Start tracking costs separately — Use a separate cost code for the potential change

Step 2: Send Written Notice (Within 24–48 Hours)

Check your contract for notice requirements. Most contracts require written notice within a specific timeframe (often 7–21 days). Missing the notice deadline can waive your right to the change order.

Written notice includes:

  • Date
  • Contract and project reference
  • Description of the changed condition or direction
  • Contract provision requiring the change (if applicable)
  • Statement of intent to request a change order
  • Request for direction on how to proceed

Example notice:

"This letter serves as notice that on 02/12/2026, during excavation at Grid B/4, we encountered rock at elevation 98.5'. The geotechnical report (dated 08/2025) indicates soil to elevation 95.0'. This constitutes a differing site condition per Section 4.3 of the contract. We request direction on how to proceed and reserve our right to submit a change order for the additional cost and time required for rock removal."

Step 3: Document Everything

What to DocumentHowWhy
Photos of the conditionBefore, during, and afterVisual evidence of the change
Daily reports noting the changeSeparate entries for change workContemporaneous record
Extra labor hoursSeparate time cards or cost codesCost backup
Extra equipmentUsage logs with hoursCost backup
Extra materialsReceipts, delivery tickets, invoicesCost backup
Written directions receivedEmails, RFI responses, meeting minutesProof of direction
Schedule impactUpdated schedule showing delay/accelerationTime extension support

Step 4: Prepare the Change Order Request (COR)

COR Package includes:

  1. Cover letter — Summary of the change, contract reference, total cost and time requested
  2. Detailed cost breakdown:
Cost CategoryCalculation Method
LaborHours × rate (including burden) per worker/trade
MaterialsQuantity × unit cost (with supplier quotes or invoices)
EquipmentHours × rate (rental rate or internal rate)
Subcontractor costsSub's quotes or invoices (with your markup)
OverheadPer contract (typically 10–15% of direct costs)
ProfitPer contract (typically 5–10% of direct costs)
Bond premiumIf bonded (typically 1–2% of change amount)
TotalSum of all categories
  1. Backup documentation — Time cards, material receipts, equipment logs, photos, RFI responses
  2. Schedule impact analysis — Days of delay or acceleration, revised milestone dates
  3. Markup substantiation — Reference the contract markup provisions

Step 5: Submit and Track

  1. Submit COR per contract requirements (usually to GC or owner's representative)
  2. Log in the change order tracking system
  3. Request written acknowledgment of receipt
  4. Set follow-up reminders:
    • Day 7: Follow up if no response
    • Day 14: Formal follow-up with schedule impact warning
    • Day 21+: Escalate per contract dispute provisions

Step 6: Negotiate

ApproachWhen to Use
Agree on price before workPreferred — no risk of non-payment
T&M with not-to-exceedWhen scope is unclear — track actual costs up to a cap
T&M open-endedEmergency or undefined scope — agree on rates, track actual costs
Proceed under protestWhen forced to start before agreement — document everything, reserve rights

Negotiation tips:

  • Start with your detailed backup — let the numbers speak
  • Be prepared to explain every line item
  • Know your contract markup rates before negotiating
  • Don't accept "we'll work it out later" — get it in writing
  • If you can't agree on price, agree on a method (T&M) and track it

Step 7: Execute the Change Order

Once approved:

  1. Receive signed change order document
  2. Verify it matches what was agreed (scope, cost, time)
  3. Distribute to field — superintendent, foreman, affected subs
  4. Update the schedule of values
  5. Include in the next pay application
  6. Update project budget and schedule

Change Order Log

Track every potential and actual change:

#DescriptionDate IdentifiedNotice SentCOR SubmittedAmountStatusCO #
PCO-001Rock at Grid B/402/1202/1202/20$28,500Under Review
PCO-002Add outlets to Conf Room B02/14N/A (owner directed)02/18$4,200ApprovedCO-003
PCO-003RFI-042 beam redesign02/1502/15PendingTBDPricing

Common Mistakes

MistakeConsequenceFix
Performing work before approvalOwner can refuse to payGet written authorization first — always
Missing the notice deadlineWaive your right to the changeKnow your notice requirements, send notice within 24 hours
Verbal agreements"That's not what we agreed to"Confirm everything in writing
Incomplete cost backupGC disputes your numbersTrack every hour, receipt, and invoice from day one
Ignoring schedule impactYou absorb the delayAlways include time extension request with cost
Bundling unrelated changesOne disputed item holds up the whole packageOne COR per change — keep them separate
Not tracking pending changesLost revenueMaintain a change order log, review weekly

Metrics

MetricTargetFrequency
Notice sent within 48 hours100%Per occurrence
COR submitted within 14 days of directionover 90%Per occurrence
Approval rateover 80% of submitted CORsMonthly
Average approval timeunder 30 daysMonthly
Pending COR valueTracked and reportedWeekly
Collection rate on approved COs100% collectedMonthly

ResourceLink
Change Order Request GeneratorGenerate COR
Change Order Log TrackerCO Log
Change Order GuideFull Guide
T&M Ticket PlaybookT&M Workflow
RFI Process PlaybookRFI Process