Who has sheet E-37,
and which revision.
On most jobs that question takes three emails. Here one register knows: every sheet, every revision with its reason, who it went to and when. It is fed from SDS/2 every hour, so it is never a day behind the model. Transmittals go out in one approval.
- Registerevery sheet on the job, main and miscellaneous, erection and shop
- Revisionmark, date, reason, and what changed since the last issue
- Holderwho was sent which revision, and when; who is still on an old one
- Transmittalbuilt from the register, approved once, sent, logged
- Reasonwhy each sheet was revised, written by the detailer who revised it
- Ask"who has sheet E-37, and which revision?"
One register,
kept by the job
The register is not typed. It is read from the model and the approvals, so it cannot drift from either.
Fed
Every hour the register reads SDS/2: which sheets exist, which were revised, what the detailer wrote as the reason.
Revised
Every revision is logged with its mark, date and the reason the detailer wrote, and what changed since the last issue.
Approved
A transmittal is built from the register. One person approves it, with their name, and it goes.
Answered
Who has what, at which revision, since when: read from the register, not from memory or a spreadsheet.
What a person
still does
The register records. People decide what goes out.
- 01Approves every transmittal.Nothing leaves the office on the register's say-so. A named person approves each one.
- 02Writes the reason.Why a sheet was revised is written by the detailer who revised it, in words your approver will read.
- 03Not yet.It tracks our sheets. Drawings from the engineer or other trades are filed with the job but not revision-tracked by the register.
Never ask which revision again.
Send one package. Every sheet in it is on the register from the day it is drawn.
Start a package— contract drawings and specs
— your shop standards
— the sequence or phase
— the date you need it

