Download the submittal log
XLSX
Submittal log (Excel)
Header block, 12 columns, drop-downs for type, review action and status, Rejected rows in red and Revise and resubmit rows in amber, frozen header row, filters and a How to use sheet.
CSV
Submittal log (CSV)
The example rows as plain CSV (UTF-8), for Google Sheets or any other tool.
Both files are free under CC BY 4.0, with no form to fill in. The XLSX opens in Excel, Google Sheets, LibreOffice and Numbers. The CSV carries the table only; the header block is in the XLSX.
Who keeps a submittal log, and why a supplier needs its own
On a construction project the specification lists what each trade must send to the engineer or architect before it may order, build or install: product data, shop drawings, certificates, test reports, samples and manuals. Each of these is a submittal, and the submittal log is the list that tracks them. The main contractor keeps one for the whole job. An equipment supplier needs its own for the sections in its scope, because fabrication usually cannot start until the drawings are approved, and a slow review turns into a late delivery with the supplier's name on it.
- Project engineers and project managers at equipment suppliers, who own the dates.
- Document controllers, who send the transmittals and enter what comes back.
- Main contractors' package managers, who can use the same columns across several suppliers.
Process and energy projects track the same thing as a vendor document register against a VDRL. If your customer works that way, use the vendor document register template. To check that a single submittal is complete before it goes out, see the HVAC submittal checklist. See also water treatment equipment manufacturers.
Header block
| Field | Example |
|---|---|
| Project | Example Riverside Pumping Station Upgrade (fictional) |
| Main contractor | Example Civil Contractor Ltd (fictional) |
| Engineer / reviewer | Example Consulting Engineers (fictional) |
| Subcontract or purchase order | PO-EX-2750 (fictional) |
| Supplier's scope | Pump station equipment package: three submersible pumps, valves and a control panel |
| Specification sections in scope | 4321, 4052, 4090 and 0178 (invented project specification) |
| Review period in the contract | As stated in the contract (this invented example uses 14 calendar days) |
| Log revision | D |
| Date | 2027-02-27 |
| Kept by | Project engineer |
Example rows: a pump station equipment package
| Submittal no. | Specification section | Description | Type | Rev | Submitted | Required back | Returned | Review action | Reviewer comment summary | Resubmittal due | Status |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 4321-001 | 4321 Submersible pumps, 1.4 A | Pump product data and performance curves | Product data | 0 | 2027-02-01 | 2027-02-15 | 2027-02-12 | Approved as noted | Show the cable length on the datasheet at the next issue. | Closed | |
| 4321-002 | 4321 Submersible pumps, 1.4 B | Pump general arrangement and installation drawings | Shop drawing | 0 | 2027-02-01 | 2027-02-15 | 2027-02-15 | Revise and resubmit | Guide rail fixing detail does not match the wet well drawing. Lifting chain not shown. | 2027-03-01 | Closed |
| 4321-002 | 4321 Submersible pumps, 1.4 B | Pump general arrangement and installation drawings | Shop drawing | 1 | 2027-02-26 | 2027-03-12 | Under review | ||||
| 4321-003 | 4321 Submersible pumps, 1.4 C | Motor datasheets and electrical data | Product data | 0 | 2027-02-03 | 2027-02-17 | 2027-02-16 | Approved | Closed | ||
| 4321-004 | 4321 Submersible pumps, 1.5 A | Material certificates for pump casings and impellers | Certificate | Due before shipment, after the castings are made. | Not submitted | ||||||
| 4321-005 | 4321 Submersible pumps, 1.5 B | Factory performance test reports, one per pump | Test report | Due after the factory tests. | Not submitted | ||||||
| 4052-001 | 4052 Valves, 1.3 A | Product data for gate valves and check valves | Product data | 0 | 2027-02-05 | 2027-02-19 | 2027-02-18 | Rejected | Wrong gate valve series submitted. The specification asks for resilient-seated valves. | 2027-03-04 | Resubmit |
| 4052-002 | 4052 Valves, 1.3 C | Valve coating colour sample | Sample | 0 | 2027-02-05 | 2027-02-19 | 2027-02-19 | Approved | Closed | ||
| 4090-001 | 4090 Control panel, 1.4 A | Control panel general arrangement and wiring diagrams | Shop drawing | 0 | 2027-02-10 | 2027-02-24 | Not back by the required date. Chased on 2027-02-26. | Under review | |||
| 4090-002 | 4090 Control panel, 1.4 B | Control description and input/output list | Shop drawing | 0 | 2027-02-10 | 2027-02-24 | 2027-02-23 | Approved as noted | Add the high-level alarm to the telemetry list. | Closed | |
| 4090-003 | 4090 Control panel, 1.5 A | Level instrument calibration certificates | Certificate | 0 | 2027-02-22 | 2027-03-08 | 2027-02-25 | For information | Closed | ||
| 0178-001 | 0178 Closeout submittals, 1.2 | Operation and maintenance manual | O&M manual | Due before handover. | Not submitted |
Drawing submittal 4321-002 appears twice: revision 0 came back Revise and resubmit, and revision 1 is under review. The control panel drawings are past their required-back date and have been chased. The specification section numbers are invented, and the 14-day review period belongs to the invented contract; yours is in your own contract. Every example value is invented: the project, customer, bidders, purchase order, prices and every document, certificate, serial and report number do not exist. Standards are named but not quoted.
Review actions
| Review action | Common meaning |
|---|---|
| Approved | No comments. The work the submittal covers can go ahead. |
| Approved as noted | The work can go ahead with the reviewer's comments taken in. The contract says whether a corrected record copy has to be sent. |
| Revise and resubmit | The affected work must wait. Correct the submittal and send it again as the next revision. |
| Rejected | The submittal does not meet the contract documents. A new submittal is needed, often for a different product. |
| For information | Received for the record. No approval is given, and none is needed. |
Reviewers' stamps differ from project to project. Some use letters or numbers, and some use other wording for the same outcomes. Enter the words on the stamp and edit the drop-down list to match. What each action lets you do next is set out in the contract. Check the governing standard or contract.
Columns and what to write
| Column | What to write |
|---|---|
| Submittal no. | The number the project's submittal procedure gives it. Many projects use the specification section plus a running number. Keep the same number for every revision. |
| Specification section | The section and paragraph of the project specification that asks for the submittal. |
| Description | What the submittal contains, in the words of the specification where you can. |
| Type | Product data, Shop drawing, Certificate, Test report, O&M manual or Sample (drop-down). |
| Rev | Revision of the submittal. Each resubmittal gets its own row, so the history stays visible. |
| Date submitted | The date it left you, from the transmittal (YYYY-MM-DD). |
| Date required back | The date submitted plus the review period the contract gives the reviewer (YYYY-MM-DD). |
| Date returned | The date the reviewed submittal came back (YYYY-MM-DD). Blank while it is under review. |
| Review action | Approved, Approved as noted, Revise and resubmit, Rejected or For information (drop-down). Use the wording on the reviewer's stamp. Rejected rows turn red; Revise and resubmit rows amber. |
| Reviewer comment summary | The reviewer's comments in one or two lines, enough to know what has to change. |
| Resubmittal due | The date the next revision must go in, where one is needed (YYYY-MM-DD). |
| Status | Not submitted, Under review, Resubmit or Closed (drop-down). |
How to keep the log
- Fill in the header block: the project, who reviews submittals, your subcontract or purchase order, and the review period the contract allows.
- Go through each specification section in your scope and list every submittal it asks for, one row each, before you send the first one. Missing rows are the ones that surprise you later.
- Number each submittal the way the project's procedure says, and pick its type from the drop-down.
- When a submittal goes out, enter the revision and the date submitted, then work out the date required back from the contract's review period.
- When it comes back, enter the date returned, the review action as stamped, and the comments in a line or two.
- For Revise and resubmit or Rejected, set a resubmittal due date and add a new row for the next revision when it goes out. Close the earlier row; the new row carries the open review.
- Each week, filter Status for Under review and compare today's date with the date required back. Chase anything late in writing, and note the chase in the comment column.
- Issue the log with your progress report, with its revision and date in the header.
Keeping submittals in step with the specification
A log tells you what was sent and when. It cannot tell you whether the drawing you sent agrees with the specification section it answers. In OdysseyGPT's Order & Document Control module, VDRL/MDR Tracker (beta) reads the customer's document requirements and your register and lists what is missing, late or at the wrong revision. Document Review compares a specification with your own documents and quotes the page for each difference. Your project engineer decides what to do with each finding. Tools marked beta are open on request, and we onboard each team ourselves.
Want us to run the check for you?
Send your quotation and the customer's purchase order. We send back a list of what changed between them, each item cited to its page.
