The remainder statement

Five lines any rule, product spec or policy should declare: what it drops, how much, who reconciles it, who pays, and when the rule itself fails.

Before a rule runs, it should admit what it drops and how much of that to expect. It should name who reconciles each dropped case, who pays for that, and the ceiling at which the rule itself goes under review. Once filed, the statement gives the people doing the reconciling something to measure their load against.

Who can implement it, and at what level

burden The burden — the rule works only because someone else absorbs a cost it never counts

Who can implement it. The budget holder and the rule owner. Naming a custodian without funding the role moves the cost; it does not declare it. The ceiling needs someone obliged to act when it is crossed.

Who can use it, what it needs, how it fails, and the evidence

An institution-run intervention. An office has to run it, and only that office can act on the result. A copy filed outside the office is a request, not the change.

Who can use it. Whoever writes or reviews a rule, product spec or policy before it runs, and whoever will absorb what it drops. It needs an estimate of the dropped cases and a named role with budgeted time.

The statement acts on the burden: it makes the absorbed cost visible before the rule runs and names who pays it. The rule changes only if the invalidation ceiling obliges someone to reopen it.

Resources and dependencies
  • An estimate of dropped cases, stated so it can be wrong in public.
  • A named custodian with budgeted hours, not an unnamed team.
  • A review date and a person obliged to act at the ceiling.
Likely failure modes
  • A statement filed once and never reviewed.
  • A custodian named but not funded, so the person the rule dropped still reconciles it.
  • An invalidation ceiling no one is obliged to act on.
  • An estimate treated as a promise instead of a guess.
Observations that would count as evidence
  • The declared volume against the observed volume.
  • The custodian's actual hours, and who paid for them.
  • Whether the ceiling was crossed and what happened, with a date.
  • Whether the rule, the custodian or the funding changed.

Authority note reviewed 2026-11-09.

Run it on a real case: Robodebt (Australia, 2015–2019)

named as circumstances, not as an error rate

an estimate, published so it can be wrong in public

the role that reconciles each dropped case, counted as work

who pays for the reconciling

the volume at which the rule, not the cases, goes under review

Who pays when the estimate is blown?

Without JavaScript, Run submits this page: what you typed is sent to the site and comes back in the address.

The result

A worked example, until you change something above.

Remainder statement

filed against Eligibility as the portal can see it, of A benefits agency

  1. 1 · Circumstances droppedSeasonal income in lumps the eligibility window cannot see; employers who keep no records the portal acceptsnamed as circumstances, not as an error rate
  2. 2 · Expected volumeAn estimated 3.2% of otherwise eligible claimantsan estimate, published so it can be wrong in public
  3. 3 · Designated custodianA case worker with a discretionary budget, paid for the reconcilingthe role that reconciles each dropped case, counted as work
  4. 4 · Incidence / payerThe institution's budget covers the reconciliation costwho pays for the reconciling
  5. 5 · Invalidation ceilingIf non-conforming cases exceed 5%, the category is suspended and rewrittenthe volume at which the rule, not the cases, goes under review

The rule drops the circumstances above. It will be wrong about them in public, at the volume estimated, and the reconciling counts as work. A blown estimate is the rule's to answer for.

Filed. The reconciling is budgeted, the estimate is public, and the ceiling sends the rule — not the cases — under review when it is blown. The cost is declared before the rule runs.

Serve this to the institution that owns the rule. It is a filing, not a suggestion: select and copy the document, and the address bar is the shareable record of exactly what was declared. Naming does not reverse the routing — it stops it being automatic, which is the difference between an anomaly and a blown estimate.

A run, copy, print or shared link is a usage signal. It shows the instrument reached someone. It does not show that a rule, decision or institution changed.

Used this on something real? Email me what changed, when, and where it’s written down. Leave out names and anything private. I’ll only publish what I can check.

To fill in by hand, in a meeting or a hearing: Burden transfer ledger, a printable page.

Say something to this page

This box reaches a person. It binds nothing.

Send

The statement is argued in The Rule Works. She Doesn't Fit..

Where the claim is argued

Next instrument: The residual read