Design review

Every drawing numbered, reviewed and on the record

From the first draft to the frozen issue, a drawing carries its package, its discipline, its number and every verdict anyone gave it.

Structure before speed

A register only helps if everything in it is classified the same way.

Packages group the drawings that are issued together; disciplines and drawing types classify each one inside them.
Document numbers are generated from the project, package and discipline codes, so nobody is inventing a filename.
The register shows package, discipline, author, current version and lifecycle status on one row, and filters on any of them.
A drawing missing its discipline, type or package is flagged as unclassified until all three are set.
A draft's file belongs to its author alone — reviewers see the row and everything about it, but not the document until it is submitted.

Draft, internal review, sent to client, approved, frozen — and the two ways back.

A drawing moves draft → internal review → sent to client → client approved → frozen, and only along transitions its holder is permitted to make.
Two distinct kick-backs: the studio requests changes internally, the client returns a drawing for revision. They read differently everywhere because they are different events.
A submission can be cancelled and an internal rejection withdrawn, so a mis-click does not become part of the record.
A drawing sent back cannot re-enter review until the corrected file has actually been uploaded.
Uploads are blocked while a drawing waits on a reviewer or sits with the client, so nothing changes under someone mid-review.
Act on a whole selection at once — a mixed selection offers only the actions every drawing in it can take.

Internal iterations and issued revisions do not share a number.

Ver counts what the studio produced; Rev counts what the client has been sent. An issued drawing counts on both.
A new version is cut only when the file it replaces has been through review — a correction on top of an unreviewed upload stays where it is.
A revision is cut when the drawing is sent to the client: Rev 01, Rev 02, and on.
The upload dialog says which number the file will carry before you commit to it.
Any two revisions open side by side, so the change between them is looked at rather than remembered.

Comments land on the document, not in an email about the document.

Drop a pin anywhere on the page and hold the discussion there, with threaded replies underneath it.
Mark up with the pen tool or with rectangles and circles, in the colour and weight you choose.
PDFs, images, spreadsheets, Markdown and plain text open in the same viewer, with a thumbnail rail for multi-page documents.
Pins are listed beside the drawing, filtered and resolved as the rework lands.
The client reviews in that same viewer, sees the same pins, and approves or returns the drawing from it.

The trail a drawing leaves is the answer to what happened.

Link a drawing to the BOQ lines it prices, and move between the two from either side.
Each drawing carries its own activity timeline — uploads, submissions, verdicts, freezes, in order.
If the file changes while you have it open, the review says so rather than letting you review the wrong one.
All of it lands in the project audit log alongside the rest of the project's history.

Access is by invitation. Tell us about the studio and we'll set you up.