A decision log your project builds for itself
Most decisions on a job never get written down as decisions. They live in a super’s head, a buried email thread, or the margin of a set someone marked up and forgot. Then the person who made the call rolls off, the owner asks why the slab moved, and nobody can find the answer. BRAD reads the email, texts, RFIs, change orders, and marked-up sheets your project already produces and captures the decisions inside them — what was decided, why, when, and by whom — each one tied back to the document that recorded it.
Every decision, with the four answers that matter
A decision isn’t worth much six months later unless you know what was decided, why, when, and who made the call. BRAD pulls all four from the record itself. The architect approves a substitution in an RFI response; a change order reroutes the storm line; a Tuesday text tells the super to hold the rough-in — BRAD reads each one, files it as a decision, and keeps the surrounding context attached.
You don’t fill out a form or tag a thread. The log is assembled from the email and text the office and the field already send, so it reflects what actually happened on the job — not what someone remembered to write down.
Every entry carries the document that recorded it
A decision log nobody trusts is just a list of claims. BRAD answers with the source attached. Ask “why did we move the panel schedule on the second floor?” and you get the answer plus the RFI response and the marked-up sheet it came from — the actual record, not a paraphrase. When a dispute lands, the rationale isn’t a story somebody tells; it’s a document with a date and a name on it.
Ask it like you’d ask the super who was there
Plain questions, answered in seconds. “Who approved the window substitution on Rev C?” “When did we decide to defer the canopy?” “What changed on change order #14, and who signed off?” BRAD reads across the whole project record — submittals, RFIs, change orders, the email and texts between office and field — and answers with the entries and their sources, so you’re not scrolling a year of threads hoping the right one surfaces.
The why survives turnover and disputes
People roll off jobs. A super moves to the next project, a PM leaves the firm, and the reasoning behind a hundred small calls walks out the door with them. Because BRAD builds the log from the project’s own record instead of anyone’s memory, the why stays put. New people get caught up by reading the decisions instead of reconstructing them, and when an owner or an attorney asks how something came to be, the answer is already on file with the document behind it.
Honest about what it is
BRAD is document intelligence for construction — it reads your project’s record and gives you the decisions back with the source attached. It isn’t a legal determination, a guarantee that a call was correct, or a substitute for the contract and the official record. It captures what the documents say and shows you where it came from; the judgment stays yours.
Your project’s content belongs to you, and each workspace stays isolated from every other. If you have specific requirements about how your data is 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.