Search your submittals by what they actually cover
A submittal log tells you a number got logged and a date got stamped. It doesn’t tell you what the product is, which spec section governs it, or whether the last revision quietly changed the answer. BRAD reads the submittals and the spec sections they answer to, then lets your team search by what a submittal covers and see where each one stands — open, approved, or revise-and-resubmit. Every answer comes back with the page it came from.
Search by what it covers, not by log number
Forward BRAD the submittals — product data, shop drawings, samples, manufacturer cut sheets — and it reads them. Ask “did we submit the TPO roofing yet?” or “what gauge is the approved metal stud?” and you get the actual submittal back, with the page and the line it’s on — instead of scrolling a spreadsheet of numbers and dates hoping the description column is filled in.
Your PM, your super, and the architect are all reading the same record. Nobody has to know the log number to find the thing. They search the way they’d describe it standing in the field.
Each submittal tied to the spec section that governs it
A submittal exists to prove a product meets the specification. BRAD reads the spec sections too, so it knows a waterproofing submittal answers to 07 13 00 and a glazing package answers to 08 80 00. Ask what a submittal is supposed to satisfy and BRAD puts the governing section next to the submitted product — both with their sources.
That’s where the expensive gaps hide: a product that looks fine on its own data sheet but doesn’t actually meet the section it was submitted against. BRAD sets the two side by side so the reviewer is comparing the right things.
Open, approved, revise-and-resubmit — tracked across the package
BRAD tracks where each submittal stands and which spec it answers to, so “what’s still open on the curtain wall?” is one question, not an afternoon cross-checking the log against the architect’s returns. Approved, rejected, revise-and-resubmit, approved-as-noted — it reads it from the document that says so, and shows you that source.
When the super is about to install, that’s the question that matters: not “was something submitted,” but “is the approved version the one showing up on the truck.” BRAD keeps the status and the governing section in one place so the superseded sample doesn’t get built by mistake.
When a revision moves the governing spec, BRAD flags it
Specs move. An addendum or a revised section can change a fastener pattern, a fire rating, or an approved manufacturer — and a submittal approved against Rev B may no longer match Rev C. BRAD reads the revisions and flags when the spec that governs a submittal has changed under it, so an already-approved product doesn’t get installed against an out-of-date requirement.
It points you at what changed and which submittals it touches, with both versions cited. You decide whether to re-review. BRAD’s job is making sure you know there’s a decision to make.
Honest about what it is
BRAD is document intelligence for construction submittals — it reads, connects, and answers with the source attached. It is not a code official, an approval authority, or a guarantee that a product meets a spec. The architect of record and your review process still own that call. BRAD’s job is to put the submittal, its status, and the governing spec section in front of the right person, with citations, so the decision gets made on the full picture instead of a half-remembered email.
Your project’s content belongs to you, and each workspace stays isolated. If you have specific requirements about how your submittal and spec data are handled, ask us and we’ll answer plainly.
See Brad on your project
Brad connects the plans, contracts, change orders, photos, and conversations on your job into one source of truth. Request a demo and bring a project you want to untangle.