It is never unclear which revision counts
Every file replacement creates a revision with a lineage: who replaced it, when, and what changed since the previous one. Only the current revision feeds checking and the assistant's answers; the older ones stay in the history.
Three revisions in the history, one answering
Each file replacement becomes a revision. The older ones stay readable; only the current one feeds checking, the assistant and the kiosk.
- rev. AhistoryFeb 11initial model
- rev. BhistoryFeb 28L2 changed to 14 cm
- rev. CcurrentMar 12V3 with a 6.15 m span
- Requirement checkingchecks rev. C
- Assistant and kioskanswer from rev. C
- What changedfrom rev. B to C, property by property
What stops happening in the office
- 01
The end of versions in file names
The revision belongs to the project, not to the file name. Nobody has to guess whether structure_rev_final2 is the good one.
- 02
What changed, property by property
Between two revisions, the screen shows which property changed on each element, before and after.
- 03
A draft does not become final
Publishing happens when the activity is accepted. Until then, whatever circulates shows as a draft.
- 04
A stamp that does not lie
A requirement checked against an older revision starts showing as out of date, instead of staying green.
A stage advances on evidence, not on a manual tick
NBR 13531, RIBA and Lei 14.133 tracks come configured. A manager can advance with a target still open, and the decision is recorded with author and reason.
- 01Concept design4 of 4 targets metmet
- 02Developed design6 of 9 targets · 2 requirements openin progress
- 03Technical designwaits for the developed design gatewaiting
Upload two revisions of your project and watch the trail appear
Tell us how revisions circulate in your office today. We reply by e-mail.
Request access