Submittal Log & Revisions
Prove what went out. Years later.
The question that eats a Monday morning is not what did we submit. It is what are we still waiting on, and what is waiting on us. And the question that eats a deposition is worse: what exactly was in Rev 2? The log answers both.
01 Issued means frozen
Mark as Submitted promotes the compile into a numbered revision whose bytes never change again, no matter how much the working submittal is edited afterward. The record outlives deleted submittals and deleted sites. Months later, what you transmitted is still there, exactly as transmitted.
02 The stamp, on the record
- Review outcomes as status chips: Approved, Approved as Noted, Revise & Resubmit, Rejected, No Exceptions Taken
- The engineer's returned, marked-up documents attached to the exact revision they answer
- Ball-in-court beside every row, so a revise and resubmit can never hide among the closed items
- Day counts that flag overdue reviews on their own
- A full log export as a PDF for project closeout
03 Your own numbers, finally
A kept log is also a measured one. When we counted thirteen of our founder's own project logs, one package in four came back for resubmittal and the median review took three weeks. Those are the numbers that decide schedules, and most integrators have never counted theirs. A log kept this way counts itself.
Read more
More of the kit