Field answers, in seconds — with the document attached

The question that can’t wait for a callback

“What’s the rebar spacing on grid C?” “Is the door schedule still on Rev C, or did Rev D supersede it?” “Did the owner sign CO #14, or are we still waiting?” The field asks these with the crew standing there and the clock running. Too often the honest answer is “let me get back to you” — and that wait is a crew idling on the clock, a guess that turns into rework, or a call the office returns an hour later when the pour’s already going in.

Brad closes that gap. Text the question, or email it from the trailer, and Brad reads your project’s plans, specs, contracts, and change orders and answers right then — fast enough to act on while the crew is still at the wall, not after they’ve moved on or built to the wrong detail.

Every answer carries its source

A field answer with nothing behind it is just another opinion, and the super knows it. So Brad doesn’t answer bare. Ask for the spec section and Brad sends it back with the sheet number and revision it came from. Ask whether the change order is signed and Brad points to the actual executed CO — not a recollection of it.

That citation is what turns a text into a decision the crew can build on. The super sees the detail, confirms it’s the current revision, and proceeds without wondering whether he’s working off a superseded sheet — because the document that settles it is right there in the reply.

Over the text and email the crew already uses

Nobody on a jobsite wants a new app to fumble for with gloves on. So Brad lives where the field already works: a text thread and an email inbox. The super texts the question the same way he’d text the PM, and the answer comes back the same way — with the document attached.

No rollout, no training day, no chasing down who downloaded it. Anyone who can send a text can use Brad on day one — from the cab of a truck or the middle of a slab pour.

The office stops being a switchboard

When the field can pull its own routine answers from the connected record, the PM and the architect stop relaying the same clarification a dozen times a week. The questions that still need a human get kicked up with context already attached — the current detail, the relevant CO, the prior RFI response — instead of starting cold.

And the answer doesn’t vanish into a one-off text. The question, the answer, and the document behind it stay part of the project record, so the next person who asks gets the same grounded reply — and nobody in the field is left holding an undocumented call.

Honest about what it is

Brad is document intelligence for construction — it reads your project’s plans, specs, contracts, and messages and answers field questions with the source attached. It isn’t a guarantee, a code ruling, or a substitute for licensed professional judgment or your formal RFI and submittal process; it connects those so the field is acting from the current, verifiable picture. Your project’s content belongs to you, and each workspace stays isolated. If you have specific data-handling requirements, ask us — we’ll answer plainly.