Construction Submittal Log Best Practices for PMs

A construction submittal log is the running record of every product data sheet, shop drawing, sample, and material approval a project needs, along with where each one sits in the review process right now. Done well, it's the early-warning system that keeps long-lead items from blindsiding your schedule. Done badly, it's a stale spreadsheet nobody trusts, and you find out a critical submittal was never approved the week the material was supposed to ship.

If you're a GC project manager, the submittal log is one of the few documents that quietly decides whether a job stays on schedule. Let's get it right.

What is a submittal log, really?

It's not just a list of submittals. It's a status tracker. The whole point is to answer three questions at a glance: what needs to be submitted, where each item is in the approval chain, and what's at risk of being late. A list tells you what exists. A good log tells you what to chase today.

The log lives between your spec book and your procurement schedule. It pulls required submittals out of the specs, tracks them through review, and feeds approved items into purchasing so material orders go out with enough lead time. Miss that handoff and you get the classic problem: an approval that lands too late to matter.

The fields that actually matter

Most submittal logs are either too thin to be useful or so bloated nobody updates them. Here's the set of columns that earns its keep:

Field	Why it's there
Submittal number	Unique ID, usually tied to the spec section
Spec section	Ties the item back to the contract requirement
Description	Plain-language "what this is" so anyone can scan it
Type	Product data, shop drawing, sample, mock-up, etc.
Responsible sub	Who owes you the submittal
Ball in court	Who has it right now and what they need to do
Date received	When the sub sent it to you
Date to architect	When you forwarded it for review
Date returned	When it came back, with the action taken
Status	Approved, approved as noted, revise and resubmit, rejected
Required-on-site date	The schedule date the material is actually needed
Lead time	Fabrication or delivery time after approval
Required approval date	Required-on-site minus lead time. The real deadline.

That last group is where most logs fall short. If you only track when something was submitted, you're managing history. Tracking the required approval date is what lets you manage the future.

Best practices that keep the log honest

Build the log from the specs, before the job starts

Sit down with the spec book during preconstruction and pull every required submittal into the log up front. Don't let it grow reactively, one item at a time, as subs remember to send things. A complete log from day one is the difference between leading the schedule and chasing it.

Track ball-in-court relentlessly

"Ball in court" means exactly one party owns the next action at any moment: the sub, you, the architect, or the engineer. The single most useful thing your log can tell you is who is sitting on what, and for how long. When an item has been in the architect's court for 18 days, that's a phone call, not a footnote.

Work backward from the required-on-site date

For every submittal tied to a long-lead item, calculate the required approval date and treat it as the deadline that matters. Anchoring deadlines to procurement reality, not to when something happened to get submitted, is what turns the log from a record into a planning tool. This is the same backward-planning discipline that drives good bid follow-up, which we cover in the bid coordination checklist.

Update it on a fixed cadence

A log updated "whenever" is a log nobody believes. Pick a rhythm, usually weekly, and review it the same way every time: new items, items aging in someone's court, and anything approaching its required approval date. Bring the at-risk items to your project meeting.

Keep one source of truth

If submittal status lives in three inboxes and a whiteboard, it lives nowhere. Whether you run it in Procore, Autodesk Build, a shared sheet, or another platform, everyone references the same log. No private side-copies.

Common submittal log mistakes

A few patterns sink more schedules than anything else:

• Tracking submission, not approval. Knowing when something went out tells you nothing about when you can order the material.
• Ignoring lead times. A 12-week curtain wall and a 2-day fastener submittal are not the same urgency, even if they were submitted the same day.
• Letting the ball-in-court column go stale. If it doesn't reflect who actually has the item today, the log is decorative.
• No owner. When "everyone" maintains the log, no one does. Assign it to one person.
• Reacting instead of forecasting. If your log only tells you what already happened, you'll keep finding out about problems too late to fix them.

Who should own the submittal log?

Someone has to own it, and it usually shouldn't be the PM doing the data entry. The project manager owns the decisions: which items are at risk, who gets the escalation call, how to recover a slipping approval. The day-to-day upkeep, logging receipts, forwarding to the architect, updating ball-in-court, and flagging aging items, is exactly the kind of high-volume, time-sensitive work that's perfect to delegate.

That's where a submittals and RFI virtual assistant earns their keep. They keep the log current, route items to the right reviewer, and surface the at-risk approvals before they become schedule problems, so you spend your time deciding instead of chasing. It pairs naturally with broader project administration support, and if you're weighing whether that kind of help is worth it, the ROI case for hiring a construction VA breaks down the numbers. Submittal tracking is one of the core lanes covered in our breakdown of what a construction project coordinator actually does.

A simple weekly submittal review

Run this every week and the log stays alive:

1. Add new required items discovered since last week.
2. Update ball-in-court for everything in motion. Who has it, since when.
3. Flag aging items, anything sitting in one court past your threshold (say, 14 days).
4. Check required approval dates. Anything inside its lead-time window gets escalated now.
5. Report the at-risk list at your project meeting, with a clear ask for each item.

A submittal log isn't paperwork for its own sake. It's how you see schedule risk coming while you still have time to do something about it. Build it from the specs, track ball-in-court honestly, plan backward from procurement, and keep one person accountable for it.

If your submittal log has quietly become a graveyard nobody updates, tell us about your workflow and we'll help you get it back to being an early-warning system.