FIELD NOTE · ALLOWANCE

Watching an allowance burn down

An allowance drawn down by the change orders you've tagged against it — and no meter at all until you've tagged something.

What it reads
The allowance line an approval letter authorized, and every change order tagged against it.
What triggers it
The tagged drawdowns cross 80% of the authorized amount — the default threshold.
What it needs from you
Nothing to act on by itself. It is a running balance, based on what has been tagged so far — not a finding.
Every figure, date, and party in this article is illustrative — drawn from a fictional "Project A" case built to be realistic, not a real client, GC, or project.

The exhibits

Three change orders, tagged against the allowance in the order they landed. Each rung is one tag — nothing is drawn that was not tagged.

Drawdown 1

The first change order tagged against this allowance.

CO #029 was tagged to the allowance line: "Lobby feature wall, stone substitution per owner selection."

CO #029 · this drawdown$78,400Illustrative figure

Running total, based on tags: $78,400Illustrative figure of $240,000Illustrative figure authorized.

Drawdown 2

A second change order, tagged against the same line.

CO #035 was tagged next: "Exterior blade signage, revised letter set and illumination." The running total is the sum of every tagged change order so far — nothing else.

CO #035 · this drawdown$52,900Illustrative figure

Running total, based on tags: $131,300Illustrative figure of $240,000Illustrative figure authorized.

Drawdown 3

A third change order — this is the one that crosses the 80% threshold.

CO #044 was tagged last: "Level 1 wayfinding, added directory and code signage." Tagging it is what crosses the default 80% threshold — the threshold fires on the tag, not on any judgment about the work.

CO #044 · this drawdown$71,250Illustrative figure

Running total, based on tags: $202,550Illustrative figure of $240,000Illustrative figure authorized.

The ladder stops here. It says nothing about whether what remains is enough — only what has been tagged so far.

The check, in full

One authorized allowance, drawn down by the change orders somebody has tagged against it — and nothing else.

Authorized$240,000Illustrative figure
  1. CO #029 · Lobby feature wall, stone substitution per owner selection$78,400Illustrative figure
  2. CO #035 · Exterior blade signage, revised letter set and illumination$52,900Illustrative figure
  3. CO #044 · Level 1 wayfinding, added directory and code signage$71,250Illustrative figure
  4. Not drawn$37,450Illustrative figure
The track is the authorized amount. Each numbered part is one change order somebody tagged — there is no other way a dollar gets in here.
  1. The allowance line comes from a verified approval letter — the same figure the letter itself prints.
  2. A drawdown is a change order a human has tagged against that allowance line. Nothing is drawn from it automatically.
  3. The drawn total is the sum of the tagged change orders. It reads as "based on tagged change orders" every time it is shown, because a pay application may verify a different number.
  4. The 80% threshold is our own shipped default, not an industry standard — a team can tune it.

What does NOT trigger it

  • A change order that touches the same package but has not been tagged to this allowance line.
  • An allowance with no tagged drawdowns at all — no meter renders for it, because there is nothing to measure yet.
  • A pay application total. The product does not verify billed amounts against this figure.

This is a deterministic sum, not a model's estimate — the same tagged change orders produce the same total every time.

What this does not do

It does not decide
It reports a running balance based on what has been tagged. It does not say the allowance is over budget, and it does not say anyone did anything wrong.
The blind spot
A change order can touch this same scope and never get tagged to the allowance line — the dataset used to build this article has 46 change orders in total, most of them untagged to any single allowance. An untagged change order contributes nothing here, ever, silently, forever — not a smaller slice, not a rounding error. That is why the figure never draws a slice for it: there is nothing to draw.
The precondition
It only shows a track at all once at least one change order has been tagged. An allowance nobody has tagged anything against shows no meter, no remaining figure, and no "0% drawn" — a 0% bar would say we checked and found nothing; the truth is nobody has tagged anything yet, and those are different statements.
No score
There is no percentage printed on the track, because a proportion of a quantity the system only partly knows is not evidence — it is a running tally, qualified every time.

Your call

$202,550 of a $240,000 allowance is drawn — and every dollar of it is a change order somebody tagged.

What the rep does next

The owner's rep checks whether any recent, untagged change orders on this package should be tagged to the allowance before the runway gets any tighter.

See it run on one of your projects.

30-day pilot. One active job. I'll show you exactly what it would have caught on a project you already know.

Request a Demo