Submittal Register

Track each submittal package, sender, recipient, dates, revision, response code and overdue action.

This Excel template contains prepared working sheets and completion notes on a separate sheet. Enter your project data and review the completed workbook before use.

This editable workbook helps you organise project information. Check any included formulas, assumptions and results before use; it does not replace professional review.

Prepare project brief

The form prepares a separate brief; it does not fill the Word or Excel file.

Read product descriptions in your language. The Word and Excel template files are in English.

Submittal Register · Document preview — Selected page preview · XLSX

Learning

How to use this template

When you need it

Establish the submittal register before scheduled submissions begin and update it with every issue, response and resubmission. Use it where design, material or vendor packages require controlled review before dependent work can progress.

What it helps you decide

It makes the review transaction visible from submission to response. Coordinators can identify missing or overdue actions and distinguish a document's latest revision from the latest package actually submitted for review.

How to complete it

Build the baseline from required submittals and the agreed review procedure, identifying document numbers, revisions and purpose of issue for each package to be routed.
Record actual submission and response references from controlled communications, checking that responses relate to the same package and revision rather than a similar earlier issue.
Identify resubmission actions and outstanding responses, coordinate them with originators and reviewers, and retain the issue history so package status remains traceable during later review.

Who prepares and reviews it

The document controller maintains transmittal and response references with package originators. Review coordinators validate routing and response status; the assigned technical or contractual authority determines the meaning of the actual review outcome.

A mistake to avoid

Do not overwrite prior submission references with the latest issue; losing transaction history makes it difficult to explain what reviewers actually received and returned.

Illustrative example

Illustrative example: a steelwork package is resubmitted after comments, but the team initially records the earlier response against the new revision. Register reconciliation exposes the mismatch. The coordinator seeks the correct response before representing the current package as reviewed for its intended purpose.

Explore the wider topic

Document contents

Submittal baseline
Issue tracking
Response tracking
Outstanding actions

Required inputs

Required submittal schedule
Issued transmittals and received responses
Document numbering and review procedures

Practical tools.
Professional judgment.

Confirm the adopted edition, local amendments, National Annex where relevant, and contract requirements.