Submittal Log Software
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.
Issued means frozen
Mark as submitted promotes the compile into a numbered submission 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.
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 submission 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
- The whole log exported to XLSX or PDF, in the format the GC asks for
When the stamp comes back
Drop the reviewer's returned PDF on the submission it answers. The outcome is read off the stamp for you to confirm in one click, the reviewer's comments flow to the punch list and the Comment Response Log, and the next submission starts from the same submittal with the history underneath it.
Every submission states what changed since the one before: documents added, replaced, or removed, and sections retitled. When the engineer asks what is different in Rev 2, the answer is already written.
Send a link, not a 40 MB attachment
Share emails the reviewing engineer a link bound to their address. They read, mark up, and answer on the page it opens, with no account to create, and their response waits for you to accept it onto the record. You see whether the link was opened and when it was last downloaded.
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.
Questions integrators ask
RFI-01What is a submittal log?
The running list of every submittal on a job: its number, what was sent and when, the reviewer's response, and who owes the next move. Here it keeps itself as you issue packages and record responses, and it exports to XLSX or PDF when the GC asks for yours.
RFI-02What does ball in court mean?
Who owes the next move. While a package is with the reviewer the ball is in their court; once it comes back Revise and Resubmit, it is in yours. The log marks it on every row with a glyph as well as a color.
RFI-03Can I log submittals I sent before using Submittal Kit?
Yes. Record an external submittal with the PDF you sent, and it takes its place on the log with the numbering kept continuous.
RFI-04What happens to an issued submission when the submittal changes?
Nothing. The issued files are frozen when you mark the package submitted, and they outlive later edits and deletes. Only a submission that never actually went out can be withdrawn, which frees its number.
Read more
- What real submittal logs say about resubmittal rates
- What Approved as Noted actually requires you to do
- Submittal numbering and revision schemes that survive a long job
- Answering review comments on a resubmittal
- Revise and Resubmit: 5 checks before your submittal goes out
- When a review comment is a change order
- Is that review comment in the spec? Trace it first
- Revise and resubmit without rebuilding the whole package
- How the submittal log works
- Record a returned review