Nearly everything written about preliminary notices is addressed to the party sending one—the subcontractor or supplier protecting its right to payment. Almost nothing is written for the general contractor on the receiving end, even though every notice that gets sent has to be received, read, and acted on by someone. This article is for the receiver. If your firm builds commercial work of any size, preliminary notices are arriving at your office right now, and the difference between a good intake process and no process shows up months later, when a payment dispute turns into a recorded lien.
What a preliminary notice actually tells you
A preliminary notice is a document sent near the start of a claimant's work that preserves its right to file a mechanic's lien later if it goes unpaid. Most states—around forty, by common counts—have some form of the requirement, though the names, deadlines, and covered parties vary widely (see the overview on preliminary notices; for anything consequential, consult construction counsel licensed in the project's state).
It's tempting to treat these as junk mail, since most claimants will simply be paid in the ordinary course and nothing further will happen. That's a mistake, because the notice carries information a GC often has no other way to get. Your contract is with your first-tier subs. The preliminary notices tell you who is actually furnishing labor and material below that tier—the second-tier sub your drywall contractor brought on, the lumber supplier behind your framer—and each one identifies a party who can encumber the project if someone above them in the chain fails to pay. A complete file of notices is, in effect, a census of everyone who expects money from your project. When you later collect lien waivers or respond to a payment claim, that census is what tells you whether the name in front of you belongs to the project at all.
Why intake usually fails
The failure mode is rarely a decision to ignore notices. It's the absence of a defined path for them. A notice arrives by certified mail at a regional office, gets signed for by whoever is near the front desk, and is scanned to a shared folder or forwarded to a project team that may or may not recognize the project name on it. Claimants frequently identify projects by street address or by the owner's name for the job, not by the name in your accounting system, so matching the notice to a project takes actual attention. If the person doing the matching is busy—and they are always busy—the notice sits.
The second failure is transcription. Even when notices reliably reach one person, that person has to read a scanned document and key its contents into a tracking spreadsheet. The formats vary from state-mandated forms to attorney letterhead, the scans vary in quality, and the fields that matter most—amounts, dates, the claimant's relationship to the project—are exactly the ones where a typo does damage. We've written more about that problem in The Lien Notice Paper Problem.
What a good intake process looks like
A workable process has a few defined parts, none of them complicated in principle:
- A single point of entry. Every notice, regardless of which office signs for it, gets scanned and sent to one address or queue. Nothing stays in a desk drawer.
- A consistent record. For each notice: the date on the document, the date received, the claimant, the party that hired them, the matched project, the amount claimed if stated, and the document type. Date received matters independently of the document date, because response windows and internal follow-ups run from it.
- Routing to an owner. Each project has a financial coordinator or project accountant who is responsible for its notices. The record isn't complete until that person has seen it.
- A follow-up discipline. The dangerous notices are the ones that stop being routine—a notice of intent to lien, or a recorded lien affidavit, on a project where a preliminary notice arrived months earlier. Someone has to be watching for that escalation, which requires the earlier notice to be findable in seconds, not buried in a scan folder.
The record-keeping half of this is a master log, and we've covered what belongs in one—and why shared spreadsheets quietly diverge from reality—in Building a Master Lien Log Your Whole Team Trusts.
When a notice stops being routine
Most preliminary notices expire quietly: the claimant is paid, the deadline to lien passes, and the file closes itself. The intake process earns its keep on the exceptions. A recorded lien affidavit is a different legal instrument from a preliminary notice—it clouds title, alarms owners and lenders, and starts clocks that are unforgiving. A GC with a well-kept notice file can respond to one in an afternoon, pulling the claimant, the hiring party, the payment history, and any waivers on file from a single log. A GC without one starts the same afternoon by searching inboxes. State law governs every deadline in this paragraph, and the variations are substantial, so treat the specifics as a matter for your attorney rather than a blog post.
Automating the intake
Everything above can be done by hand, and at a firm receiving a handful of notices a month, it probably should be. At the volume a regional or national GC sees, the transcription and routing become a real clerical cost, and the consistency the process depends on is exactly what tired humans are worst at. Bex Liens automates the receiving side: forward each scanned notice to Bex, and it extracts roughly 22 fields per document, classifies the document type, fuzzy-matches the project against your project list, emails a clean transcription back to the sender for verification, and maintains the master log. Routing rules—by category, amount, project, or jurisdiction—push urgent documents to the right coordinator without anyone checking a calendar, and recorded instruments can trigger a faster escalation path than routine notices. Because the whole exchange runs over email, your existing mailbox retains a complete audit trail of every document and every decision, a property we discuss in Bex's security and observability posture.
Preliminary notices are one of the few early-warning systems a construction project comes with. If yours are being signed for, scanned, and forgotten, we'd be glad to show you what an automated intake looks like on your own documents—reach out below.