REASON_LABELS defines the seven reasons. The agreement renders all of them as a checkbox list with only the selected one filled, exactly like the paper form it was modeled on, so the customer sees the reason in context rather than as an isolated label.
Also called: reason for change · who asked for this · site condition · code required
- 1The reason is chosen in the change order editor.
- 2The agreement renders every reason with a Check component, checked only for the chosen one.
- 3The same labels are reused by the admin viewer and the signing modal.
The document is described as 'modeled on Chris's paper "Change Order Agreement" template but fully generated'. Rendering the whole checklist rather than only the selected reason is what keeps it recognisable as the same instrument builders already use — and it makes 'this was your request, not my error' visible on the page the customer signs.
- Change orders with no recorded cause
- Disputes over whether a change was requested or a correction
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 →