Nearly every general contractor of size keeps a lien log—a spreadsheet, usually on SharePoint or a shared drive, that is supposed to record every lien-related document the company has received. And at nearly every firm, the people who rely on that log privately discount it. They check the source emails before answering a hard question, or they keep a personal side copy for their own projects, which is the surest sign a shared record has failed. The log's problem is rarely its design. It's that a log is only as good as its intake, and manual intake degrades quietly until nobody quite believes the spreadsheet anymore. This article covers what belongs in a master lien log, why shared spreadsheets drift away from reality, and what it takes to keep one continuously trustworthy.
What belongs in the log
The log's job is to answer, quickly and defensibly, the questions that come up when payment friction turns into legal friction: have we received anything from this claimant, on which project, for how much, and where do things stand? Working backward from those questions, a useful log carries at least:
- Notice date and date received. These differ, and both matter—the document's own date anchors statutory analysis, while the received date drives your internal response clocks.
- Document category. Preliminary notice, notice of intent, recorded lien affidavit, release, or correspondence. A recorded instrument is a different animal from a routine notice, and the log must say which is which. (The distinctions and their deadlines vary by state; keep your counsel in that loop.)
- Claimant and hiring party. Who says they're owed, and who brought them onto the project. The hiring party is what connects a second-tier claimant to the first-tier sub whose payment chain broke.
- Project, as your systems name it. Claimants identify projects by street address or the owner's project name. The log needs your canonical name, or filtering by project silently misses records.
- Amount claimed, when the document states one.
- Disposition. Open, resolved, released, escalated—with a date. A log full of notices and empty of outcomes tells you what arrived but not what's still live, and the still-live list is the whole point.
- A link to the source document. The scan itself, named consistently, one click away. Any question the columns can't answer gets answered by the document, provided the document can be found.
Why shared spreadsheets drift
None of the above is hard to set up. The failure is in the maintenance, and it follows a pattern familiar to anyone who has run a shared tracker of any kind.
Entries never happen, because the person who signs for the mail isn't the person who owns the log, and the handoff has no enforcement. Entries happen twice, because two offices each scanned their copy. Concurrent editors overwrite each other, and a row updated on Tuesday reverts on Wednesday when someone pastes over it from an old copy—file-sync conflicts do the same thing without any human error at all. Dispositions go stale, because closing out a row requires knowing an invoice was paid, and that fact belongs to accounting, not to whoever maintains the spreadsheet. And every value in every row was keyed by hand from a scan, so the log inherits every transcription slip—we've written about why those documents are unusually hostile to accurate transcription in The Lien Notice Paper Problem.
Each defect is small. Their sum is a record that is roughly right, and "roughly right" is precisely the standard a lien log cannot meet, because the log exists for disputes, and disputes go looking for the one row that's wrong.
Trust is an intake property, not a formatting property
Teams respond to a distrusted log by redesigning it—new columns, color coding, data validation, a tab per project. This treats the symptom. The log becomes trustworthy when three things are true: every document that arrives enters the log without depending on a person remembering to do it; every value in the log traces to a source document that's one click away; and updating a record costs so little effort that dispositions actually get updated. Meet those conditions and even a plain spreadsheet earns back its authority. Miss them and no amount of formatting will.
That framing points directly at automation, because the three conditions are mechanical. Intake should be a forwarding rule, not a chore. Extraction should be done by software that reads the scan and populates the row—with the transcription verified by the sender, not merely hoped correct. Updates should be as cheap as a one-line email.
How Bex keeps the log current
Bex Liens maintains the master log as a product of automated intake rather than a separate clerical task. Each scanned document forwarded to Bex is read in full—roughly 22 fields extracted, the document type classified, the project fuzzy-matched against your project list—and the log is updated as a consequence. Bex emails its transcription back to the sender for verification, so the data in the row has been confirmed by the party who wrote the document, an accuracy discipline we describe in how Bex meets users where they are.
The log itself is a clean Excel workbook, organized into tabs, fully sortable and filterable, and Bex can write it to SharePoint so it lives where your team already works. Releases close out the matching record automatically, and dispositions that only a human knows—"the Ridgemont invoice was paid"—are handled by telling Bex exactly that, in a plain-English email. Financial coordinators and project accountants don't have to remember to consult the log, either: Bex alerts them on the cadence you choose about what's open and coming due on their projects, with routing rules that can key on category, amount, project, or jurisdiction.
There's also a newer capability worth knowing about, currently in beta: ad-hoc reporting in natural language. Ask Bex for an executive summary of the five largest notices from the last thirty days, or the master log filtered to two projects, and it produces exactly that—and a report you like can be put on a schedule and emailed to the people who need it.
A lien log your team actually trusts is less a spreadsheet achievement than an intake achievement. If your current log is the kind people quietly double-check, we'd like to show you what it looks like when the maintenance is automatic—get in touch below.