Work changes on real jobs. A condition is not what the drawing showed. An owner asks for a different finish. A trade finds a conflict that an RFI cannot fully settle. None of that is unusual. What gets expensive is treating a conversation in the dirt as if it were already an approved, billable change.

This is not legal advice, and it is not a claim about how every contract works. Your contract, and a construction attorney when the dollars matter, tell you what has to be in writing and when you may proceed. The filing habit is simpler: a verbal field agreement still needs a written change record before the extra work is treated as approved and billable.

Paper first, in practical terms

When extra work is requested or discovered, write down the following in the job file the same day: the date and area; who asked for it, or what condition triggered it; a short description of the work; what is known so far about cost and time; what document will carry it; and whether you have been told to proceed, and by whom.

That note is not the executed change order. It is the start of the record. Follow it with the pricing, the official form, and the signed document as they come, and file each one in a Change Orders folder, named with the date and the number.

Do not rely on a text message or a "go ahead" shouted over a saw. If the direction was oral, confirm it in a short written note the same day and file that note. A simple change log, even a tab in the same spreadsheet as your RFI log, helps: number, date, source, description, status (proposed, directed, executed), and a link to the PDF. Work already in place, with a status of "we still need a signature," should be obvious.

The miss this prevents

Here is how this usually plays out.

An owner or a designer, standing in the space, asks for a change. The superintendent agrees it makes sense and tells a sub to proceed so the schedule does not slip. The work gets done. Weeks later, when the cost shows up on a pay application, someone asks where the change order is. The people who were in the room remember the conversation differently. The extra work is now an argument, and maybe unpaid work, instead of a documented change.

The cost takes a familiar shape: the labor and material, the time spent reconstructing the conversation, and the strain on the next payment. The change itself was never the problem. Doing the work as if the paper already existed was.

How to run it in the job file

Give change documents their own folder in the Google Drive or Dropbox job file, and keep proposals, directives, and executed change orders clearly named so they do not look like the same thing. The executed copy is the one that belongs in the record of what was approved. Drafts and pricing sit beside it, not on top of it.

Tie changes back to the current set. If a change revises a sheet or follows from an RFI, the current drawings and the binding RFI packet should point to it, and the people doing the work should get a short notice. I cover that distribution habit in "Distribution: Who Gets the Update, and How You Prove It."

Arizona jobs already have enough schedule pressure from heat and monsoon days. A rushed "just do it" is understandable. The written confirmation keeps that rush from turning into a payment fight later. Check the contract for notice rules, and talk to a construction attorney when a missed step would hurt.

If the work already got ahead of the paper

If you have extra work already in place and a thin file behind it, start the written record now: dates, photos, who directed it, and a draft change document. That is cleanup, not a time machine, but it beats waiting until the pay application is rejected.

I can set up the job file and the change log, run document control on a retainer, or prepare closeout. If you want help, bring the unofficial change that is worrying you and whatever paper you have.

The files stay yours. This is a filing habit, not legal advice.

If you want help, not just a checklist

Some jobs run fine on a clean file and a superintendent who gives the log fifteen minutes twice a week. Others do not: revisions are moving fast, closeout is already behind, or the field simply has no hours left for paperwork.

That is where I come in. I set up the job file, run the logs on a retainer, or prepare closeout before the scramble starts. Your files stay yours, and there is no software contract to sign.

Email travis@builtonrecord.com Get the free Job File Kit