Construction Submittal Register Template

Submittal action codes, register of shop drawings, product data and samples with planned, due-back and needed-on-site dates, weekly review

ConstrucciónBrevesubmittal registerActualizada 29 oct 2026

Abrir en el editorDescargar .md

Cómo usar: Use it at the start of a construction job to track every submittal the specifications require. Fill planned rows from the specifications first, working back from the needed-on-site date. The main pitfall is ordering or installing before the submittal returns with an action code that allows it.

Vista previa

Submittal Register: [Project name]

A register for tracking construction submittals (shop drawings, product data, samples, test reports and other documents the contractor submits for the design team's review) from planned date through review to the final action. Based on common construction contract administration practice. Replace every [bracketed] value and every row marked Example. Contract terms decide what needs review and how long review takes; this is not legal advice.

Field	Value
Project	[Project name and number]
Contract	[Form of contract and clause that governs submittals]
Contractor	[Company]
Reviewer of record	[Architect / engineer / contract administrator]
Contract review period	[Example: 10 working days per submission]
Register owner	[@document-controller]
Last updated	YYYY-MM-DD

1. Action codes

Code	Meaning (Example)	Next step
A	No exceptions taken	Proceed
B	Make corrections noted	Proceed, incorporate comments; no resubmission unless asked
C	Revise and resubmit	Do not proceed; resubmit
D	Rejected	Do not proceed; submit a new proposal
I	For information only, no review	File

Many contracts state that review does not relieve the contractor of responsibility for meeting the contract documents. Check what your contract says about the effect of review.

2. Register

Submittal no.	Rev	Spec section	Description	Type	Planned submit	Actual submit	Due back	Returned	Code	Needed on site	Status
SUB-001 (Example)	0	05 12 00	Structural steel connections	Shop drawings	2026-11-02	2026-11-04	2026-11-18	2026-11-17	C	2027-01-11	Resubmit
SUB-001 (Example)	A	05 12 00	Structural steel connections	Shop drawings	2026-11-25	2026-11-24	2026-12-08	2026-12-04	B	2027-01-11	Released for fabrication
SUB-002 (Example)	0	08 71 00	Door hardware sets	Product data	2026-12-01	n/a	2026-12-15	n/a	n/a	2027-03-01	Not yet submitted
SUB-003 (Example)	0	09 91 23	Interior paint colours	Samples	2027-01-15	n/a	2027-01-29	n/a	n/a	2027-04-05	Not yet submitted
SUB-[NNN]	[0]	[Section]	[Description]	[Type]	YYYY-MM-DD	YYYY-MM-DD	YYYY-MM-DD	YYYY-MM-DD	[Code]	YYYY-MM-DD	[Status]

Example project: the fictional Fernhollow Library and Learning Centre (code FHL), as in construction/rfi-log. Due back = actual (or planned) submission date plus 10 working days.

3. Weekly review

Overdue submissions (planned date passed, not submitted): [list].
Overdue reviews (due back passed, not returned): [list, escalate per contract].
Items at risk (needed on site within lead time plus review time): [list, with mitigation].
Resubmissions open: [list].

Standard and licence note

Based on common construction contract administration practice for submittal management. Specification section numbers in the example use the MasterFormat numbering pattern published by CSI and CSC (official text: CSI, purchase or licensed access: https://www.csiresources.org/). All text and the fictional example are original. Template licence: MIT.

Plantillas relacionadas

Construcción