It’s 9:40 on a Tuesday and the tile setter is standing in the master bath with an open bag of thinset, waiting on you. The detail taped to the wall says one thing. He swears the architect changed it. You half-remember an email — something about a crack-isolation membrane in the wet areas, maybe two weeks back, maybe from the CA. So you do what supers have always done: you stop the work, you call the office, and you wait. The setter goes and finds something else to do. The clock keeps running. And the honest part is you’re not even sure the person picking up can find the right page faster than you can.

This is the quiet tax on a superintendent’s day. Not the big fires — the small ones. A dozen times a shift, the work stalls on a question that has a definite answer somewhere in the record. What’s the current detail? Did that change order actually get signed, or is it still sitting with the owner? Which spec section governs, and is it the latest revision? The answer exists. It’s just buried — in a 400-page set, an 80-page project manual, an inbox, a folder named “FINAL_v3_REALLY.” The cost isn’t the question. It’s the lookup — and trusting that what comes back is the version actually in force.

The problem was never storage. It’s retrieval — with proof.

Every job already has a place to put files: a drive, a portal, a shared folder, a Procore. Storage is handled. What isn’t handled is standing at the wall and getting the one right page back in the time it takes to read a text — and knowing it’s right because it shows you where it came from. A filing cabinet answers “where is the document.” A super needs the thing that answers “what does it say, which revision, and prove it.” That gap is the whole difference between a callback and a decision. BRAD is the second kind of tool: you forward it the documents and messages that run the job — the plans, the project manual, the contract, change orders, the RFI log, submittals, field photos, the email and text flying between trailer and field — it connects them into one record and answers over the channels the team already uses. For a super, that mostly means one channel. Text.

Storage tells you where a file lives; project memory answers the question and shows its work.

What a cited answer looks like at the wall

Back to the tile setter. Instead of calling in, you text the question the way you’d say it out loud: “What’s the current waterproofing detail for the master bath wet areas?” A minute later the answer comes back — crack-isolation membrane over the substrate, per the latest detail — and underneath it, the receipt: spec section 09 30 13, the detail on sheet A-502 at Rev C, and a note that it changed by way of RFI #22. Not a link to a 400-page PDF you’ll thumb through on your phone in the sun. The passage that governs, with its address. That citation is the whole game. A super isn’t after a chatbot’s opinion — he’s accountable for what gets built, and “the app said so” doesn’t survive a punch walk or a deposition. When the answer puts A-502 Rev C and the RFI that changed it in front of you, you’re not trusting the tool. You’re reading the source faster, with the tool doing the finding. You still own the call. You just made it in ninety seconds instead of forty minutes, and nobody walked off their work to dig.

One question, and the whole web behind it

Nothing on a jobsite stands alone, which is why this is hard by phone and easy once the record is connected. A change order isn’t a single document; it’s a knot. CO #14 bumps the tile allowance, which points to a revised spec, which is why the detail went to Rev C, which is why RFI #22 got answered the way it did, which moves the schedule and the budget. Ask about any one of those honestly and the answer is all of them. When the documents and messages are connected as one record, a question at the wall pulls the thread instead of the page — because the connection got made when the paper came in, not because you happened to remember it at 9:40 on a Tuesday.

One change order touches the spec, the detail revision, the budget, the schedule, and an RFI — which is why a single question has a connected answer.

What it does to the day

Add up the small fires. The membrane question. The firestopping callout you couldn’t put your hands on. The “is the new door schedule approved yet” text to the PM. The spec section the inspector wanted, standing right there in the corridor. Each one used to mean a stop, a call, a wait, and a crew finding busywork. Most are now a text and a glance. The work doesn’t stop. The office doesn’t get yanked off its own day to play librarian. And you stop being the bottleneck for questions you could answer yourself if the record would just hand you the page. There’s a second-order effect, too. When answers come back cited, the field and the office quit arguing from memory. Nobody relitigates what the architect said in a meeting three weeks ago — the record says Rev C, here’s the RFI, here’s the date. Disagreements get shorter because they get sourced.

The win isn’t a faster app. It’s a super who stops being the bottleneck for questions the record can already answer.

Be straight about what this is and isn’t. BRAD finds the current spec, the approved detail, the signed CO, and shows you the source — fast, over text. It does not stamp a drawing, execute a change order, or make the call for you. If a CO hasn’t been signed, the honest answer is “here’s the request, not an approval — it isn’t executed,” which is exactly what you want to hear before you build to it. The contract’s formal process still runs. A licensed professional still owns the judgment. BRAD makes the record fast and cites its work. The decision stays yours, the way it should.

The best version of this isn’t flashy. It’s a quiet Tuesday where the tile goes in on the right detail, the crew never stopped, and nobody at a desk had to drop what they were doing to find a page you could finally find yourself — with the receipt attached.