# Why Extra Work Goes Unbilled on Construction Jobs

> The crew did the work and the hours were real. What went missing was the record from that week, and the change order request was written without it.

By Vlad Shvets, Partner @ Qvery · Published 2026-11-18 · 13 min read
Canonical: https://qvery.ai/blog/extra-work-unbilled-change-orders/

Extra work on a job site often starts with someone asking for it on the spot. The general contractor's superintendent or the owner's representative points at the wall or the trench, and the crew does the work that day, because the schedule will not wait for a signature.

A change order, the signed change to the contract's scope, price or time, comes later.

What gets written down that week is thin. When a project manager sits down to build the change order request, these are the records waiting for them.

- A daily log line that names the floor and nothing else: no room, no crew, no name of whoever asked for the work.
- A time and materials ticket (a T&M ticket, the daily sheet of hours and materials) still waiting for a signature.
- A photo of a scribbled note, somewhere in a text thread.
- The extra hours booked to the base job, because nobody had a code for the change yet.

Then the general contractor or the owner asks for the breakdown and the backup, the records that prove who asked, when, and for how many hours. The hours nobody can place come off the request.

On the example worked out below, a contractor of about 200 people with 120 field workers loses **$181,440** a year this way, for work its crews really did.

> At Qvery, we help contractors stop losing money on extra work their crews did, with custom AI agents that read each week's logs and tickets and build the change order backup.

## Extra Work Starts Before the Paper Does

Under A201, the standard general conditions published by the American Institute of Architects (AIA), the work changes through a signed change order, through a construction change directive that lets the work go ahead before the price is agreed, or through a minor change that moves neither price nor time. AIA's own checklist adds that no work should proceed on a verbal instruction alone.

On site, the person who asks is often not the person who can approve a change. Approval sits with a project manager, who may need the owner, and the answer can take weeks. Meanwhile the trench is open and the crew is standing in it.

- **97%** of specialty trade contractors sometimes start extra work before the change order is approved
- **42%** do it on more than half of their changes
- **Two-thirds** still write their time and materials tickets on paper

Source: Dodge Construction Network, survey of US contractors for Clearstory, a change order software company (2026)

The usual advice is to stop the crew until someone signs, and to discipline the foreman who doesn't. I think it's right and I wouldn't build a business on it. A rule that asks foremen to act as clerks in the middle of the day works for a month.

What holds is a record good enough to bill from, made the same week the work happens, whoever ends up writing the request.

## The Backup Gets Built Weeks After the Work

When the request finally gets written, the project manager pulls three weeks of daily logs from two superintendents, the timesheets where the extra hours went to the base job's cost code, a stack of tickets with one unsigned, and whatever emails mention the change. Then they try to make it one story.

Dodge Construction Network's survey, run for Clearstory, put numbers on how long that takes. From a signed ticket to a priced change order request: **22 days** on average. From the request to a signed change order: **26 more**.

That is close to two months, and it counts only the tickets someone signed.

