OdysseyGPT

Free template

Submittal log template: a construction submittal register for equipment suppliers (Excel and CSV)

For equipment suppliers and subcontractors on construction projects: one row per submittal and revision, with the dates sent, due back and returned, the review action and the reviewer's comments.

By Ademola Afolabi, Founder, New Odyssey Ltd · Last reviewed:

The short answer

A submittal log is the register of every document, drawing, certificate and sample a contractor or supplier must send for review on a construction project. This free Excel template has one row per submittal and revision: number, specification section, description, type, dates submitted, required back and returned, review action, reviewer comments, resubmittal date and status.

Key Takeaways

  • Build the whole log from the specification before the first submittal goes out.
  • Each resubmittal gets its own row under the same number, so the review history stays visible.
  • The review period and the meaning of each review action come from the contract, not from this template.
  • The example has 12 rows for an invented pump station equipment package (PO-EX-2750).

Download the submittal log

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

Header block fields, with the invented example values
FieldExample
ProjectExample Riverside Pumping Station Upgrade (fictional)
Main contractorExample Civil Contractor Ltd (fictional)
Engineer / reviewerExample Consulting Engineers (fictional)
Subcontract or purchase orderPO-EX-2750 (fictional)
Supplier's scopePump station equipment package: three submersible pumps, valves and a control panel
Specification sections in scope4321, 4052, 4090 and 0178 (invented project specification)
Review period in the contractAs stated in the contract (this invented example uses 14 calendar days)
Log revisionD
Date2027-02-27
Kept byProject engineer

Example rows: a pump station equipment package

Invented example rows for subcontract PO-EX-2750
Submittal no.Specification sectionDescriptionTypeRevSubmittedRequired backReturnedReview actionReviewer comment summaryResubmittal dueStatus
4321-0014321 Submersible pumps, 1.4 APump product data and performance curvesProduct data02027-02-012027-02-152027-02-12Approved as notedShow the cable length on the datasheet at the next issue.Closed
4321-0024321 Submersible pumps, 1.4 BPump general arrangement and installation drawingsShop drawing02027-02-012027-02-152027-02-15Revise and resubmitGuide rail fixing detail does not match the wet well drawing. Lifting chain not shown.2027-03-01Closed
4321-0024321 Submersible pumps, 1.4 BPump general arrangement and installation drawingsShop drawing12027-02-262027-03-12Under review
4321-0034321 Submersible pumps, 1.4 CMotor datasheets and electrical dataProduct data02027-02-032027-02-172027-02-16ApprovedClosed
4321-0044321 Submersible pumps, 1.5 AMaterial certificates for pump casings and impellersCertificateDue before shipment, after the castings are made.Not submitted
4321-0054321 Submersible pumps, 1.5 BFactory performance test reports, one per pumpTest reportDue after the factory tests.Not submitted
4052-0014052 Valves, 1.3 AProduct data for gate valves and check valvesProduct data02027-02-052027-02-192027-02-18RejectedWrong gate valve series submitted. The specification asks for resilient-seated valves.2027-03-04Resubmit
4052-0024052 Valves, 1.3 CValve coating colour sampleSample02027-02-052027-02-192027-02-19ApprovedClosed
4090-0014090 Control panel, 1.4 AControl panel general arrangement and wiring diagramsShop drawing02027-02-102027-02-24Not back by the required date. Chased on 2027-02-26.Under review
4090-0024090 Control panel, 1.4 BControl description and input/output listShop drawing02027-02-102027-02-242027-02-23Approved as notedAdd the high-level alarm to the telemetry list.Closed
4090-0034090 Control panel, 1.5 ALevel instrument calibration certificatesCertificate02027-02-222027-03-082027-02-25For informationClosed
0178-0010178 Closeout submittals, 1.2Operation and maintenance manualO&M manualDue 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 actionCommon meaning
ApprovedNo comments. The work the submittal covers can go ahead.
Approved as notedThe 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 resubmitThe affected work must wait. Correct the submittal and send it again as the next revision.
RejectedThe submittal does not meet the contract documents. A new submittal is needed, often for a different product.
For informationReceived 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

ColumnWhat 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 sectionThe section and paragraph of the project specification that asks for the submittal.
DescriptionWhat the submittal contains, in the words of the specification where you can.
TypeProduct data, Shop drawing, Certificate, Test report, O&M manual or Sample (drop-down).
RevRevision of the submittal. Each resubmittal gets its own row, so the history stays visible.
Date submittedThe date it left you, from the transmittal (YYYY-MM-DD).
Date required backThe date submitted plus the review period the contract gives the reviewer (YYYY-MM-DD).
Date returnedThe date the reviewed submittal came back (YYYY-MM-DD). Blank while it is under review.
Review actionApproved, 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 summaryThe reviewer's comments in one or two lines, enough to know what has to change.
Resubmittal dueThe date the next revision must go in, where one is needed (YYYY-MM-DD).
StatusNot submitted, Under review, Resubmit or Closed (drop-down).

How to keep the log

  1. Fill in the header block: the project, who reviews submittals, your subcontract or purchase order, and the review period the contract allows.
  2. 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.
  3. Number each submittal the way the project's procedure says, and pick its type from the drop-down.
  4. 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.
  5. When it comes back, enter the date returned, the review action as stamped, and the comments in a line or two.
  6. 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.
  7. 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.
  8. 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.

Get the free quotation-vs-PO check

New templates by email (optional)

Your download does not depend on this.

We use your email only for this. See our privacy policy.

Frequently asked questions

What is a submittal log?

A list of everything a contractor or supplier has to send to the design team for review, with the dates and the outcome of each review. It shows at a glance what is approved, what is waiting and what has to go in again.

What is the difference between a submittal log and a submittal schedule?

A submittal schedule is the plan: what will be sent and by when. The log is the record of what actually happened. Some teams keep both in one sheet by adding a planned date column; this template records the actual dates.

How long does the reviewer have to return a submittal?

As long as the contract allows. Review periods differ between contracts and sometimes between types of submittal, so the template has a header field for the period and gives no default. Check the governing standard or contract.

Does a resubmittal get a new number?

Most procedures keep the number and raise the revision, which is how the example works. Others add a suffix. Follow the project's submittal procedure, and keep one row per revision either way.

Is a submittal log the same as a vendor document register?

They do the same job in different industries. Construction projects call the documents submittals and track them by specification section. Process and energy projects call them vendor documents and track them against a requirements list with review codes.

References

Creative Commons Attribution 4.0 International

Creative Commons

Visit source

Related Pages