← All field guides

Submittals2 min readNov 7, 2026

What to track on a construction submittal log (and why ball in court matters most)

Submittal log columns that matter: spec section, required-by date, lead time, revisions, and the ball-in-court column that runs your weekly meeting.

In this post
  1. The basics
  2. Why ball in court is the column that matters
  3. Common mistakes

A submittal log answers one question every week of the job: what's holding up the materials we need? If yours can't answer that in ten seconds, it's tracking the wrong things. Here is what belongs on a construction submittal log, and why "ball in court" matters more than any other column.

The short version

  • Number submittals by spec section and build the full register up front.
  • Work out a required-by date from install date, lead time and review time.
  • Track ball in court as a person and a date, and sort by how long they've held it.

The basics

  • Submittal number and spec section. Number by spec section (08 11 13-01) so related submittals sort together and nothing gets missed against the spec.
  • Description and type. Product data, shop drawings, samples, mock-ups, closeout documents.
  • Responsible sub or supplier. The company that owes the package.
  • Required-by date. Work backward from when the material must be on site: install date minus lead time minus review time. This is the date that matters, not the date it was sent.
  • Lead time. Write it down when you learn it. Long-lead items (switchgear, elevators, storefront) need to go first.
  • Revision. Rev 0, Rev 1... Each resubmittal is the same submittal, not a new line.
  • Review result. Approved, approved as noted, revise and resubmit, rejected.

Why ball in court is the column that matters

A submittal moves between at least four parties: the sub prepares it, you review it, the architect or engineer reviews it, and it comes back. At any moment, exactly one of them is holding it up. "Status: in review" doesn't tell you who to call. "Ball in court: Mechanical engineer, since Oct 30" does.

Track it as a person and a date, and sort by how long they've held it. That one view will run your weekly submittal meeting.

Common mistakes

  • Logging only what's been submitted. Build the full register from the spec at the start of the job, so missing submittals show up as missing.
  • Treating "approved as noted" like "approved." The notes need to reach the installer, not just the file.
  • Losing the trail. When a resubmittal comes back, you should be able to see every earlier round and comment.

Submittal log setup

  • Build the register from the spec at the start
  • Number by spec section
  • Add type and responsible company
  • Set a required-by date for each one
  • Record lead times as you learn them
  • Send long-lead items first
  • Track revisions on the same line
  • Track ball in court with a date
  • Pass "approved as noted" comments to the installer

Try it in ProjectAire

Submittals in ProjectAire move through issue, submit, review and close, with every step's response kept on the record. Each submittal says who has it and for how long. Some teams use the same tool for owner selections: a project can rename it "Selections." A log you already keep in Excel imports from CSV.

Start free See the submittals demo

Put this to work on your next job.