It’s 7:40 on a Tuesday and the phone is already three questions deep. The super at the elementary-school job wants to know if the gym light fixtures got approved — the electrician is staging tomorrow and won’t pull a box off the truck on a maybe. The owner’s rep on the medical-office build is asking, again, why change order #14 moved substantial completion. And the architect just emailed about RFI #22, which you could swear was answered three weeks ago, in a thread, on a phone that has since been replaced. Three jobs, three open loops, and the answer to every one already exists. It’s just buried — in an email, a submittal log, a PDF nobody re-opened, a text from a number that never got saved.

This is the part of a general contractor’s job that never makes it into the job description: you are the place where the project’s memory lives, and the place where it goes to die. Owner on one side, architect and engineers above, a couple dozen subs below, the field in the middle of all of it. Every question routes through you because you’re the only one who touched the whole thing. And the quiet cruelty of it is that most of those questions aren’t hard. They’re lookups. The hard part is the digging.

The half-hour dig is the real cost

Watch where a GC’s day actually goes and it’s rarely the dramatic stuff. It’s the small retrievals — twenty, thirty of them — each costing a few minutes that don’t feel like much until you stack the context-switch tax on top. “Was the tile in 09 30 13 approved at Rev B or Rev C?” You stop what you’re doing. You open the submittal log. You scroll. You find the submittal but not the transmittal. You jump to email. You find the architect’s response, but it references a marked-up attachment you have to download to read the stamp. Eight minutes gone — and you weren’t even the one who needed it. The foreman was, and he’s been standing in the warehouse the whole time. Now multiply that across a portfolio. A GC running four or five active jobs isn’t holding one project’s detail — they’re holding the union of all of them: every job with its own rev history, its own open RFIs, its own stack of submittals at different stages of review. The information isn’t missing. It’s scattered. And the real cost isn’t any single eight-minute dig — it’s that you can never fully put the project down.

The answer almost always exists. What you’re paying for is the thirty minutes it takes to go find it — every time, on every job.
The coordination tax

Storage isn’t memory

Most GCs already have somewhere to put files — a project folder, a document-management tab, a shared drive three subfolders deep. That solves storage. It does not solve memory. A folder full of PDFs knows where a file sits; it doesn’t know what’s inside it. It certainly doesn’t know that the tile submittal in one folder is the same tile the architect rejected in an email in a different system, which is the same tile change order #14 just bumped to a pricier line. Storage holds documents next to each other; memory understands they’re about the same thing. That gap — between filed and understood — is where AI earns a place on a jobsite. Not as a chatbot that makes things up, and not as one more dashboard to log into, but as something that reads what a project already generates, connects the pieces that are about the same thing, and hands back a specific answer with the source attached. An answer you can’t trace is a rumor. An answer with the submittal page or the email thread stapled to it is something you can act on, forward to the sub, and stand behind.

The difference isn’t where the files live — it’s whether anything understands how they connect.

What “connected” actually buys you

Think about everything a single change order touches. Change order #14 isn’t one document — it’s a rock dropped in a pond. It revised the tile spec to Rev C. It moved a line in the budget. It pushed two days into the schedule. It’s the reason RFI #22 finally got a real answer. On most projects those facts live in five different places and only connect inside one person’s head — usually the GC’s, usually at 7:40 on a Tuesday. When the project is held as one connected record, the rock and all its ripples come back together. So when the owner’s rep asks why substantial completion slipped, you don’t reconstruct the story from memory and hope you got it right. You ask once, in plain English, and get back: change order #14, here’s the signed CO, here’s the two days it added, here’s the schedule revision it triggered. Ten seconds, cited, defensible — instead of the thirty-minute reconstruction you’d have done by hand.

One change order rarely changes one thing — the value is seeing every ripple at once.

Over the tools you already use

This is the problem BRAD is built for. You forward it the documents and messages that already run the job — plans, specs, submittals, RFIs, change orders, pay apps, the photos from the field, the email and text between office and trailer — and it reads them, connects the pieces that are about the same thing, and becomes one searchable record of the project. Then you ask it questions the way you’d ask a sharp project engineer who happened to have read everything: over email and text, the channels your team already lives in. No new app for the super to learn, no portal for the architect to log into, no dashboard anyone has to remember to open. Ask “was the gym fixture submittal approved, and at what rev?” and you get the answer with the submittal and the architect’s response attached. Ask across the portfolio — “which RFIs are still open on the medical-office job?” — and you get the list, not a place to start scrolling. The field can ask from a phone in a warehouse aisle; the office can ask from a desk. Same project brain, same cited answers, whoever’s asking and wherever they are.

What it doesn’t do

Here’s the honest scope, because a GC has heard enough overpromising for one career. BRAD does not make the call. It will tell you change order #14 moved the date and show you the signed CO — it will not sign the CO, stamp a drawing, or decide whether the owner gets the two days. It surfaces what the contract documents say; it doesn’t replace the contract’s formal process, the architect’s licensed judgment, or your read of the deal. Think of it as the fastest, most honest project engineer you’ve worked with — one that always cites its source and never pretends to know what it doesn’t. The decision is still yours. It just stops costing you half an hour to get to it informed.

The phone will still ring at 7:40 on a Tuesday — three jobs, three open loops. That part of the work isn’t going anywhere. What changes is the shape of the answer. Not “let me dig and get back to you.” Just the fixture rev, the CO, the open RFIs — found in the time it takes to read the question, with the source right there underneath. That’s the difference between holding a project in your head and being able, finally, to set it down.