Change order backup documentation: a complete worked packet

Begin with the decision the packet needs

An inbox full of photos is not yet a change-order submission. The reviewer needs to understand what changed, why the sender believes it is additional work, what amount or time is requested and which records support that request. Put those questions on the cover before collecting more attachments. This gives the packet an organizing purpose and exposes missing information early.

Use a stable identifier that follows the event from the field account through the request and later revisions. Include the project, trade, location, title, preparation date and current revision. Keep the sender's internal event number distinct from a general contractor's request number or an owner's formal change number. A cross-reference prevents similar identifiers from being mistaken for the same approval state.

State what you are asking the recipient to do. A request for confirmation of observed quantities differs from a request for scope review or a negotiated price decision. If several decisions remain open, identify each and its responsible role. The cover should not imply that a field acknowledgment, permission to continue or receipt of an email automatically resolves every commercial question.

Set the boundaries of the worked example

Consider fictional Cedar Office project event EC-17. An electrical crew reports rerouting conduit above corridor C after a revised coordination drawing. The proposed packet covers the described reroute during one shift. It excludes a possible later return visit and any time-related request, both of which remain unpriced questions. Those boundaries prevent an apparently precise total from concealing incomplete scope.

For this example only, assume the preparer has documented 18 incremental labor hours at an assumed composite rate of $72, $420 of materials and four equipment hours at $45. A $120 material credit applies. Assume the example's agreed estimating convention applies a 10% markup to the net direct subtotal. These are invented teaching assumptions, not market rates or a statement about any contract's allowable charges.

Before using the structure on a real job, identify the actual pricing method and permitted cost components. Lump-sum pricing, unit prices and force-account work require different supporting detail. Resolve the basis with the appropriate project representative. Do not turn an illustrative worksheet into a claim that a particular rate, markup, credit or work direction is contractually valid.

Give the reviewer an index and a short chronology

Create an attachment index that answers what each record is and why it is included. A useful index has a reference, description, date, version and connection to the request. Avoid attaching an entire email archive without indicating the relevant message. The reader should be able to follow the scope narrative into the original source without guessing which file the preparer meant.

For EC-17, the proposed index could identify A1 as the revised coordination drawing, A2 as the instruction correspondence, A3 as the daily field account, A4 as resource records, A5 as location-tagged photos and A6 as the calculation. Those labels are examples. Preserve the actual issuing and observation dates separately from the date you assemble the packet; compiling a file today does not make it a contemporaneous record.

Add a concise chronology: what the crew understood before the change, when the revised information arrived, when the reported work occurred and when the request was prepared. Flag gaps instead of smoothing them away. If the field account does not establish who issued an instruction, name that as a clarification question. A clean story should remain faithful to uneven source evidence.

Connect the scope difference to the instruction

Describe the difference between the relevant baseline and the reported additional work. “Conduit change” is too broad to assess. A better description identifies the corridor, route affected, drawing references and actual operations: removing a described segment, installing the revised route and making the associated connections. Keep the language within the facts the records support.

Link the instruction to its source and preserve its wording in the original record. In the narrative, distinguish what the message expressly says from what the crew understood it to mean. An RFI answer may explain a technical detail without settling a price. An individual may acknowledge an event without authority to approve an extra. Ask the responsible administrator to resolve that distinction.

Show the baseline record as well as the revision when the comparison matters. If the original scope already included part of the activity, explain the proposed incremental portion and any credit. Avoid presenting the entire day's installation as additional merely because it occurred on the same shift as the reroute. Reviewers need a defensible boundary between ordinary contract work and the amount being requested.

Preserve the field facts and their limits

The daily account should identify the reported activity, location, date and resource use, with links to supporting records. Preserve its author and original submission time. If the preparer asks a later clarification, retain both the original and the dated response. This allows the reviewer to distinguish a same-day observation from an explanation assembled after the event.

Caltrans provides a specific public-owner example: its force-account procedure calls for original daily observations and appropriately detailed records, with later clarifications dated when written. That procedure is not a universal form for private construction. It illustrates why provenance and timing matter. Use your project's own required documentation and review process when building the actual packet.

For EC-17, an account saying “three workers rerouted conduit” does not establish 18 incremental hours by itself. The preparer must identify the time basis and separate other work during the shift. If a foreperson can only confirm an estimate, label it accordingly. Do not convert uncertainty into exact measured hours or create signatures that were never obtained.

Sources: Caltrans Construction Manual: Section 3-9, including force-account records

