How to document verbal change orders before the moment passes.
A GC says “go ahead and do it.” Your crew does the work. Without documentation at the moment of direction — not end of day, not end of week — that verbal approval becomes the sub's word against the GC's memory at invoice time. This guide covers why verbal change orders happen and what makes a record defensible.
Why verbal change orders happen
Verbal change orders aren't a failure of intent — they're a failure of process. Job sites move faster than paperwork, and the documentation gap is usually structural, not individual.
Job sites move faster than paper
A GC walks a floor with the sub, identifies an issue, and says handle it while you're here. Stopping the job to write a formal change order would delay the work and the schedule. The verbal directive is faster — and the documentation problem starts there.
Contractors assume someone else is writing it down
The GC assumes the sub will log the direction. The sub assumes the GC will generate a formal change order. Neither happens, and the work gets done on a handshake that neither party has documented.
Small additions don't feel worth the paperwork
A 10-minute task directed verbally doesn't feel worth stopping to document. But a project with 40 small undocumented additions adds up to real money — and none of it is individually worth fighting over after the fact.
Documentation workflow is too slow for field speed
If the documentation process requires going to the office, logging into a desktop system, or filling out a paper form, it doesn't happen in the field at speed. The documentation tool has to be as fast as taking a photo.
What makes a verbal change order record defensible
Three elements make a verbal change order record defensible when the GC disputes it later: a timestamp that precedes the work, documentation of who directed it and what specifically was requested, and — most importantly — contemporaneous GC acknowledgment rather than a retroactive dispute.
A paper T&M ticket filled out at end of day has no timestamp at the moment of direction, often lacks specifics about who directed what, and has no GC acknowledgment until invoice time. By then, the GC's memory of the conversation has faded and their incentive to dispute has grown.
A field event captured on a phone at the moment of direction — with a timestamp, photos of conditions, and the option to send a summary to the GC immediately — produces a record that is genuinely harder to dispute. The key is capturing it before the crew moves on, not after.
Timestamp
Captures when the direction was given, before work starts — not reconstructed from memory
Who directed it
Name and title of the GC or owner representative — specific enough to trace back
GC acknowledgment
A contemporaneous review link sent to the GC at capture time, not at invoice time
How Revecta handles verbal change order documentation
Revecta is built for the field-first documentation workflow — capture on a phone at the point of direction, with timestamped proof and a GC review link generated automatically.
Frequently asked questions
Are verbal change orders legally enforceable?
In most jurisdictions, verbal change orders can be enforceable contracts — but proving their existence and scope is the sub's burden. A timestamped record of what was directed, by whom, and when — created at the moment of direction — is far stronger than a recollection weeks later. This is a question your attorney should answer for your specific contract and jurisdiction.
What should a verbal change order record include?
At minimum: what work was directed, who directed it (name and title), when the direction was given (timestamp), and what the crew understood the scope to be. Ideally: photos of the conditions or work area at the time, and a follow-up acknowledgment from the GC at the earliest opportunity.
What if the GC denies ever giving the verbal direction?
A timestamped, contemporaneous record is harder to dispute than a recollection. If the GC is in the field when the direction is given, capturing the event immediately — before work starts — and sending a summary to the GC at capture time gives the sub contemporaneous documentation and puts the denial risk on the GC.
Should I refuse to proceed with verbal directives and require written approval first?
In theory, yes. In practice, refusing a GC's on-site direction risks the relationship and the project. The pragmatic answer is: proceed with the work but document the verbal directive immediately — at the point of direction, not at end of day — and get GC acknowledgment as soon as possible.