A field decision everyone agrees on, with nothing in writing, feels efficient on the day it happens. The owner or the designer is standing there. The superintendent knows what will work. A wall moves, a door gets added, or a route gets shifted so the work can keep going. Weeks later, when the cost shows up on a pay application, the memory of that handshake is not enough. One side remembers an approval. The other remembers a discussion. Without a paper trail, the change turns into a fight.

What follows is a typical case, not a specific job. The dollar figures are examples.

This is not legal advice about how to write a change order. Read the contract, and talk to a construction attorney when the dollars matter. The filing habit is simpler: if it changes the work or the price, write it down the same day.

How it usually goes

During a walkthrough, the owner asks to move a wall, add an opening, or change a finish "while the crew is already here." The superintendent agrees it can be done. Maybe a designer, on the phone or on site, says that sounds fine. Everybody nods, and the crew does the work. It is good work, and it is extra work.

Nobody writes an RFI. Nobody sends a short confirmation email. Nobody sketches the change, dates it, and files it. The daily report, if there is one, may mention the walkthrough but not the decision.

At the next pay application, the cost shows up. The owner is surprised, or remembers the conversation differently, or says they thought it was already in the scope. Now you are trying to reconstruct a handshake from memory, a few photos, and a crew's time ticket. The work was real. The record was not.

What that costs (example figures)

Often the painful number is not rework. It is work you already did and may not get paid for, or the time you spend arguing about it. A handshake change of this kind might represent $8,000 to $40,000 in labor and materials that are now in dispute, depending on what was built and how long it took. Call it a ballpark, not a quote.

Even if you eventually get paid, the item sits, the argument can slow a pay application, and an owner who feels billed for something they "never approved" starts watching every line. Sometimes the dollar figure is smaller than that example range, and you absorb it to keep the peace. That is still a cost.

The basic controls that would have caught it

You do not need to stop making field decisions. You need a paper trail the same day you make them.

Write it down before the crew is gone. A short email or a field directive, the same day, is enough to start: what was decided, who was there, what will change, and that a price will follow if the contract requires one. Send it to the people who were in the conversation. File a copy in the job folder.

Follow the contract's change process, even when the decision was friendly. Many contracts want a written directive or a change order before extra work proceeds, or at least prompt written notice. I am not telling you which clause governs your job. I am telling you that a handshake does not replace that process.

Note it in the daily report, and take a dated photo of the condition before and after, named and filed. Close the loop with a price and a signature as soon as you reasonably can. I walk through why unnamed photos fail later in "Photos That Can't Prove What You Think They Prove."

If field decisions are outrunning the paperwork

Owner-operators and superintendents who are still hands-on make decisions in real time because the job demands it. That is not the problem. The problem is a week with no time to write them down.

If that sounds like your job, I can set up the job file, run the logs and the change paper on a retainer, or prepare closeout. A handshake is not a change order. The work still happened. The file has to say so.

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