A quantity revision must identify the design version and measured section without replacing acceptance of an earlier activity.
Index
The same construction activity can have executed, checked and accepted quantities at different times; merging them makes progress claims hard to explain.
The rule that changes the scope
A quantity revision must identify the design version and measured section without replacing acceptance of an earlier activity.
An existing module works if execution and review are separate; custom development can support work-front allocation and drawing revisions.
A useful comparison keeps contracted, executed and accepted quantities in independent columns. A design adjustment may change the planned quantity without changing work already completed. Request a section-level export to check those relationships outside the system. If financial integration is involved, define that later handoff explicitly: technical acceptance should not be confused with issuing an invoice or settling a payment obligation.
Specify operational deliverables
- Record the unit, section and drawing version associated with every submitted quantity.
- Allow only the disputed line to be returned while other measurements remain under review.
- Link approval to the reviewed version and retain who recorded the discrepancy.
Test the exception before acceptance
In a hypothetical scenario, a drawing changes while a measurement awaits review; separate work completed against the old drawing from the new estimate.
Reference for assessing scope
NN/g: writing task scenarios for usability testing
Prepare your project with Quantum9
Bring a returned measurement, its drawing and the people responsible for execution and review.