Skip to content
    Free Construction Template

    Construction Change Order Template

    Document the scope change, contract adjustment, schedule impact, supporting records, and approvals in one clear project record.

    No email required. Copy the form into your project documents or print and save it as a PDF.

    Construction Change Order

    Change Order Form · Project Record

    jet.build

    Project Information

    Project Name
    Project Number
    Project Address
    Owner / Developer
    General Contractor / Construction Manager
    Contract Number
    Change Order Number
    Date Issued
    Effective Date

    Change Order Information

    Change Order Title / Subject
    Change Type / CategoryOwner Request · Design Revision · Field Condition · Scope Clarification · Allowance Adjustment · Value Engineering · Schedule Change · Other
    Related Change Event / PCO
    Related RFI
    Related Submittal
    Related Drawing / Specification
    Affected Trade(s)
    Location / Project Area

    Description of Change

    Scope ChangeDescribe the work being added, deleted, revised, or otherwise changed.
    Reason for ChangeState the project condition, decision, document revision, owner direction, coordination issue, or other basis for the change.
    Detailed DescriptionDescribe enough detail that the parties reviewing the change can understand exactly what work is affected.

    Supporting Documents

    Drawing References
    Specification References
    RFI References
    Submittal References
    Proposal / Estimate Reference
    Schedule Reference
    Photos / Markups
    Other Attachments

    Contract Value Adjustment

    Cost Adjustment TypeAdd · Deduct · No Cost Change
    Original Contract Sum
    Net Change From Previously Approved Change Orders
    Contract Sum Before This Change Order
    Amount of This Change Order
    Revised Contract Sum

    Cost Breakdown

    Optional — use the breakdown required by your project procedures.

    Labor
    Materials
    Equipment
    Subcontractors
    Allowances
    Taxes / Insurance / Bonds
    Markup / Overhead / Fee
    Other
    Total

    Schedule Impact

    Time AdjustmentDays Added · Days Deducted · No Time Change
    Affected Schedule Activity / Milestone
    Current Contract / Milestone Date
    Revised Date
    Calendar Days Added
    Calendar Days Deducted
    Schedule Impact Description

    Related Project Impact

    Procurement Impact
    Design / Coordination Impact
    Submittal Impact
    Field / Sequence Impact
    Budget / Forecast Impact
    Other Downstream Action Required

    Approval / Execution

    Approval requirements and authority are governed by the applicable contract and project procedures.

    Prepared By
    Company
    Date
    Reviewed By
    Company
    Date
    Approved By
    Company
    Date
    Owner / Authorized Representative
    Company
    Date
    Contractor / Authorized Representative
    Company
    Date
    Additional Approval
    Company
    Date

    Notes / Conditions

    Notes / Conditions

    Project-specific contract documents and procedures govern actual change-order requirements, approval authority, pricing, entitlement, schedule adjustments, and execution.

    How to use this construction change order template

    1. 1Identify the change. Give the change order a unique number and a specific subject.
    2. 2Connect it to the source. Reference the RFI, drawing revision, field condition, owner direction, submittal, proposal, or other record behind the change.
    3. 3Define the scope. Describe exactly what work is being added, removed, or revised.
    4. 4Document the cost. Record the proposed or agreed contract adjustment according to project procedures.
    5. 5Document the time impact. Identify affected activities, milestones, and any proposed time adjustment.
    6. 6Attach supporting records. Include estimates, drawings, markups, RFIs, proposals, photos, and schedule information when applicable.
    7. 7Route it through the required review so responsibility and approval status stay visible.
    8. 8Update the project record. After approval or execution, make sure budgets, commitments, forecasts, schedules, and related records reflect the change as appropriate.

    For the broader process behind the form — how potential changes move through pricing, schedule review, approval, and execution — see our guide to construction change orders.

    These steps are a practical starting point. Project-specific contract documents and procedures govern actual change-order requirements, approval authority, pricing, entitlement, schedule adjustments, and execution.

    Example of a completed construction change order

    Fictional example for illustration only.

    Change Order
    CO-017
    Title
    Loading Dock Slab Drainage Revision
    Project
    Harbor Point Office Renovation
    Related Records
    RFI-041 · Drawings A-504 / P-202
    Cost Adjustment
    +$12,500 (Add)
    Time Adjustment
    0 calendar days (No Time Change)
    Status
    Approved

    Reason for change

    Revised drainage configuration after coordination between architectural, structural, and plumbing documents.

    Change description

    Revise the loading dock slab depression and drain configuration based on the coordinated detail issued in response to RFI-041.

    Schedule context

    Work is incorporated before the affected concrete placement.

    Supporting documents

    Contractor proposal, RFI-041 response, A-504 markup, P-202 markup.

    Fictional example for illustration only. The amount shown does not represent any benchmark or typical value.

    What makes a construction change order effective?

    A strong change order has

    • One clearly defined scope change
    • Specific document references
    • A clear reason for the change
    • Cost impact documented
    • Time impact documented
    • Affected work identified
    • Supporting records attached
    • Approval responsibility clear
    • Final execution documented
    • Related project records updated

    A weak change order has

    • Vague scope
    • No source documentation
    • Multiple unrelated changes bundled together without clarity
    • Unclear pricing basis
    • No schedule impact documented
    • Missing attachments
    • Unclear approval status
    • A change discussed only through email
    • No connection to downstream project records

    Change order vs. RFI — what is the difference?

    RFI

    Asks for clarification or resolves missing or conflicting project information.

    • Question
    • Document references
    • Responsible party
    • Response
    • Project impact

    Learn what an RFI is in construction.

    Change order

    Documents an approved or formally processed change affecting contract scope, cost, time, or other contractual requirements according to the project's procedures.

    • Scope change
    • Cost adjustment
    • Time adjustment
    • Supporting records
    • Approvals
    • Revised contract information

    An RFI can lead to a potential change, but an RFI itself is not a change order. Project-specific contract documents and procedures govern actual contractual treatment.

    Potential change vs. executed change order

    Many construction teams track a potential change before it becomes an executed change order. Depending on the organization, that intermediate record may be called a change event, a potential change order, a PCO, a change request, a change proposal, or a proposed change. These names are not universally interchangeable — the applicable contract and project procedures define what each record means on a given project.

    • Change Event
    • Potential Change Order
    • PCO
    • Change Request
    • Change Proposal
    • Proposed Change

    Potential change

    Used to evaluate scope, pricing, schedule impact, responsibility, and supporting documentation before anything is formalized.

    Change order

    Used when the change reaches the formal approval or execution stage required by the applicable project procedures.

    A good workflow preserves the connection between the original issue and the final approved change.

    Why use a formal change order instead of just documenting the change in email?

    Email is useful for communication. A formal change-order record does a different job: it provides structured visibility into

    • Change number
    • Scope
    • Source documents
    • Cost adjustment
    • Schedule adjustment
    • Approval status
    • Authorized parties
    • Supporting attachments
    • Final execution
    • Downstream project updates

    Communication and formal project record are two different jobs. Most teams need both.

    When is a change order template enough?

    A document template can work well when:

    • Change volume is manageable
    • One person maintains the register
    • Review responsibility is clear
    • Pricing backup is easy to organize
    • Approval routing is straightforward
    • Contract values are updated consistently
    • Schedule impacts are manually coordinated
    • Project stakeholders share one clear filing structure
    When the document stops scaling

    The form records the change. The workflow controls the exposure.

    A single well-written form documents one change. Larger projects and portfolios also need a project-wide view — a construction change-order log template gives the team visibility across:

    • Potential changes
    • Pricing requests
    • Owner decisions
    • Design decisions
    • Change status
    • Responsible party
    • Approval routing
    • Budget impact
    • Forecast impact
    • Commitment impact
    • Contract value
    • Schedule impact
    • Related RFIs
    • Related submittals
    • Supporting documents
    • Executed changes
    • Portfolio reporting
    Change management in Jet.Build

    Connect change orders to the rest of the project.

    Jet.Build keeps change records connected to the financial and project information behind them — including budgets, commitments, RFIs, documents, approvals, schedules, and reporting — so teams can review the change in context rather than rebuilding the story from separate spreadsheets and email threads. Changes stay linked to the project records they affect.

    Explore Cost Management Explore Financial Management

    Related construction resources

    Construction Change Order Log TemplateTrack potential and approved changes across the project — including status, responsibility, pending exposure, approved cost, and schedule impact.Construction Cost Management SoftwareConnect project changes to budgets, commitments, forecasts, approvals, and cost visibility.Construction Financial ManagementManage project financials and maintain clearer visibility into changing contract values.What Is a Change Order in Construction?Learn how potential changes move from issue identification through pricing, schedule review, approval, and execution.What Is an RFI in Construction?Understand how project questions are documented and when an RFI can lead to a downstream change.Construction RFI TemplateDocument the question or clarification that may precede a potential change.Construction Project ManagementKeep RFIs, submittals, approvals, documents, and project records connected.Workflow AutomationRoute project reviews and approvals with clearer ownership.

    See how Jet.Build manages project changes from issue to approval.

    Take about 30 minutes with our team to see how Jet.Build connects changes to project financials, documents, RFIs, schedules, approvals, and reporting.

    Schedule a Demo