![One change from work to signature: the work on day one, a thin log line, an unsigned ticket, a priced request 22 days after the signed ticket, a signed change order 26 days later.](https://qvery.ai/blog/extra-work-unbilled-change-orders/illustration-change-order-gap.webp)

*Dodge’s 2026 survey for Clearstory puts about seven weeks, on average, between a signed ticket and a signed change order.*

On the other side of the table, the general contractor's reviewer has the contract open. A201's standard terms accept a lump sum only when it is "properly itemized and supported by sufficient substantiating data to permit evaluation", and the reviewer checks exactly that: who directed the work, the hours times the rate, a signed ticket, logs that agree.

In the survey, **53%** of general contractors named thin backup as a reason they cut or hold back change order payments, second only to disputed prices.

There is a clock on the contractor too. A201 gives a contractor **21 days** from the event, or from first spotting the condition, to start a claim, and owners edit that window: one city's copy for a community center build cuts it to ten. A request rebuilt in week six can miss a notice deadline nobody was counting.

## The Records That Hold Up Were Made That Week

Months later, when a change is questioned, the records don't carry equal weight. Each one proves something specific and leaves something else open, so the strongest backup is several of them saying the same thing.

**What each record proves when a change is questioned**

| Record | What it proves | What it leaves open |
|---|---|---|
| Written direction: an email or a signed field directive | Who asked for the work, and when | How long it took |
| A signed T&M ticket | The crew, hours and materials that day | Whether the work was outside the contract |
| A daily log that names the place, the crew and who directed it | Who was there and what ran | Very little, if it names only the floor |
| Timesheet hours coded to the change | Each worker's hours, day by day | The direction behind them |
| A dated photo | The condition before and after | Hours, or who gave the order |

Records that contradict each other do more damage than missing ones. A log that shows six on the crew and a timesheet that shows four hand the reviewer a reason to cut the whole day. Spotted in the first week, the mismatch takes one call to the superintendent, who still remembers the day.

Small extras follow the same rule at a smaller scale. Two hours of a favor can ride on next week's larger change order, if someone kept the two hours.

Where they are lost, the cleaner fix is a line in the contract: small items documented by email or text within a day and billed at the contract's rates, with prior approval kept for the larger ones.

**Tips**

> Any emailed direction will always hold up in cost disputes. Photos of the conditions with a markup in an email is a golden ticket. Daily logs I’ve seen used to backup man hours on a T&M ticket.
> ([r/ConstructionManagers · Feb 2026](https://www.reddit.com/r/ConstructionManagers/comments/1quha0s/when_disputes_come_up_later_what_documentation/o3a6haw/))

> Cost disputes generally require emailed directive or signed tags combined with daily reports and pictures.
> ([r/ConstructionManagers · Feb 2026](https://www.reddit.com/r/ConstructionManagers/comments/1quha0s/when_disputes_come_up_later_what_documentation/o3c9vor/))

> Consistent! Documentation that conflicts and contradicts itself is worse than no documentation
> ([r/ConstructionManagers · Feb 2026](https://www.reddit.com/r/ConstructionManagers/comments/1quha0s/when_disputes_come_up_later_what_documentation/o3fgkgx/))

## Half an Hour a Week Is $181,440 a Year

Take a contractor of about 200 people. At specialty trade contractors, construction trades held about **60%** of the jobs in May 2025, by the Bureau of Labor Statistics count, so call it **120 field workers**.

Say each of them loses half an hour a week of extra work to the gap: an hour on a favor every other week, a ticket that never got signed, a morning booked to the base job. That half hour is our assumption, and your own written-off and denied requests will tell you whether it is low.

The rate is what your contract lets you bill. An hour of a construction worker costs a private employer **$46.65** with benefits (BLS, June 2026), and California's highway contracts pay extra work on time and materials at full labor cost plus a 35 percent markup. That makes **$63** an hour, before equipment and materials.

That is **2,880 hours** a year and **$181,440** of work done and never billed. If our agents get 40% of it onto change order requests, which is our assumption because they can only find work some record mentions, that is **1,152 hours** and **$72,576** a year.

They run for about $450 a month, so the return after running cost is **$67,176** a year, and every $10,000 of the build is earned back in **1.8 months**.

Put your own crews and your own contract rate in.

(An interactive calculator on the page: roi-unbilled-extra-work.)

The calculator counts only work that never reached a bill. It leaves out the project manager's days spent rebuilding backup, and the billed work that gets cut or written off later: **77%** of specialty contractors in the Dodge survey have written off change order work as bad debt.

> Unbilled extras get treated as a field discipline problem, and the fix is a talk with the foremen. The talk wears off in a month. What doesn't wear off is someone reading the records the same week, while the superintendent still remembers who asked and the ticket can still be signed. That's the first job I'd hand to agents: the crew is paid already, only the paper is missing.
>
> Vlad Shvets, Partner @ Qvery

Change order backup is one of [several paperwork jobs a contractor's office still does by hand](https://qvery.ai/blog/ai-agents-for-contractors/), and our Construction Playbook prices it next to the others for a company your size.

Industry Playbook: https://qvery.ai/industry-playbooks/ai-agents-for-construction/

## Qvery's Agents Build the Backup the Week the Work Happens

The agents we build for a contractor's project office start when a superintendent's log or a project manager flags a potential change. From that day they read the daily logs, typed or photographed from a handwritten page, the timesheets, the machine hours, the T&M and haul tickets, the owner's emails and field directions, and your contract's changes article and rate sheet.

For every day of the extra work they tie the hours, machines and loads to the change and keep base-contract hours out, unless the timesheet and the log put them at the change. Where the log, the timesheet, the ticket and the machine disagree, they keep both figures with their pages.

They also sort each direction by what it is (a signed directive, an email, a word on site) and count the days to the first written notice the way your clause counts them.

What your project manager gets is a dated timeline of who asked, who worked and what ran, each line pointing to the page it came from, and a list of what is missing, each gap naming the record that would close it. Found in the first week, a gap can often still be closed: the ticket signed, the email confirming the direction sent.

Work nobody wrote down anywhere stays invisible to the agents, as it does to anyone else. What they recover is the work some record mentions and nobody put together in time.

![Logs, timesheets, tickets and emails go to Qvery’s AI agents, which tie each day to the change, flag records that disagree and count notice days; the project manager decides.](https://qvery.ai/blog/extra-work-unbilled-change-orders/illustration-change-order-agents.webp)

*The agents assemble the backup from your own records each week; your project manager decides what to claim.*

On the sample company we built for the free try, a made-up civil contractor of 230 people, the agents found **$16,202** of work in the records that the draft request left out, four unsigned tickets, and written notice **11 days** after the slab was found. They report the eleven days and leave the reading of the clause to the contractor.

If you have a change from a recent job, send its daily logs and a line on what the extra work was.

Free report: construction/change-order-documentation

> A daily log, a timesheet and a ticket for the same day should tell one story, and often they don't. The log can list the excavator all day while its engine hours say it ran for three. Our agents keep both figures with their pages and never pick one. Your project manager decides which is right, before the owner's reviewer finds the gap.
>
> Piotr Babel, Partner @ Qvery

## What Stays With Your Project Manager

> 🛑 **What the agents never do** They never price the change, contact the owner or the general contractor, call a notice late or on time, treat a photo as proof of hours, or guess a handwritten word, which they mark unknown. Nor do they make a record. They point to the ones your crews made, so the backup is only as strong as the week it was made in.

Daily logs carry your crews' names and hours. Before anything is built, the access is set down in writing: which files the agents may open and where they are processed. Every finding is logged with the page it came from. Qvery AI OÜ is an EU company, and how your people's names are handled is part of the contract you sign.

## Backup on Every New Change by the Third Week

Your superintendents keep writing their logs the way they do now. In the first week we learn their format, your timesheet codes, your ticket books and the change forms your owners expect, which takes about three hours of one project manager.

Qvery's Agents Back Up Every Extra the Week It Happens: https://calendly.com/qvery-vlad/30min

From the third week, each new potential change has its backup started the day it is logged, and about half an hour of a project manager's time goes into checking it instead of building it.

Each week we count what this job is for: changes with backup started that week, tickets found unsigned while there was still time to sign them, and extra-work hours that reached a request instead of the write-off column.

## Frequently asked questions



### What is a change order in construction?

A written agreement that changes a construction contract's scope of work, its price, its schedule, or any mix of the three. Under the AIA's standard terms the owner, the contractor and the architect sign it, and it becomes part of the contract. Work beyond the original scope without one is, on paper, a favor.

### What should a change order include?

A description of the change clear enough for someone who was not there, the drawings or specification sections it affects, the change to the contract price and the contract time (even when one of them is zero), and the signatures. Attached to it, or ready when asked, sits the backup.

### What is change order backup?

The records that prove a change and its cost: who directed the work and when, the hours by trade and day, the equipment and materials, and the rates the contract sets. The AIA's standard terms accept a lump sum only when it is itemized and supported well enough to evaluate, so the backup is what gets the number accepted.

### What is a construction change directive?

A written order from the owner, prepared by the architect, that tells the contractor to go ahead with a change before the price or the time has been agreed. The amount is settled later, by a lump sum, unit prices or cost plus a fee. Signed by the contractor, it becomes a change order; either way, the hours still have to be proven.

### Can a contractor get paid for extra work without a signed change order?

Sometimes, depending on the contract and on how the work was directed. Many contracts pay nothing without written approval, and some require notice by a set method within a set number of days. Late or informal changes do get paid, often after a negotiation and for less than asked. For a specific case, your counsel decides.

### How long does a contractor have to give notice of a change?

As long as your contract says. The AIA's A201 gives 21 days from the event, or from first spotting the condition, whichever is later, to start a claim, and owners edit that number: one city's copy cuts it to ten days. Subcontracts set their own windows. Our agents count the days the way your clause counts them, with the arithmetic shown.

### What is a T&M ticket?

A time and materials ticket is the daily record of extra work: the date, the crew, the hours by worker or trade, the equipment and the materials. Someone the general contractor has authorized signs it on site, ideally the same day. An unsigned ticket found in the first week can still be signed; at closeout, whoever could sign it may be on another job.

### Is a signed ticket enough to get paid?

It proves the hours and the work done that day. It does not prove by itself that the work was outside the contract, which is the question a reviewer asks first. Written direction from someone with authority, an email or a signed field directive, belongs beside it, and a daily log that agrees with both.

### How small is too small to write up as a change order?

There is no fixed line, and many contractors let small extras go to keep the relationship. The cost is that nobody tracks the total. Keep every extra in the record, fold the small ones into the next larger change order, and agree in the contract how small items are documented and billed.

### Do our superintendents have to change how they keep daily logs?

No. The agents read the logs where they already sit, whether a log app or scans of handwritten sheets. The gap list shows your superintendents which details the requests keep missing, and better logs make better backup from there.

### What if our daily logs are handwritten?

A photo of a handwritten page counts the same as a typed entry. Every handwritten page is read as an image, and a word, date or figure the agents cannot make out is marked unknown and shown with its page, never guessed.

### Does this work for a general contractor as well as a subcontractor?

Yes. A general contractor builds backup for its own change orders to the owner and reviews its subcontractors' requests. The agents set a subcontractor's claimed hours against the general contractor's own logs for the same days and keep the difference, priced at the subcontractor's rate.

### What do the agents cost each month?

On this article's example, about $450 a month: model usage for each change backed up, plus hosting, the record of every finding and upkeep of your contract's rules. The build is a fixed price for a defined result, agreed before any work starts, and every $10,000 of it is earned back in 1.8 months on the example.
