How to bill for extra work without a signed change order

Your crew did work that is not in your contract. Nobody signed a change order. The superintendent pointed at something on Tuesday, your foreman handled it, and now it is the end of the month and you have to decide what to do with those hours.

This is the most expensive routine decision a subcontractor’s office makes, and most offices make it badly — either by eating the cost quietly or by slipping the number onto a pay application and hoping. There is a better sequence, and it starts with being precise about what you actually have.

This is process, not legal advice. What you are owed is decided by your subcontract and your state’s law. Read your notice clause, and when the number is big, call your construction attorney.

First, name what you have

“No signed change order” covers four very different situations, and they do not get handled the same way.

1. Verbal direction. A named person with apparent authority told you to do it. You have a person, a time and a conversation.
2. Written direction that is not a change order. An email, an RFI response, a sketch, an ASI, a field directive, a note in the GC’s project system. Stronger than people realize: not a CO, but a written instruction.
3. Constructive change. Nobody told you to do anything. Conditions, sequence or another trade’s work forced you into labor you did not price — stacked trades, a slab out of tolerance, three remobilizations because an area was never ready.
4. Nobody directed it and nobody forced it. Your crew did extra work on their own initiative, or fixed somebody else’s problem to keep moving. This one is the hardest to recover, and sometimes the right call is to log it as a lesson and move on.

Most offices treat all four as “unapproved extras” and give them the same shrug. Case 2 is often billable almost immediately; case 3 needs a record built over weeks. Filing them the same way is how the strong claim gets buried in the weak pile.

The clock you are already on

Nearly every commercial subcontract carries a notice requirement: written notice within some number of days of the event, in a named form, to a named person. Missing it is how good extras die. The work was real, the direction was real, the cost was real, and the notice was eleven days late.

Before anything else today:

• Find the notice clause in this subcontract. Not the prime contract, not the last job’s. Note the day count, who it goes to, and how it has to be delivered.
• Send notice even without a number. Notice of a change and a priced proposal are different documents, and the first does not wait on the second. “On the 14th we were directed by J. Alvarez to do X; we consider this a change to our scope; costs to follow” is the shape most notice clauses ask for — check yours for anything else it requires.
• Use the form the contract asks for. If it says written notice to the project manager, a text to the superintendent is not notice.
• Log the date you sent it. That date is the fact you will be asked for later.

Notice is cheap and reversible. If the GC comes back and says the work was always in your scope, you have lost nothing but an email.

Build the record today, not at closeout

Direction turns into money only if the facts of that afternoon are still provable months later. Capture them the same day.

• A T&M ticket per occurrence, signed in the field. Date, job, specific location, who directed it by name and time, labor by worker and classification, material and equipment with quantities, and one plain sentence on why it was extra. Our guide to running T&M tickets so they hold up covers the full anatomy, including what that signature does and does not mean.
• The daily log for that day, written as if a stranger will read it. Crew count, what the area looked like, who else was working in it, weather if it mattered. A log written for its own sake is the most credible document you own, precisely because it was not written to win an argument.
• Photos, wide enough to locate. A tight shot of a conduit proves nothing. The same conduit with a column line and a door opening in frame locates itself.
• The email thread, intact. A reply chain with timestamps beats your summary of it.

For a constructive change, the record is the claim. No single directive caused it, so what you are proving is a pattern: the same area, blocked repeatedly, documented on the day each time. That pattern only exists if someone wrote it down every day, which is the real reason daily logs matter.

Do not slip it onto the pay application

The tempting move is to add a line, or quietly inflate an existing one, and let the draw carry the extra work.

Do not. Three reasons, in order of how much they cost you:

1. Once your schedule of values is set, it is the billing basis. New money belongs in a change order that gets added to the SOV — there is no clean place for an unauthorized number to live.
2. It puts the whole draw at risk. A GC’s PM who finds an unapproved line does not strike just that line. They kick the application back, and the money nobody disputes waits another cycle.
3. It costs you the benefit of the doubt. A sub whose billing has always tied out gets heard. A sub who has been caught padding gets audited line by line for the rest of the job.

