What spreadsheets do well
A well-maintained submittal log in Excel tracks the basics effectively:
- Submittal number, spec section, and description
- Date submitted, date required, and current status
- Who submitted it and who is reviewing it
- Approval status and revision number
Spreadsheets are flexible, free, and familiar. Every PE and PM on a construction project knows how to use one. For a small project with 50 submittals, a spreadsheet log can work fine.
Where spreadsheets break down
The problems start when the project scales — or when the team needs more than status tracking:
- No connection to documents. The log says "submitted" but doesn't link to the actual PDF, the specification section, or the contract drawings. The reviewer has to find everything separately.
- No review intelligence. The spreadsheet cannot compare a submitted product against the spec. That is entirely manual — and the most time-consuming part of the job.
- No issue tracking. When a reviewer finds a problem, the comment lives in an email, a Bluebeam markup, or a cell that gets overwritten. There is no structured record of what was found, who owns it, and whether it was resolved.
- No decision trail. Six months later, nobody can explain why a submittal was approved or rejected. The spreadsheet says "Approved" — but not why, or what conditions were noted.
- Version control problems. Multiple people edit the same file. Rows get deleted. Formulas break. The "latest" version is whichever one someone last emailed.
- No resubmittal context. When a resubmittal arrives, the reviewer starts from scratch because there is no connection between the original comments and the new package.
What DECK replaces
DECK is not just a better spreadsheet — it replaces the entire manual process that sits behind the spreadsheet:
| Capability | Spreadsheet | DECK |
|---|---|---|
| Submittal log and status | Yes — manual entry | Yes — with review context |
| Link to submitted documents | Hyperlinks at best | Yes — documents connected to requirements |
| Requirements comparison | No — entirely manual | Yes — AI-assisted with citations |
| Cross-document gap detection | No | Yes — specs, drawings, schedules, addenda |
| Cited findings | No | Yes — linked to source pages |
| Issue assignment and tracking | No — comments in cells or email | Yes — owner, response, resolution |
| Decision trail | "Approved" in a cell | Full review record with rationale |
| Resubmittal comparison | No — start over | Comment-to-change comparison |
| Multi-user collaboration | Conflict-prone | Built for teams |
The real cost of spreadsheets
The spreadsheet itself is free. The process around it is not. A Project Engineer spending 2–4 hours per submittal searching specifications, cross-referencing drawings, and writing review comments is the actual cost — and it scales linearly with every submittal on the project.
On a mid-size commercial project with 300–500 submittals, that manual review burden can add up to thousands of hours. Missed requirements in that process lead to rework, change orders, and schedule delays — costs that dwarf any software subscription.
When to move beyond spreadsheets
If any of these are true, the spreadsheet is no longer the right tool:
- You have more than 100 submittals on the project
- Multiple reviewers are working across different trades
- Review comments are scattered across email, Bluebeam, and the log
- You cannot explain why a submittal was approved six months ago
- Resubmittals keep coming back without addressing the original comments
DECK gives your team the review intelligence that a spreadsheet cannot. See the full capabilities in Construction Submittal Management Software, or learn how the review process works in How to Review Shop Drawings Against Specifications.