A per-business threshold in invoice settings. A change order at or above it requires a signed agreement; below it, no signature is needed. The policy function returns not just the answer but a sentence explaining it, which the interface shows verbatim.
Also called: do I need a signature for this · small extras · signature threshold · $400 outlet
- 1signaturePolicyFor(total, threshold) returns { thresholdUsd, required, because }.
- 2The comparison is at-or-above, not above, so a $5,000 threshold catches a $5,000 change order.
- 3A null threshold means every change order requires a signature, and the explanation tells the builder where to set one.
A build is running, the customer asks for one extra outlet, and dragging a signing ceremony behind $400 stalls the day. The same ceremony skipped on a $40,000 slab is a dispute with no paperwork behind it. Each business sets the dollar figure above which a signature is required — and until they set one, every change order needs signing, because a threshold invented on their behalf would quietly let real work start unsigned. A change order landing exactly on the number counts as needing one, since that is the figure somebody will inevitably type.
- Signature friction on trivial changes.
- Significant work starting on an unsigned change order.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →