Project & Register Info
Submittal Status Summary
Submittal Register
| # | Submittal No. | Description / Title | Type | Discipline | Spec / Dwg Ref | Rev | Submitted By | Reviewer | Date Submitted | Review Due | Date Returned | Review Code | Remarks | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Total Submittals Logged | 0 | |||||||||||||
Approval Summary
About this submittal and approval tracker
This tool keeps the submittal register for a construction package: every shop drawing, material submittal, method statement, sample and technical datasheet sent to the engineer for review, tracked from submission through to approval. It is built for document controllers, contract administrators, resident engineers and project managers who have to prove what was approved, when it was returned and how long the review actually took.
What each submittal records
- Submittal number and revision, so resubmissions stay linked to the original
- Type and discipline, and the specification or drawing reference it responds to
- Submitting party and the reviewer responsible for returning it
- Date submitted, review due date, and date returned
- Review code — A, B, C or D — or Under Review / Not Submitted
Review codes used
| Code | Meaning and effect on the work |
|---|---|
| Code A | Approved. Work may proceed as submitted. Counted as approved in the summary. |
| Code B | Approved as noted. Work may proceed provided the reviewer's comments are incorporated. Counted as approved. |
| Code C | Revise and resubmit. Work may not proceed. A new revision of the same submittal number is required. |
| Code D | Rejected / not reviewed. Usually incomplete, superseded or the wrong scope. A fresh submittal is required. |
| Under Review | Submitted and with the reviewer. These are the rows that can go overdue. |
| Not Submitted | Planned against the submittal schedule but not yet issued. Never counted as overdue for review. |
How the review due date works
The contractual review period is set once in the register header — commonly fourteen or twenty-one calendar days — and each row calculates its own review due date as date submitted plus that period. Where a particular submittal carries an agreed different period, typing a date directly into the row overrides the calculation and the row is marked as manual. Changing the header period recalculates every row that has not been overridden.
How overdue submittals are flagged
A submittal counts as overdue when its review due date has passed and it has not yet been returned. Once a review code and a returned date are entered the row stops counting as overdue, whether the outcome was approval or revise and resubmit. The flag applies itself as dates roll past, so a submittal that was within its review period last week shows as overdue this week without anyone editing it, and the overdue count moves with it.
The approval summary
Above the register, the summary counts total submittals, how many are approved under codes A and B, how many are under review, how many were returned for revision and how many are overdue, alongside the approval rate shown as a progress bar. Below the register, submittals are grouped by discipline and the review turnaround is reported: the average days taken to return a submittal, the longest review still open, and how many resubmissions the package has generated. Where the average turnaround exceeds the contractual review period, this register is the record that supports a delay notice or an extension of time claim.
Getting data in and out
Submittals can be imported from an Excel or CSV file rather than typed, exported back to CSV, saved as a project file that reloads with every field intact, and the whole register with the approval summary printed or saved as a PDF for issue.
Frequently asked questions
What is a submittal tracker?
A submittal tracker is the register that records every drawing, material, sample and method statement the contractor sends to the engineer for review, and follows each one through to approval. It holds the submittal number, revision, date submitted, date returned and the review code given, so at any point you can say exactly what is approved, what is still in review and what has to be resubmitted.
What do submittal review codes A, B, C and D mean?
Code A means approved and the work may proceed. Code B means approved as noted, so work may proceed provided the reviewer's comments are incorporated. Code C means revise and resubmit, so the work may not proceed and a new revision is required. Code D means rejected or not reviewed, usually because the submittal was incomplete or the wrong scope. Codes A and B allow work to start; codes C and D do not.
How is the review due date calculated?
The due date is the date submitted plus the contractual review period, which is set once in the register header and is typically fourteen or twenty-one calendar days. Each row calculates its own due date from that, and any row can be overridden by typing a different date where a particular submittal carries an agreed shorter or longer review period.
When is a submittal counted as overdue?
A submittal is overdue when its review due date has passed and it has not been returned, meaning it is still shown as Under Review with no returned date. Once a review code and a returned date are entered the submittal stops counting as overdue, whether it was approved or sent back for revision. The flag applies itself as dates roll past, so nothing has to be edited to keep the overdue count current.
What is the difference between a submittal and a transmittal?
A submittal is the item being sent for review, such as a shop drawing or a material technical datasheet. A transmittal is the covering document that formally conveys one or more submittals, carries its own number and records the date of issue. One transmittal often carries several submittals, which is why the register is kept at submittal level and the transmittal number is recorded against each row.
Related project management tools
Running the same project: