Construction Submittal Log Excel Template | SheetCraft

Every superintendent has the same war story. The tile shop drawing sat on the architect's desk for three weeks. By the time it came back approved with revisions, the resubmittal cycle ate another two. Now the tile is ordered with a six-week lead time, the bathrooms are on the critical path, and the owner is asking why the schedule slipped a month. Nobody saw it coming because nobody was tracking it. A proper construction submittal log template Excel file would have flagged the risk in week one.

This is the most underrated tool on a construction job. Not because submittal tracking is glamorous, but because every dollar of general conditions you burn waiting on approvals is a dollar you stole from your own profit. A small commercial job at $4,000 per week in supervision, trailer rental, and insurance loses $16,000 for every month of approval drag. On a 12-month job, the spread between a managed submittal log and a reactive one is six figures.

Why Most Submittal Logs Are Useless

The standard submittal log most contractors run looks like a spreadsheet that lists what was submitted and when it came back. That is a historical record, not a management tool. By the time you can see the problem, the problem already happened. The architect held a shop drawing for 22 business days, you found out on day 23, and now you are scrambling.

The submittal log you actually want answers a different question. Not "what did we send" but "what is about to bite us, ranked by exposure." That requires three pieces of data most logs do not capture: required-on-site date, fabrication lead time, and current calendar age in review. With those three columns and a couple of formulas, you can rank every open submittal by how much float you still have, and act on the worst one this week instead of finding out about it next month.

The Real Cost of a Late Submittal

Before building the log, price out the damage. A late submittal does not just delay one trade. It cascades.

Cost Category	Mid-size Commercial Job	Single-Family Custom Home
General conditions (per week)	$4,200	$1,100
Liquidated damages clause (per day)	$1,500	$250
Crew demobilization and return	$3,800	$1,200
Expedited shipping if recovery needed	$2,500 to $8,000	$600 to $2,400
Total exposure on a 3-week delay	$31,000+	$6,500+

That is per delayed submittal. A job with 80 to 200 submittals and three late ones is not unusual. Now multiply. This is why the submittal log earns its keep five times over before the slab is poured.

The 11 Fields Your Submittal Log Must Have

Open a fresh workbook. Set up these columns in this order, because the formulas later reference them by position.

Submittal Number (Column A). Format: spec section dash sequence. Example: 03 30 00-001 for the first concrete submittal.
Spec Section (Column B). Pull from the project manual table of contents.
Description (Column C). What the submittal is. "Rebar shop drawings, footings and grade beams" beats "rebar."
Submittal Type (Column D). Shop drawing, product data, sample, mockup, certificate.
Responsible Sub (Column E). Who owes you the submittal.
Required On Site (Column F). Date the material or installation has to happen.
Lead Time (weeks) (Column G). Fabrication plus shipping after approval. Get this from the sub or supplier in writing.
Submitted Date (Column H). When you sent it to the architect.
Returned Date (Column I). When it came back.
Status (Column J). Pending, Approved, Approved as Noted, Revise and Resubmit, Rejected.
Resubmittal Count (Column K). How many cycles this took. Zero on first submission.

Then add three calculated columns on the right that do the actual work.

Days in Review (Column L). How long the architect has been sitting on the current version.
Latest Approval Needed (Column M). Backed out from required on site, minus lead time, minus a buffer.
Risk Flag (Column N). Red, Yellow, Green, based on time remaining versus current status.

Excel Formulas That Catch Risk Before It Becomes a Delay

Here is where the log stops being a list and starts being an early warning system. Assume row 4 is the first data row, headers are in row 3.

Days in Review

If the submittal is still in review, count business days since you sent it. If it came back, use the returned date to lock the count.

=IF(I4="",NETWORKDAYS(H4,TODAY()),NETWORKDAYS(H4,I4))

NETWORKDAYS counts Monday through Friday, skipping weekends. You can add a holiday range if your contract recognizes specific dates. This column tells you, at a glance, which submittals have been sitting in the architect's queue past the contractual review period, usually 10 to 15 business days.

Latest Approval Needed Date

Work backward from when you need the thing on site. Subtract lead time. Subtract a buffer of 5 business days for shipping and receiving.

=WORKDAY(F4,-(G4*5)-5)

