Revisions and traceability
Immutable snapshots, revision notes, duplication and review.
The revision system is what makes a calculation defensible months later.
The principle
The panel states it plainly: every explicit save keeps an immutable input and result snapshot.
A revision records the inputs and the outputs at that moment. Change an input later and save again, and you get a new revision — the old one is not overwritten. The calculation behind an issued report can always be recovered exactly as it was.
Saving a revision
- Write a Revision note — the field asks what changed?
- Click Save Revision
Fill in the note. Updated soil parameters after receiving lab results costs seconds and answers the question a reviewer will ask.
Revision history
Every revision is listed with its number, its note and who saved it when. The header shows the current revision.
The other actions
| Action | Effect |
|---|---|
| PDF summary | Exports the calculation as a document |
| Duplicate | Copies it as a new calculation — useful for a variant |
| Submit for Review | Sends it for checking |
Duplicate rather than editing when testing an alternative — you keep both results side by side instead of burying one in revision history.
Submit for Review
Moves the calculation into review. As with laboratory results, design work should be checked by someone other than its author before it is issued.
Status
Calculations show Draft until approved. Anything supporting an issued report should not still be a draft.