Bill unapproved extras as unapproved extras: a pending change order, in the log, with a status.

The three ways the money actually comes in

Bundle the tickets into one change order

The normal path, and it works more often than most subs expect. Gather everything that traces back to the same cause — one directive, one RFI, one late design change — and build one change order request from it. The package is the argument: here is the single thing that happened, here are the seventeen tickets it caused, here is the priced total, here is the notice we sent on the 15th.

One CO per cause is reviewable. Seventeen separate CORs is a backlog your GC’s PM will never work through, and a backlog is indistinguishable from a denial.

Convert it to force account or a T&M directive

If the GC agrees the work is extra but nobody wants to argue about price yet, ask for a directive to proceed on a time-and-material basis against the rate schedule in your contract. You keep working, the hours get tracked and signed daily, and the number settles as actuals rather than as an estimate. It is also the only clean way to handle work of genuinely unknown extent.

It only works if the rates were agreed up front — hourly by classification, material markup, equipment rates, standby. If they were not, you are negotiating markup on every ticket for the length of the job.

Preserve it and settle at closeout

Some extras will not resolve during the job, usually because the GC has not been paid for them either. That is a real answer, but only if the item stays alive: notice sent, cost documented, an open status and an owner in your change order log, raised in writing at every monthly meeting.

What is not acceptable is “we’ll deal with it at the end” as a filing system. By the end, the superintendent who signed those tickets is on another job and the GC’s PM has rotated off. Whatever is not in the paper did not happen.

What makes a retroactive CO approvable

The COs that get approved months after the work share five things:

1. One cause, clearly stated. Not a list of grievances.
2. A named person and a date for the direction, or a documented pattern for a constructive change.
3. Notice that was sent on time, in the contract’s form, with the date on it.
4. Cost detail that ties to the tickets — hours by classification, material at invoice, equipment by day, markup at the contract rate. Not a round number.
5. Timeliness. Submitted while the people who were there are still there.

Miss one of the five and you are negotiating. Miss three and you are asking for a favor.

The office habit that prevents all of this

One hour a week. Pull every open change event and every signed ticket that has not been rolled into a CO. For each one: is notice out, is the cost documented, and does it have a cause it can be bundled under? Then send what is ready.

That hour works because it happens while the evidence is fresh and the people are still on the job — the two conditions that decide every entitlement argument.

How SubMark handles it

Your GC uses Procore. You use a spreadsheet. There’s a better way — and this is exactly the gap a spreadsheet cannot close, because the evidence is created in the field and the billing happens in the office.

SubMark runs the whole chain:

• Change Events — crews log a scope change with photos and the responsible trades the day it happens, and it converts to a formal change order in one click. The record exists before anyone knows there will be an argument.
• T&M Tags — field tickets priced off your own rate lists and e-signed by the GC on the spot. Several tags convert into one change order, which is how you bundle by cause.
• Daily Logs — weather, narrative, labor, materials and photos, with a submit-and-review workflow. The corroborating record behind every ticket, written on the day.
• Change Order Tracking — build the COR, send the GC a link to review it, and take their redlines and decision in place. Status, aging and recovery tracked against contract value, so “what is still open on job 214” is a glance.
• Schedule of values and draw tracking — approved change orders are added to the SOV automatically, so a CO signed on the 3rd is billable on that month’s draw.
• Email intelligence on Outlook and Gmail — a GC’s reply on your change order surfaces on your Home page with a link back to the thread, instead of sitting unread in your inbox.

The two halves of that chain have a page each: change order management for the request and the decision, and T&M tickets for the field ticket that backs it up.

The trades that live on directed extras feel it most: electrical, plumbing and HVAC and mechanical.

Field users and the subs you invite are free and unlimited, which matters here more than anywhere — the whole process depends on foremen actually logging the change event and the daily log. See how pricing works.

The short version

• Name which of the four situations you are in before you do anything else.
• Send written notice today, in the contract’s form, even without a price.
• Build the record the same day: signed ticket, daily log, photos, intact email thread.
• Never hide an extra inside a pay application.
• Bundle by cause, submit one CO per cause, and submit it while the people are still there.
• Review open extras for one hour a week, every week.