Not just drawings. Every register a project runs on, with the contractor, subcontractors and client working from the same current revision.
Transmittals run in sequence against the project's own prefix, and a number is never reused.
The next revision is worked out from the code the client gave, under the scheme the project set.
Who approved what, and when, kept after the fact — including the submissions that were sent back.
Filed against the register under their own revision, not on a shared drive in a folder named final.
Raise a request against an ITP, route it for internal approval, and send the client the form they already use — with the drawings, test reports and the ITP itself attached to it as one PDF.
A document runs through letters while it is being agreed, then numbers once it has been. The code the client returns decides which. CMXDocs works out the next revision so nobody has to remember the rule.
| Code | Means | Next revision |
|---|---|---|
| A | Approved | A → 0 |
| B | Approved with comments | A → 0 |
| C | Rejected, resubmit | A → B |
| D | For information | 0 → 1 |
| AFC | Approved for construction | 0 → 1 |
One scheme, shown. A project sets its own, and the register follows it.
Accounts are set up by your Admin. If you need one, ask them — or get in touch and we will point you the right way.