How to Document Change Directives in Construction

A superintendent gets the call at 6:15 a.m.: relocate the duct bank, start today, and keep the schedule moving. The owner’s representative may call it a field direction. The architect may call it a construction change directive. Your foreman may hear it as, “Just get it done.” Knowing how to document change directives is what keeps that verbal instruction from becoming unpaid work, a schedule dispute, or a fight over who authorized what.

A change directive is not the same thing as a fully executed change order. It usually tells the contractor to proceed before cost and time are agreed. That makes the record created in the first hours especially important. You are not just documenting extra work. You are establishing the scope, authority, conditions, cost basis, and project impact while the facts are still visible.

Start With the Directive, Not the Work

Do not let the field team begin change work based only on a verbal instruction if a written directive can be obtained. Ask for the construction change directive, architect’s supplemental instruction, field work order, revised drawing, email authorization, or other contract-recognized document. The exact name depends on the contract, but the practical question is simple: who directed the work, and do they have authority to do it?

When an instruction is verbal and the work cannot wait, document it immediately in the daily report. Record the name and company of the person giving the instruction, the date and time, the specific location, and the exact work directed. Follow that entry with a same-day written confirmation to the responsible project contacts. State that your crew is proceeding as directed and that cost and time impacts remain to be evaluated.

Keep the language factual. Do not write that the owner “approved” a cost increase unless they actually did. Do not label work as a change order before a change order is executed. A clean record distinguishes between direction to proceed and agreement on compensation.

How to Document Change Directives From Day One

Your record should be built around the change, not buried inside general project notes. Assign a unique tracking number and use it on daily reports, photos, labor tickets, equipment logs, correspondence, and pricing backup. If the directive later becomes a formal change order, that number gives the office a complete trail.

At a minimum, each change directive file should identify:

• The directive number, date received, issuing party, and source document
• The affected drawing, specification section, area, and original scope condition
• A plain-language description of the directed work and any exclusions or unanswered questions
• The expected labor, material, equipment, subcontractor, schedule, and access impacts
• The contract notice sent, the recipient, and the date and time it was delivered

This is not paperwork for paperwork’s sake. A vague entry such as “performed extra work at owner request” proves very little. A record that says “At 9:20 a.m., Owner’s Rep J. Smith directed relocation of 180 linear feet of installed 4-inch conduit from Grid B-7 to B-10 due to conflict with revised steel layout” gives the project team something they can verify.

Capture the Existing Condition Before It Disappears

Photos taken after demolition rarely explain why the work changed. Before the crew starts, capture the existing installation, the conflict, relevant dimensions, nearby grid lines, and drawing references. Use wide photos to establish location and close photos to show the condition requiring the change.

Add a short caption to every important image. A photo without context can be challenged months later. The caption should state what it shows, where it was taken, when it was taken, and why it matters to the directive. If the work is driven by an unforeseen condition, include scale references and photos of the surrounding area, not just the obstruction itself.

Field photos should support the written record, not replace it. A hundred unlabeled images are less useful than ten organized photos tied to a directive number and daily report.

Separate Changed Work From Base Contract Work

This is where many otherwise valid change claims lose strength. If the same crew is performing base scope and directive work in the same area, establish a practical way to separate the time. Use distinct cost codes, daily labor allocations, or time-and-material tickets. Identify each worker, classification, regular and overtime hours, and the specific changed activity performed.

The same rule applies to equipment. If a skid steer, lift, crane, or generator is used because of the directed work, log its hours, operator, activity, and rate basis. Track material by delivery ticket, purchase order, or field issue record. For subcontracted work, require daily tickets and supporting records from the subcontractor while the work is happening, not when the pricing deadline arrives.

There is a trade-off here. Overly detailed tracking can slow a small, low-risk change. But when the directive involves major rework, restricted access, overtime, acceleration, or a disputed scope boundary, broad estimates are not enough. Match the level of documentation to the exposure.

Protect Notice Rights and Schedule Entitlement

Most contracts require prompt notice for changes, delays, differing site conditions, and impacts. A directive may authorize work, but it does not automatically preserve your right to additional time or compensation for disruption. Read the notice clause before assuming an email is sufficient.

Send notice even if you do not yet know the full cost or duration. State what is known: the date of the directive, the affected work, the immediate impact, and the fact that the full time and cost consequences are under review. Update the notice as the impact develops.

Daily reports should document more than manpower counts. Record when crews were redirected, when planned work could not proceed, when access was restricted, when inspections were delayed, and when other trades were affected. Tie those events to the directive number. If a change forces out-of-sequence work or creates a stacking issue, describe the condition in plain jobsite terms.

Avoid unsupported schedule claims. Saying a change “delayed the project” is not the same as showing it affected a critical activity. Work with the project manager or scheduler to connect the field event to the schedule logic, milestones, and recovery measures. The field record supplies the facts. The schedule analysis explains entitlement.

Get Daily Verification When the Contract Allows It

For time-and-material work, daily signed tickets are among the strongest tools available. Present tickets promptly to the owner’s representative, construction manager, or other authorized reviewer. A signature may confirm labor and equipment were present, but it may not confirm final pricing or entitlement. Read the ticket language and avoid overstating what a signature means.

If the reviewer refuses to sign, do not abandon the record. Note the person’s name, the date and time, and the reason given, if any. Submit the ticket anyway and preserve proof of delivery. A refused signature is not ideal, but contemporaneous, detailed records still carry weight.

Do not let unsigned tickets sit in a foreman’s truck for a week. Late tickets invite questions about accuracy and make it harder for the other party to verify the work.

Keep the Field and Office Looking at the Same Record

A change directive becomes difficult to manage when the superintendent has photos, the foreman has labor notes, the project manager has emails, and accounting has invoices with no common reference. Centralize the directive file and make sure every team member uses the same number, description, and status.

A mobile field reporting process helps because records can be created where the work occurs, while conditions and conversations are fresh. The office should be able to see the directive, daily entries, photos, tickets, notices, and pending questions without reconstructing the story from texts and memory.

Review open directives in the regular project meeting. Confirm whether each item is awaiting instruction, underway, complete, priced, approved, disputed, or incorporated into a signed change order. This prevents field work from continuing for weeks under an unresolved directive.

Common Documentation Failures That Cost Contractors

The first failure is treating a directive as a casual request. If the person giving the instruction lacks authority, or the instruction conflicts with the contract documents, raise the issue promptly and document the response. Proceeding may be necessary, but silence can create avoidable risk.

The second is waiting until the end of the month to build the backup. By then, crews have moved on, site conditions have changed, and nobody remembers whether the lift was used for base work or rework. Same-day reporting is more credible and far less expensive than reconstruction.

The third is mixing opinion with fact. Document the direction, observed condition, labor used, and resulting disruption. Save accusations, legal conclusions, and emotional commentary for the appropriate internal discussion. Court-ready records are specific, professional, and consistent.

A change directive is where project control either holds or starts to slip. Document the instruction before work starts, capture the condition as it exists, track the changed work separately, and preserve notice as impacts develop. When the final pricing discussion arrives, the contractor with a complete field record is not relying on memory. They are relying on the jobsite facts.

Grant