Revision Control
Revision control ensures that every version of a document is preserved, traceable, and clearly identified. In Kazinex Workflows, each upload to a document record creates a new revision — a distinct, immutable snapshot of the file at that point in time. The current revision is always the latest approved (or latest uploaded, if none are approved yet).
What a revision contains
Each revision record stores:
| Field | Description |
|---|---|
| Revision code | The identifier for this version (e.g. P01, A, Rev 2) |
| File | The uploaded file — stored in the configured storage provider |
| Filename | The original filename as uploaded |
| File size | Recorded at upload time |
| Change description | Free-text note describing what changed in this revision |
| Uploader | The member who uploaded the file |
| Upload timestamp | Exact date and time of upload |
| Storage provider | Which provider holds this file (Supabase, SharePoint, or R2) |
| Status | The document status at the time this revision was current |
Uploading a new revision
- Open the document detail page (click the document title in the Register).
- Click Upload New Revision.
- Fill in the revision fields:
| Field | Required | Description |
|---|---|---|
| Revision code | Yes | Unique code for this revision. Must be different from all previous revisions of this document. |
| File | Yes | The new version of the file. Drag and drop or click to browse. |
| Change description | Recommended | What changed from the previous revision. Appears in the revision history. |
| Status | No | You can optionally change the document status as part of this upload (e.g. set to For Review to indicate this revision is ready for routing). |
- Click Upload.
The new revision becomes the current revision immediately upon upload. The previous revision is retained in the revision history.
Revision code conventions
Kazinex does not enforce a specific revision code format — your organisation sets its own convention. Common patterns:
| Phase | Draft codes | Issued codes |
|---|---|---|
| Preliminary | P01, P02, P03 | A, B, C |
| For Construction | C01, C02 | FC-A, FC-B |
| As Built | AB-1, AB-2 | R0, R1 |
Set the convention in your project's document control plan and communicate it to all team members. The system validates uniqueness but not format.
Viewing revision history
On the document detail page, click Revision History (or the Revisions tab). The full history shows every revision ever uploaded, in chronological order, with:
- Revision code
- Upload date and uploader name
- File size and filename
- Change description
- Download button for each historical revision
Historical revisions cannot be deleted — they are permanent records.
Superseding documents
When a new revision is approved, the previous revision (and its document status) is automatically marked Superseded. This makes it unambiguous which revision is the current approved version.
A document can also be superseded by a different document — for example, when a drawing is replaced by a reissued drawing under a new number. In this case:
- Open the superseded document's detail page.
- Go to Document Relations → Add Relation.
- Select relation type Supersedes and choose the new document.
Both documents are linked and the old document shows the supersession in its relations panel. See Document Relations for details.
Restoring a revision
Project Admins can restore a previous revision to be the current revision (for example, if a revision was uploaded by mistake). The action is logged in the document's event history as "Restored to current."
Restoring does not delete any revisions — it simply designates a historical revision as the current one.
What's next
- Document Statuses — how status interacts with revision approval
- Document Locking & Confidentiality — lock a document to prevent further revisions
- Document Relations — link related documents, supersessions, and references