A change order sounds like formal paperwork, and on a small job it rarely looks like one. It usually shows up as "while you're in there, could you also..." — a request that feels small in the moment, gets agreed to keep things friendly, and never gets written down anywhere. Multiply that across a job, and the gap between what was quoted and what actually got done can be significant, without a single moment where it felt like a big decision.

Why unpriced scope changes hurt more than obvious overruns

A job running over budget on materials at least shows up as a number somewhere. Scope creep is quieter — extra work absorbed for free doesn't look like a cost overrun on the job costing; it just looks like the job took longer and used more materials than expected, with no obvious reason why. The margin damage is identical, but the cause is invisible unless every scope change is deliberately logged as one.

What actually counts as a change order

  • Extra work not in the original quote — an additional socket, an extra section of fencing, a second coat that wasn't specified.
  • A material upgrade the client requests mid-job — a better-spec fitting or finish than originally priced.
  • Existing conditions that change the plan — rot, damp or wiring found once work's underway that wasn't visible at quoting.
  • A timeline change that costs money — a client asking to pause and resume later, or compress a schedule that adds overtime or extra plant hire days.

Any of these, agreed verbally and never written down, is a change order that's happening without being tracked as one.

The habit: note it the moment it's agreed, not at invoicing

The fix isn't a heavyweight change-order process for every small tweak — it's a quick, contemporaneous note the moment something extra is agreed: what's changing, roughly what it'll cost, and that the client's aware. Even a one-line note against the job, logged the same day, is enough to turn "I think we agreed to something extra" into a clear, dated record by the time the final invoice is written.

A worked example

Say a bathroom refit is underway and the client asks, mid-job, to also replace a section of flooring that wasn't part of the original quote. Agreed verbally and left untracked, that flooring work either gets absorbed for free or becomes an awkward, undocumented add-on at invoicing that the client barely remembers agreeing to. Logged the day it was agreed — what's changing, materials needed, extra time — it becomes a clean, defensible addition to the final invoice instead of a dispute waiting to happen.

Small changes still deserve a note, even if they're not billed separately

Not every change needs a formal repricing — a genuinely minor addition might reasonably be absorbed as goodwill. Even then, a quick note logged against the job means that if several "small" changes happen across one job, the pattern is visible rather than each one disappearing individually into a job that just quietly took longer than quoted.

How Site Wallet handles this

A note, extra cost or additional receipt can be logged against a job at any point as scope changes come up — so a mid-job addition is captured the moment it's agreed, not reconstructed from memory when the final invoice is being written. Over time, that also builds a record of which types of job tend to generate the most scope creep, which is exactly the detail worth building into how similar jobs get quoted next time.

FAQ

Do I need the client to sign off on every change order?

For anything beyond a genuinely trivial addition, a written or clearly documented confirmation — even a text message — protects both sides and avoids a dispute later, more so than a verbal agreement nobody wrote down.

What if I don't want to charge for a small extra?

That's a reasonable call to make — the point of logging it isn't necessarily to bill for it, it's to keep visibility of how much "free" extra work a job actually absorbed, so the pattern is a decision rather than something that happened by accident.

How is this different from a job simply running over budget?

An overrun is often a cost that was always part of the original scope, just underestimated. A change order is genuinely new work that wasn't quoted at all — different cause, and a different fix: requoting the addition rather than just tightening the original estimate.