Search your job costs straight from the records that created them

A budget line tells you a number was spent. It does not tell you who approved it, against which scope, or whether anyone signed. That context lives in the documents the cost arrived on, and the documents are scattered: an invoice in someone’s inbox, a PO in the accounting folder, a receipt texted up from a gas station, a change order three replies deep in a thread. By the time a question comes up, finding the page behind the number is its own small project. Brad makes the number and its page one click apart.

This is not a small tax. People who build for a living spend roughly a fifth of every week just searching for and gathering information, and a chunk of that is chasing down records that already exist.^[1] In construction specifically, the time lost to data that is hard to find or out of date runs into real money: bad data and the rework it causes were tied to roughly $1.85 trillion of waste across global construction in a single year.^[2] Cost records are a big part of that pile, because a charge with no traceable source is a charge somebody has to relitigate later from memory.

Every cost traces back to the document that authorized it

Brad keeps the thread between a charge and its paperwork intact. Pull up a line and you are one click from the invoice it sat on, the purchase order it was supposed to match, and the change order that made it allowable in the first place. The schedule of values, the PO, the invoice, and the change order stop being four separate piles and become one record you can walk in either direction.

So when a line shows up that the PM swears was never approved, you do not argue from memory across the table. You open the charge, follow it back to change order #14, and read the scope and the signature on the page. The document is the source, and the source is attached. That matters more than it sounds, because the most common cause of construction disputes is a party failing to understand or comply with its contract obligations, and most of those fights are really arguments about what a record actually said.^[3]

Pull every cost tied to a vendor or a cost code

Brad knows the invoice from the framer, the PO you cut for him in March, and the three field receipts the super texted in are the same vendor, even when the name is spelled three different ways across three documents. Ask for everything tied to that vendor and you get the full run, not whatever happened to land in one folder. The same holds for a cost code. “Everything booked against sitework” returns the records that actually carry that cost, gathered from across the project’s email and texts, instead of whatever a spreadsheet happened to capture.

The point is that you are searching the documents themselves, so nothing drops out because somebody forgot to code it or coded it wrong. A receipt that never made it onto the accounting export is still in the record, because Brad read it where it landed. The cost code becomes a way to navigate the documents, not a gate that quietly loses the ones nobody tagged.

Ask “what have we spent on X?” and answer it from the records

Most cost questions will not wait for the month-end close. The owner wants a number on the call. The super needs to know if there is room for one more concrete pour before the line runs dry. The office is chasing why a budget line is over. Brad answers from the documents already in the job’s record, so the number is current to the last invoice that came in, not pinned to the last time a spreadsheet got touched.

And because every figure carries its citation, the answer holds up when someone leans on it. The number comes with the invoices and tickets that add up to it, so whoever you are answering to can check the math against the actual pages. That is the difference between a defensible cost position and a confident guess, and on a job where overruns are the norm rather than the exception, defensible is worth a great deal. Only about three in ten owners’ projects come within ten percent of budget, and the post-mortem on the other seven usually turns on records nobody could produce in time.^[4]

It works over the email and text the costs already arrive on

Receipts, invoices, and approvals do not show up in a tidy queue. They come in as a photo texted from the field, a PDF forwarded by a sub, a change order buried three replies deep in a thread. Brad reads them where they land. You forward or copy it the way you already do, and it files each one into the cost record without anyone changing how they work.

There is no new system to log into, no export-import dance, no asking the field to learn another app. That matters because the apps usually lose. Construction sits near the very bottom of every industry on digitization, and the reason is rarely the software itself; it is that adoption dies the moment a tool asks a busy crew to do data entry.^[5] The documents that make up your costs keep flowing the way they always have, and the searchable record assembles itself behind them.

What the cost search is, and what it isn’t

Brad is document intelligence for construction cost records. It reads, connects, and answers from the receipts, invoices, POs, and change orders you forward it, always with the source attached. It is not an accounting system, an audit, or a guarantee that a charge is correct or approved. It shows you the document so you can judge that yourself, and it flags when an invoice has no matching PO or a charge has no authorizing change order, rather than papering over the gap.

Your project’s documents and the cost record built from them belong to you, and each customer’s workspace stays sealed off from every other. If you have specific requirements about how your cost data is handled or retained, ask us and we will walk you through exactly how it works, rather than point you at a badge.

A cost record is only as good as your ability to find the page behind a number, fast and with the signature on it. Brad does not replace the people who decide what a charge means. It makes sure that when they decide, the document is already in their hand instead of somewhere in a thread from April.