The drawing issue register: prove what you sent, and when
A transmittal is a covering note; a register is the record that survives the project. The columns to keep, a revision and status convention that holds as a job grows, and how to stop a contractor building off a superseded sheet.
- A transmittal is a covering note for one issue. A register is the running record of every issue on the project.
- The register is the document you'll want two years later, when nobody can remember which revision the contractor was working from.
- Revision letters before construction, revision numbers after. Status codes carry the intent; the revision only carries the sequence.
- The failure is rarely a missing drawing. It's a drawing that's present and out of date.
Ask a practice of four people where the latest revision of a particular sheet is, and you'll usually get a confident answer and a wrong one. Not through carelessness. The drawing exists, it was issued, somebody remembers issuing it, and the version in the folder looks right. It just isn't the one on site.
The register is the cheapest insurance in a studio. Ten minutes a week to maintain, and it answers without argument the only question that ever really matters after the fact: what did we send, to whom, and when.
Two documents often confused
A transmittal accompanies a single issue. It says: here are these eleven sheets, at these revisions, issued to you on this date, for this purpose. It travels with the drawings and it's addressed to somebody.
A register is cumulative and addressed to nobody. It's the studio's own running list of every drawing on the project and every time each one went out. One transmittal produces one row per drawing in the register.
Small practices tend to keep transmittals and skip the register, because the transmittal is the thing the client asks for. That's the wrong way round. A transmittal is useful for a week. The register stays useful for the life of the building, and for however long afterwards somebody might raise a question about it.
The columns that earn their place
A register with thirty columns will not get filled in. Keep it to the nine that answer real questions, and resist the urge to add a tenth.
| Column | What it holds | Why it earns its place |
|---|---|---|
| Drawing number | A-10-P-201 | The stable identity. It never changes, even when everything on the sheet does. |
| Title | First floor plan | So a human can scan the register without decoding numbers. |
| Revision | C, or 2 | Which version of that drawing this row is about. |
| Status | For construction | What the recipient is allowed to do with it. The single most useful column. |
| Date issued | 14 May 2026 | The fact everything else is argued from. |
| Issued to | Contractor, structural consultant | Who has it. Determines who must be told when it changes. |
| Purpose | Tender / approval / information | Why it went. Distinguishes a courtesy copy from a live instruction. |
| Medium | PDF, 2 prints, DWG | Matters when a dispute turns on what was actually usable. |
| Acknowledged | Yes, 15 May | The difference between sent and received. |
Nine columns, one row per drawing per issue. A sheet issued four times has four rows, not one row edited four times.
Studios get that last point wrong more than any other. The register is append-only in spirit: you add a row, you don't edit the previous one. Editing destroys the history, and the history is the whole product. An audit log works on the same principle, for the same reason: corrections belong in new entries rather than in overwrites.
Status codes carry the meaning
The revision tells you the sequence. The status tells you what the drawing is for, and it's the status that keeps people out of trouble.
- For information. Here is where we have got to. Do not price it, do not build it.
- For approval. We need a decision on this before we go further.
- For tender. This is the set contractors are pricing. Changes after this point cost money.
- For construction. Build this. The only status that should ever be on site.
- Superseded. This drawing has been replaced. Kept for the record, not for use.
A sheet can go out five times with the same drawing number and a different status each time, and each of those is a different instruction. A concept plan issued "for information" and the same plan issued "for construction" aren't two versions of one thing. They're two separate acts with very different consequences.
Numbering that survives a growing job
Every practice invents a numbering system on its first large project and regrets it on its second. The regret is always the same: the scheme had no room in it. Sheets called 01 through 40 are fine until the client adds a basement.
Use fields rather than a single running number. Discipline, level, type, sequence. Which letters you pick matters far less than keeping each field separate and leaving slack in each one.
| Field | Example | Meaning |
|---|---|---|
| Discipline | A | Architectural. S structural, M mechanical, E electrical, L landscape. |
| Level | 10 | First floor. 00 site, 01 ground, 10 first, 20 second. Leaves room to insert. |
| Type | P | Plan. S section, E elevation, D detail, Q schedule. |
| Sequence | 201 | Three digits, starting at 201 rather than 001, so there is space in front. |
A-10-P-201 reads as: architectural, first floor, plan, sheet 201. A basement added in year two becomes level 90 or level 05, and nothing else has to be renumbered.
For revisions, adopt letters before the set goes out for construction and numbers afterwards. Rev A, B, C through design and approval; Rev 1, 2, 3 once the drawing is a construction document. The change of character in the marker tells anyone glancing at a title block which side of that line the sheet sits on, which is information a letter or a number alone can't carry.
The superseded set
How it actually goes wrong: a revision goes out on a Thursday. The site engineer is on leave and the email lands under twenty others. The foreman is working from a print taken off Rev B, pinned to the site office wall since February. Nobody is negligent, nobody is lying, and the slab goes in at the old dimension.
The question afterwards isn't really about liability. It's about evidence. If you can show the drawing was issued, to whom, on which date, at which revision, with the status "for construction", and that it was acknowledged, you're in a straightforward position. If your record is an email thread and a memory, you aren't.
The failure is never a missing drawing. It is a present drawing that is out of date, and a present drawing carries all the authority of a current one.
Two habits shrink this to almost nothing. First, every superseded revision stays on the record rather than being overwritten, so the register can always show what was live on any given date. Versioned document sets do that by default: a replacement adds the new revision without discarding the old one.
Second, there's one place the current set lives and everybody knows it's the place. Not a folder that was shared once and has drifted since, but a workspace per client where the current revision is the one you see. The moment the answer to "which is the latest?" becomes "check your email", you've lost.
Running it without it becoming a job
A register nobody updates is worse than no register, because it looks authoritative and isn't. Keep the ritual small enough to survive a busy month.
Log at the moment of issue
The row goes in when the drawings go out, not at the end of the week. Ten seconds then; twenty minutes of reconstruction later.
One ten-minute pass a week
Reconcile what left the studio against what's in the register, and chase any acknowledgement still outstanding. Friday afternoon, same time every week.
Re-issue the whole set at each stage change
When the job moves to tender or to construction, issue the complete set at current revisions rather than the deltas. It costs one transmittal and it resets everyone to the same baseline.
Close it at handover
The register goes to the client with the as-built set. It's part of the deliverable, and a practice that hands one over looks materially different from one that doesn't.
On the smallest jobs a spreadsheet is enough, and anyone telling you otherwise is selling something. It stops being enough at roughly the point where more than one person in the studio issues drawings, because a shared spreadsheet has no way of noticing that two people edited the same row. If you're at that point, think about what the practice runs on rather than adding another tab.
One last thing, slightly outside document control but bearing on it directly. Your register is also the record of what you licensed and when, which matters if a question ever arises about who owns the drawings. And a register showing a set was issued against a stage payment is quietly useful when a fee conversation turns awkward.
One place the current set lives
AtelierLab keeps every drawing filed by client and project, with versioned replacements that preserve the full revision history and a record of what was issued and when. Bring the formats you already work in, no conversion.
Questions, answered
The questions architects ask most about this, in plain language.
Ask us anythingA transmittal is a covering note for a single issue, addressed to a specific recipient, listing the drawings and revisions being sent and the purpose of that issue. A register is the studio's own cumulative record of every drawing on the project and every occasion each one was issued. One transmittal generates one register row per drawing. If you can only maintain one, maintain the register, because a register can reconstruct what a transmittal said but a folder of transmittals cannot reconstruct a register.
Use letters before the drawings are issued for construction and numbers afterwards: Rev A, B, C through concept, preliminary and approval, then Rev 1, 2, 3 once the sheet is a construction document. The change of character tells anyone reading a title block which side of that line the drawing sits on. If your consultants work to ISO 19650 you will see the same idea as P01 and C01 prefixes with a separate suitability code, and it is better to follow their convention than to run two on one job. Either way, keep the revision separate from the status, which is what actually says whether a drawing is for information, approval, tender or construction.
Longer than feels necessary. Questions about what was issued tend to surface years after practical completion, often when the building changes hands or a defect appears, and by then nobody's memory is worth anything. Keep every superseded revision rather than overwriting it, so the register can always show which drawing was live on any given date, and hand a closed register to the client with the as-built set at completion.
That depends on the contract and the facts, and it is a question for your lawyer rather than for an article. What is within your control is the evidence. If you can show the current revision was issued, to whom, on what date, with a construction status, and that it was acknowledged, your position is straightforward. If the record is an email thread and a recollection, it is not. The register exists to make that difference.
Yes, though it can be small. Even on a single house the set will go through tender and construction revisions, and the question of which drawing the contractor was working from can still arise. A spreadsheet with the nine columns is sufficient at that scale. It stops being sufficient at the point where more than one person in the studio issues drawings, because a shared spreadsheet cannot tell that two people edited the same row.