Reconcile labor, materials and equipment separately

For labor, show the category, incremental hours, rate reference and calculation. If a composite rate includes burdens or other components, identify the basis so the reviewer can check for overlap. Keep sensitive payroll details in the appropriate controlled source rather than broadcasting them in a general email attachment. Provide enough reference information for the authorized reviewer to verify the line.

For materials, connect quantities to purchase or issue records and explain the proposed charge basis. A supplier invoice can show a purchase without proving that all purchased material was installed in EC-17. Identify returns, stock transfers, unused quantities and credits. If a credit is still pending, state its status and avoid treating an expected credit as a confirmed accounting entry.

For equipment, identify the asset or rental reference, use period and rate basis. Distinguish operating time, rental duration and any other requested category under the actual pricing rules. In our fictional packet, four hours at $45 produce $180; the worksheet should not also add the same cost through an undisclosed labor rate component. Check the whole packet for duplicate recovery before submission.

Make the amount traceable and arithmetically complete

The illustrative calculation starts with $1,296 labor, $420 materials and $180 equipment, producing $1,896 in direct cost. Subtracting the assumed $120 material credit leaves $1,776. Applying the example's assumed 10% markup to that net subtotal produces $177.60, for a requested total of $1,953.60. The table makes each step inspectable instead of hiding it inside a lump sum.

This calculation demonstrates reconciliation, not eligibility. On a real job, the applicable agreement may use another base, different markups, limits or a different pricing method altogether. Identify the approved basis and have the authorized reviewer assess it. A spreadsheet formula can be perfectly correct while applying the wrong commercial rule.

Add a version note when a line changes. If a later verified material credit becomes $150 rather than $120, retain the original submission, identify the new source and recalculate the affected subtotal and markup. Explain the amount difference in the transmittal. A revised total without a change summary forces the reviewer to compare every line and increases the chance of reviewing an obsolete worksheet.

Use photos and acknowledgments for their actual purpose

Select photos that help locate and explain the work. Identify the capture date if known, location, view direction and connection to the described operation. Keep the original file and use a clearly labeled annotated copy when marking the route. A tightly cropped after photo may show a finished installation but omit the condition that prompted the change.

Explain what each acknowledgment represents in your process. Procore's T&M support documentation provides tasks for ticket creation and signature requests, demonstrating that digital field records and signatures are established workflows. The meaning of a particular signature still depends on the record and project terms. Do not summarize every acknowledgment as approval of price or entitlement.

If the recipient declines to sign, preserve the actual response and route the issue through the agreed process. Do not insert a name, infer acceptance from silence or rewrite a disagreement into a neutral confirmation. The packet can document what was reported and what remains disputed. Accuracy is more useful to a reviewer than a falsely complete approval trail.

Sources: Procore support: T&M Tickets

Run a review before the packet leaves the office

Have someone other than the preparer follow the amount from the cover to the source records. Ask them to identify the requested scope, reproduce the total and find any stated exclusions. If they cannot answer those questions without the preparer narrating the packet, revise the index and references before adding more attachments.

Check common inconsistencies deliberately: drawing versions, work dates, duplicate ticket references, overlapping labor, credits, rate bases and mismatched totals. Review whether each file opens for the intended recipient and whether the shared location exposes unrelated confidential records. A broken link is a receiving problem even when the preparer's local copy looks correct.

Use an exception list instead of delaying every submission until every uncertainty disappears. Identify unresolved questions, the person responsible and the requested response. Follow the project's notice and submission requirements through the appropriate administrator. Preparing backup is one part of that process; a useful evidence packet should not be mistaken for proof that every required communication has occurred.

Track the next decision without rebuilding the packet

Send the request through the agreed destination with its identifier, revision and specific decision sought. Retain the transmittal and receipt information. Track a request for missing evidence separately from a scope disagreement or a price negotiation. This lets the team improve the submission rather than repeatedly sending the same general reminder.

Connect later questions to the same packet. When a reviewer asks for a material explanation, assign that action and preserve the response with its source. When a formal change is issued, cross-reference it without erasing earlier versions. Keep approval, billing eligibility and payment as distinct events so the evidence record remains useful to the project and finance teams.

Bring a redacted packet to a Buildalytic workflow demo: one field account, one unanswered clarification and the desired office handoff. Its custom-workflows offering is a starting point for discussing intake and follow-up around your existing tools. Ask the demonstration to show how an exception reaches the right person and how the original evidence stays connected, then confirm the implementation scope.

Sources: Buildalytic custom workflows