Organize is enabled per organization, and as of September 2026 it is off for new and existing accounts by default - the platform still groups documents into version chains and records stages automatically, you just won't see the tab. Everything on this page describes the tab itself. If you need it, talk to us.
The parts you keep either way are in the project's Files panel: setting a document's stage, and adding or removing a document from a version chain, are both on its right-click menu.
Organize
A project accumulates documents. Three revisions of the architectural set, a consultant's package, the specs, a re-issue of two sheets. Organize is where you tell the platform how those relate - and where it tells you what it worked out on its own.
Use case: a set arrives named ARCH_REV3_FINAL_v2.pdf and you need it recognised as revision 3 of the architectural set, not a new document.
Version chains
A version chain is the sequence of revisions of one set. Chains are what Compare Versions needs to know which two documents to diff, so getting them right pays off immediately.
The platform proposes chains automatically from filenames, dates and content. In Organize you can:
- Link a document into an existing chain.
- Unlink one that was chained wrongly.
- Reorder a chain when the revisions aren't in the order the filenames imply.
- Re-detect - run the automatic pass again after uploading several documents at once.
The version chain editor
Reorganise
For a project that's grown messy, Reorganise proposes a complete restructure rather than making you fix chains one at a time. It shows you what it wants to change; nothing moves until you accept. A project can be re-detected and reorganised as often as you like.
Project stage
Record where the project is - the stage vocabulary is your organization's, so it matches how your firm actually describes phases - with an optional percent complete.
This isn't bookkeeping. Stage steers how the platform reviews: a design-development set and a construction-documents set warrant different expectations of completeness, and Spec Audit in particular is aimed at the CD phase. Recording the stage stops a 50% set being marked against a 100% standard.
Where the platform inferred a stage rather than reading it off the drawings, it says so and marks it as a guess - so you know which ones are worth confirming instead of having to re-check them all.
Per-sheet revision history
The sheet view shows what actually changed, sheet by sheet, across the whole chain - a heatmap of churn.
This is the fastest way to answer two questions people ask constantly:
The per-sheet revision heatmap
- "Which sheets have been reissued the most?" - usually where the coordination problem is.
- "Has anyone touched this sheet since rev 1?" - the sheets that never move can be trusted; the ones that move every revision want a closer look.
For a written description of what changed between two specific revisions, use Compare Versions. Organize tells you where to look; Compare Versions tells you what changed there.
The timeline
A chronological view of the project's document history - what arrived when, what superseded what, and which phase each landed in. Useful for reconstructing the record when a job has been running for a year and nobody remembers what came in before the last permit set.
Spreadsheet revisions
Where a chain's documents are spreadsheets rather than drawings - a schedule reissued three times - Organize will diff them directly, so a changed value in a fixture schedule shows up as a change rather than a new file.
Organize is switched on per organization, and enabled for most accounts. If you don't see it, talk to us.