Upload and distribute a new drawing revision
v2026.3 · Updated 15 Sep 2026 · 6 min read
Every controlled drawing in SasCon keeps a revision history. When you upload a new revision it supersedes the previous one, the audit trail stays intact, and everyone on the distribution matrix is told. This article takes you through it twice over: first the upload, then the distribution.
Before you start
Where you do this
Documents → Register
You will need
The signed-off drawing file, and the revision letter from its title block
Takes about
Five minutes, plus review time
You need one of these roles:Document controllerProject administratorConsultants and sub-contractors can view the result, not publish it.
Walkthrough video not uploaded yet
Walkthrough · 4:12Watch it done — 4:12 walkthrough. Prefer reading? The written steps below cover the same ground.
- 0:00Opening the register
- 1:20Reading the title block
- 2:48Distributing
Step 1 — Upload the revision
Take this part slowly the first time. SasCon checks the file against the project numbering rule before anything is published, so nothing you do here is visible to the team until the checks pass.
- 1Open Documents → Register and type the document number into the register search box.
- 2Select the row for the document, then choose Actions → Upload revision. If that option is greyed out, the document is on hold.
- 3Drag your file into the upload panel. SasCon reads the title block and fills in the revision letter and revision date where it can.
- 4Check the revision letter, revision date and status against the drawing itself, and correct anything the title block reader got wrong.
- 5Write a revision note saying what changed. One sentence is enough, and it saves the next person opening both drawings to find out.
- 6Select Upload. The file is scanned and validated, then published to the register.
Screenshot not uploaded yet
Nothing is sent yet
The revision stays in Pending while validation runs. You get a notification either way, and no one is emailed until you distribute it in step 2.
Publishing supersedes the previous revision
The earlier revision moves to Superseded and can no longer be issued. It stays in the revision history for audit, so nothing is lost — but you cannot reverse the supersede yourself.
Field reference
| Field | Required | What to enter |
|---|---|---|
| Document number | Yes | Generated from the project numbering rule. Read-only once the document has been published. |
| Revision | Yes | Letters for design issues, numbers for construction issues. Follow whatever the previous revision used. |
| Revision date | Yes | The date printed on the title block, not today’s date. |
| Status | Yes | Preliminary, For review, or For construction. Ask the project manager if you are unsure. |
| Discipline | Yes | Decides which distribution matrix SasCon suggests in step 2. |
| Revision note | No | Strongly recommended. Appears in the revision history and on the transmittal. |
Step 2 — Distribute to the review team
Distributing creates a numbered transmittal. Recipients see the revision in their register straight away and get an email carrying your cover note.
- 1Open the published revision and select Distribute.
- 2Choose the saved distribution matrix for the discipline, or add companies and people by hand.
- 3Set what you need back — for information, for review, or for approval — and add a due date if a response is required.
- 4Write a short cover note and select Issue. Check the delivery log afterwards to confirm everyone received it.
Screenshot not uploaded yet
Related articles
Was this article helpful?
Version 2026.3 · Last reviewed 15 Sep 2026 by the SasCon documentation team