Submittal software for construction
Submittals reviewed in order, with every revision kept
Each submittal moves from the sub to GC review, then design review and an optional consultant review, with standard review codes at every step. Revisions stay linked under one number, and required-on-site dates show which approvals are running late.
Live demo — click any tool in the sidebar.
Submittals
Shop drawings, product data and samples through review, with lead times attached.
Submittals
Shop drawings, product data and samples through review, with lead times attached.
What it does
Sequential review, fixed review codes and every revision kept.
Sequential review steps
GC review, design review and consultant review run in order. The next step opens only when every required reviewer on the current one has responded.
Standard review codes
Reviewers respond with approved, approved as noted, revise and resubmit, or rejected. Anything other than approved needs a note saying what to change.
Revisions under one number
A revise-and-resubmit starts the next revision as a draft for the sub. Rev 0, Rev 1 and on stay linked on the submittal, with the latest one in the log.
At-risk by required-on-site date
Enter when the material is needed on site and its lead time. Conflo works out the approve-by date and flags submittals that are at risk of missing it.
Ball-in-court by company
The log shows which company holds each submittal and the active review step, from the sub preparing it to the reviewer on it now.
Organized by spec section and package
Record the spec section, submittal type (shop drawings, product data, samples, calculations, mockups, certificates, O&M manuals), package and location.
How it works
Step by step.
From the first step to the final record.
Step 1
Set up the submittal
Enter the title, spec section, type and the sub who prepares it. Add the package, location, required-on-site date and lead time.
Step 2
Pick the reviewers
Choose GC, design and consultant reviewers. Only the people you pick review it; if no GC reviewer is picked, the GC step is skipped.
Step 3
Submit for review
The sub or the GC submits it. Each step's reviewers see it in their Inbox and respond with a review code and notes.
Step 4
Return it to the sub
The GC returns it with the final code, and the deciding review is marked official. A revise and resubmit goes back to the sub to start the next revision.
Who uses it
Built for the whole project team.
Everyone on the job works in the same record — each sees what their role allows.
General contractors
Manages the submittal log, reviews first, routes to the design team and returns each submittal with the final code.
Subcontractors
Prepares and submits their company's submittals, and starts the next revision when one comes back revise and resubmit.
Owners
Sees the submittal log and which approvals are at risk of holding up material.
Architects & engineers
Reviews the submittals routed to them and responds with a review code and notes.
Questions
Submittals, answered.
What review codes are available?
Approved, approved as noted, revise and resubmit, and rejected. A revise and resubmit or rejection at any step ends that round and sends the submittal back to the GC.
How are resubmittals handled?
When a submittal is returned as revise and resubmit, the sub or GC starts the next revision. It keeps the same number and reviewers, and earlier revisions stay listed on the submittal.
Can subs see other companies' submittals?
No. A subcontractor sees only their own company's submittals. The GC, owner and design team see the full log.
How does Conflo decide a submittal is at risk?
It subtracts the lead time from the required-on-site date to get an approve-by date. Submittals without approval within seven days of that date are flagged.
