Required Fields in a Revision Register
- Drawing number — unique identifier matching the title block
- Drawing title / description
- Current revision letter or number
- Date of current revision
- Submission date — when submitted to EOR
- EOR review status — In Progress, Submitted, Approved, Approved as Noted, Revise and Resubmit
- Date returned from EOR
- Fabrication release status — Not Released, Released for Fabrication, Superseded
- Date released for fabrication
- Prior revision history — all prior revisions with dates and disposition
How to Use the Register in Weekly Reporting
The revision register is the most useful weekly project report you can give a fabricator. A register that shows 3 drawings returned 'Revise and Resubmit,' 12 drawings 'Approved as Noted' pending release, and 2 drawings awaiting EOR response past the required date gives the fabricator a complete picture of where the project stands — without requiring them to interpret a narrative status update.
Maintaining the Register in Real Time
A revision register that is updated weekly is better than none. A register updated in real time is the standard to aim for. Every time a drawing is submitted, a response is received, or a revision is issued, the register should be updated the same day. A one-week lag in a fast-track project can mean two releases go out without the register being current — and if a superseded drawing reaches the floor in that window, the register would have prevented it.
How Drawing Packages Are Reflected in the Register
On projects with phased or packaged drawing releases, the revision register should include a column tracking which release package each drawing belongs to — PKG-01, PKG-02, or a phase designation like Foundation Package, Level 1 Framing, Roof Framing. This allows the fabricator to filter the register by package and confirm that all drawings in a package have reached the same approval and release status before committing material to that package. A package where 14 of 15 drawings are approved but one is still 'Revise and Resubmit' should not be released to the floor as a complete package.
Tracking EOR Review Response Times in the Register
A well-constructed revision register also records the date a submittal was sent to the EOR and the date comments were received. This two-date tracking makes EOR review duration visible. Most structural specifications allow 10 to 14 business days per review cycle. When the register shows a submittal has been with the EOR for 18 business days without a response, that is a documented delay — and a basis for notifying the GC that the fabrication schedule is being affected by the review cycle. Procore, e-Builder, and Aconex all have native submittal tracking modules that can serve this function when kept current.
Linking the Register to the CNC File Release Record
For projects where CNC files are a major deliverable, the revision register should include a CNC release column showing whether the NC files for each drawing's members have been issued to the fabrication equipment at the same revision as the drawing. A drawing at Rev B that still has Rev A NC files on the drill line is a production risk that the register should make visible. This linkage — drawing revision to CNC file revision — is particularly important when a drawing revision changes only hole patterns and the visual difference between Rev A and Rev B drawings is subtle.
Register Format and Access
The revision register should be shared with all project parties in a common-access format — a Procore submittal log, a shared Excel file with controlled access, or a dedicated field in the project's document management platform. It should never be a file that only the detailer can see. The fabricator, GC, and EOR should each be able to query the register independently to answer questions about drawing status without routing through the detailer's PM. Access parity prevents information asymmetry and the blame disputes that follow when a party claims they were not notified of a revision.