# 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.

<!--
Guidance: How to use this template
- Build the register from the specifications at the start of the job:
  every section that asks for a submittal gets a planned row before
  work starts, with the date it is needed on site.
- Work back from the "needed on site" date: lead time for manufacture
  and delivery, plus review time set in the contract, plus a margin for
  one resubmission.
- Common pitfall: ordering or installing before the submittal is
  returned with an action that allows it. Record the action code before
  procurement is released.
- Questions that are not submittals go to the RFI log
  (`construction/rfi-log`); a review comment that changes scope, cost
  or time goes to change control (`construction/change-order-variation`).
-->

| 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

<!-- Guidance: Use the codes defined in your contract or specification; the ones below are a common pattern, shown as an example. -->

| 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

<!-- Guidance: One row per submission; a resubmission keeps the number and adds a revision letter. Spec section uses your specification system (for example MasterFormat in North America or Uniclass or NBS in the UK). -->

| 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

<!-- Guidance: Review the register in the weekly progress meeting. Focus on items late to submit, overdue for return, or with a code C or D close to the needed-on-site date. -->

- 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.