Submittal Cover Sheet Template and Submittal Register (Free CSV)

A submittal cover sheet template is the first page of every submittal package: it identifies the submittal by number and spec section, states what type it is, records the contractor's review, flags any deviations from the contract documents, and gives the architect a place to mark an action. This page includes the cover sheet and a submittal register template for tracking every package.

A complete submittal cover sheet includes: submittal number, revision, spec section (for example 08 71 00 Door Hardware), title, type (product data, shop drawing, or sample), submitted by, date submitted, required response date, the contractor's review stamp statement, deviations from the contract documents (yes or no, with a description), and the A/E action: No Exceptions Taken, Make Corrections Noted, Revise and Resubmit, or Rejected.

What fields go on a submittal cover sheet?

The cover sheet exists so the architect can tell, before opening the package, what it is, whether the GC actually reviewed it, and whether it asks for anything different from the specs. The example is a door hardware submittal.

What do the A/E action codes mean?

Firms word their stamps differently, but most use some version of these four. Put the full list on your cover sheet so the reviewer checks one box instead of writing a sentence.

What fields go in a submittal register template?

The submittal register (also called a submittal log) lists every submittal the specs require, before any of them arrive. Build it from the submittals article in each spec section, then track status on the same sheet.

Download the submittal cover sheet and register templates

Download the submittal cover sheet template (CSV, opens in Excel or Google Sheets) and download the submittal register template (CSV). Both include the door hardware example row.

How do you use a submittal cover sheet step by step?

• Build the register first, from every spec section's submittals article, so you know what's coming.
• When a sub's package arrives, review it against the spec section and drawings before stamping it. A pass-through stamp shifts nothing to the sub.
• Fill in the deviations field honestly. On AIA A201 contracts, the contractor stays responsible for deviations it didn't specifically call out in writing.
• Set the required response date from lead time and the need date, not a fixed two weeks.
• Log the A/E action and return date on the register the day it comes back, and issue the next revision number for any resubmittal.

What are common submittal cover sheet mistakes?

• A contractor stamp on a package nobody at the GC opened.
• Deviations marked N when the product is a substitution.
• Wrong spec section, so the package goes to the wrong reviewer.
• Reusing revision 0 on a resubmittal, which breaks the history.
• Bundling several spec sections in one package, so one rejection holds up the rest.

How is this different from the submittal log and types guides?

This page gives you the forms. For running the log over a whole project, read the submittal log guide. For what counts as product data, a shop drawing, or an informational submittal, see construction submittal types, and for filing and numbering, how to organize submittals.

Where does Helonic fit with submittals?

Helonic's submittal review checks a package against the governing spec section and the contract drawings, requirement by requirement, and returns a matrix with the page and spec paragraph for each finding. In the example, that's the step that would catch the Set 12 closer deviation before the stamp goes on. The architect or engineer of record still decides the action code.