Construction Change Order Backup: What to Attach to a PCO Before It Goes Upstream

Key takeaways

• A proposed change order should document one change event with its source, marked scope, cost backup, field record, and any time support.
• Marked-up drawing and specification references make the scope delta visible without forcing the reviewer to reconstruct the change.
• RFI-based changes need the original question, the official response, and a direct explanation of how the answer changed priced scope.
• Unforeseen conditions and T&M work should be supported by dated field records created when the event occurred.
• A live change log keeps pricing status, revisions, approvals, and billing status tied to the same record.

Attach the source document, marked-up plan or specification references, a scope narrative, itemized cost backup, field records, and any time-impact support that applies. Keep each proposed change order focused on one change event and label the revision trail so the reviewer can follow scope, cost, and timing in one package.

Tribuild Consultancy is a multi-trade estimating, preconstruction, and project-administration support company.

Every PCO backup should include the change source, marked scope references, pricing backup, field records, and any time support.

Use one package for one change event. The file should show what changed, what caused it, where it appears in the documents, how the amount was built, and whether time is part of the request.

Include these attachments in the base package:

• PCO cover sheet or summary with the project name, PCO number, contract or subcontract reference, date, and a short description of the change event.
• One cause per package so unrelated issues are not mixed together.
• Source document that triggered the change, such as a revised drawing, bulletin, ASI, sketch, specification revision, RFI response, field directive, or documented site condition.
• Marked-up plan or specification references showing the affected area, sheet references, detail references, and the old versus new requirement where available.
• Scope narrative stating what is included, what is excluded, and which trade interfaces are affected.
• Cost backup for labor, material, equipment, subcontractor pricing, vendor pricing, and the markup structure required by the governing contract or review format.
• Time support, if time is requested, tied to procurement, sequence, access, rework, or a defined delayed activity.
• Field records such as daily reports, photos, delivery tickets, signed T&M tags, meeting notes, and dated email direction.
• Revision history and change log reference so pricing status, submission dates, revisions, approvals, and billing status stay connected.

Maintain a change log that tracks the change number, origin, pricing status, submission date, revision date, approval status, and billing status.

Documents are prepared within the contractor's established review and approval workflow.

Drawing or specification revisions need the revised requirement, the prior basis, and the quantity delta.

Attach both the new requirement and the prior basis so the scope change is visible before the reviewer opens the pricing backup.

For a drawing or specification revision, attach:

• The revised sheet, bulletin page, or specification section with the issue date and revision identifier.
• The prior version or affected excerpt of the same document.
• A marked comparison highlighting added, deleted, or relocated scope.
• Relevant detail, elevation, section, schedule, or keynote references when plan view alone is not enough.
• The specification excerpt when product requirements, finish level, accessories, testing, or performance criteria changed.
• A quantity breakdown showing the difference from the original takeoff.
• Updated vendor or subcontractor quotes tied to the revised requirement.
• A coordination note when another package is affected.

A short summary line should state the trigger and the scope delta in the same sentence. For example: revised A6.21 adds wall backing, changes door frame types, and extends wall protection; attached markup and quantity backup show the added framing, backing, hardware coordination, and finish patching.

RFI-based changes need the question, the answer, and a direct explanation of the scope change.

Attach the RFI record and explain how the answer changed the priced scope. If the answer confirms the original requirement, the package should not present it as a new scope change.

For an RFI-based change, attach:

• The original RFI with the date and full question.
• The official response from the responsible upstream party.
• Any sketch, exhibit, or supplemental instruction issued with the response.
• A before-and-after scope narrative explaining what was carried before the answer and what the answer now requires.
• Marked-up plans, details, or specification references showing the affected area.
• Quantity and cost backup tied to the clarified requirement.
• Related correspondence when the answer followed a meeting decision or verbal direction.

Same-day email follow-up helps connect field direction to the RFI, sketch, or PCO number while the record is current.

Unforeseen conditions and T&M work need contemporaneous field records.

Build these packages from dated field records created when the event occurred. The later summary should organize the backup, not replace it.

Unforeseen conditions need photos, location references, notice, and quantity support.

For a concealed or unforeseen condition, attach:

• Date-stamped photos showing the condition before corrective work starts.
• Location references such as plan area, gridline, room number, area map, or utility stationing.
• Daily reports or superintendent logs describing when the condition was found and how work was affected.
• Notice correspondence sent when the condition was identified.
• A scope narrative covering investigation, demolition, removal, patching, replacement, standby, access impact, or temporary protection.
• Quantity backup for labor, material, haul-off, replacement work, or temporary measures.
• Delivery, disposal, or trucking tickets when those costs are part of the request.
• Subcontractor or vendor quotes when another trade or supplier is involved.

T&M work needs daily tickets, matching logs, and dated cost support.

For force-account or T&M work, attach:

• Signed daily T&M tickets showing labor classifications, hours, equipment, and materials.
• Foreman reports or time records that match the tickets.
• Material invoices, packing slips, or delivery tags tied to the dated work.
• Equipment logs or rate sheets when required by the review format.
• A summary roll-up that converts the daily records into the proposed amount.
• A scope note separating extra work from base contract work.

When daily tickets are unsigned, assemble the dated logs, photos, delivery tags, and email recaps in the same package and identify the missing signature issue in the summary.

Vendor-driven material changes need the commercial paper trail.

Attach the documents that show what product or price basis was carried before the change and what pricing or product basis applies after the change.

For a vendor-driven material change, attach:

• The original basis document showing the product, system, or allowance carried before the change.
• The original quote or pricing basis, if available, used in the estimate or buyout.
• The updated vendor or supplier quote with the quote date, scope notes, validity period, and lead time.
• Any manufacturer or supplier notice that explains the reason for the change, if one exists.
• A side-by-side scope narrative describing the change in product, finish, gauge, size, accessory, freight, availability, or required alternate.
• Marked-up plans, schedules, or submittal references tying the vendor change to project scope.
• Freight, tax, restocking, or handling support when those costs are included.
• Coordination notes if the alternate affects adjacent trades, mounting, power, controls, structure, or dimensions.

When one material issue creates separate trade impacts, log the related pricing with separate scope descriptions so each item can be reviewed on its own record.

Schedule support belongs in the PCO only when the change affects sequence, procurement, fabrication, or access.

Request time only when the file can show a direct connection between the change event and a defined activity, release, or procurement path.

For schedule-related backup, attach:

• The event date and the document that caused the impact.
• The affected activity or milestone such as release for fabrication, equipment approval, rough-in start, close-in, energization, or turnover.
• A sequence narrative explaining what work was waiting, what could proceed, and what could not.
• Revised procurement, fabrication, or delivery dates when the issue affected buyout or lead time.
• Updated vendor lead-time information when supply timing is part of the request.
• A schedule excerpt, fragnet, or activity comparison when the project team uses schedule support in change review.
• Mitigation steps taken such as resequencing, alternate sourcing, partial release, or area turnover adjustments.
• Cost backup for schedule-related money such as remobilization, supervision, lifts, or added handling, when those costs are included.

A standard backup template by change type keeps estimating, project management, field records, and billing support aligned. If you want to review one upcoming project or change-management workflow, Tribuild can discuss a cleaner estimating-to-project-administration handoff.

Sources

• https://tribuildconsultancy.com