WORKDAY counts in business days. Lead time in weeks gets multiplied by 5 to convert. This is the drop-dead date for the architect to issue an approval. If today is past this date and the submittal is still pending, you have a problem.

Risk Flag

The flag is the heart of the log. It looks at status and timing together. Three nested IFs that you can paste once and copy down.

=IF(OR(J4="Approved",J4="Approved as Noted"),"GREEN", IF(AND(J4="Pending",TODAY()>M4),"RED", IF(AND(J4="Pending",NETWORKDAYS(TODAY(),M4)<=10),"YELLOW", IF(OR(J4="Revise and Resubmit",J4="Rejected"),"RED","GREEN"))))

Approved or Approved as Noted is green. Pending past the latest approval date is red. Pending with 10 business days or fewer until the latest approval date is yellow. Anything kicked back is red until resubmitted. Apply conditional formatting to color the cell, and the log becomes a one-glance status board.

Aging Bucket for the Weekly Report

If you want to roll up by how long things have been sitting, add this column.

=IF(L4<=5,"0-5 days",IF(L4<=10,"6-10 days",IF(L4<=15,"11-15 days","Over 15 days")))

Pivot the log by this column to send a weekly aging report to the architect. Nothing speeds up reviews like a Monday morning email showing seven submittals over 15 days in review with a copy to the owner.

A Worked Example That Shows the Difference

Take a real scenario. You are 8 weeks into a 36-week hotel renovation. The custom millwork for the lobby has an 18-week lead time. Required on site is week 30. You submit shop drawings in week 8.

Field	Value
Required On Site (F)	Week 30
Lead Time (G)	18 weeks
Submitted Date (H)	Week 8
Latest Approval Needed (M)	Week 30 minus 18 weeks minus 5 days, which lands in Week 11
Days in Review at Week 11	15 business days
Risk Flag at Week 11 if still pending	RED

Without the log, you check on this in week 13, learn the architect needs revisions, resubmit in week 14, get approval week 16. You are now 8 weeks late to start fabrication, which arrives in week 34. Lobby opens four weeks late. With the log, the cell flips yellow in week 9 and red on day one of week 11. The PM is on the phone the same morning. The submittal gets pushed through, fabrication starts on time, lobby opens on schedule.

The Excel formula did not save the job. The visibility did. The formula just made sure the visibility happened automatically every time anyone opened the file.

The Weekly Review Routine That Keeps Approvals Moving

A log that nobody opens is wallpaper. Build the review into a recurring meeting.

Monday 8:00 AM, 15 minutes. Sort by Risk Flag column descending. Walk every red and yellow with the project engineer.
Monday 9:00 AM email. Send the architect a filtered view of items over 10 days in review. Cc the owner if you are over 15.
Friday 3:00 PM, 10 minutes. Update Returned Date and Status for everything that came back that week. Add new submittals from the upcoming look-ahead schedule.
End of month. Pivot by Responsible Sub and Resubmittal Count. Subs averaging more than one resubmittal per submittal are getting a phone call about quality control.

This routine takes 45 minutes a week. It pays for itself the first time it catches a slipping submittal.

Where Excel Beats the SaaS Tools

Procore, Autodesk Construction Cloud, and the rest have submittal modules. They are excellent on the right job. Where they fall down: $700 to $1,200 per user per year for a tool subs will not log into anyway, rigid workflows that do not match how your team actually reviews, and no easy way to model "what if I add 5 days of buffer to my lead times across the board." Excel handles all three problems for the cost of an hour of setup.

The other advantage is that the log moves with the work. Email it to a sub who needs to see what is open against their scope. Print a filtered view for the OAC meeting. Drop a snapshot into the monthly owner report. None of that requires a license, a portal, or a training session.

Stop Building Yours From Scratch

Setting this up once is straightforward. Setting it up for every job, with conditional formatting, formulas, drop-downs for status, validation on dates, and a pivot for the weekly aging report, gets old fast. That is what we built the SheetCraft Construction Budget Tracker for. It includes a submittal log tab with all 14 columns above, the risk flag formulas pre-built, conditional formatting wired up, and a dashboard that rolls up by status, sub, and aging bucket. Drop in your spec sections and required-on-site dates and the rest works on day one.

One late submittal pays for the template a hundred times over. See the Construction Budget Tracker and stop running submittals on a list that only tells you what already went wrong.