"Lien waiver" and "lien notice" sound like two forms of the same paperwork, and the two get conflated constantly—in conversation, in software marketing, and occasionally in the org chart, where one coordinator inherits "liens" as a category and discovers it means two unrelated jobs. They are opposites in nearly every way that matters. A waiver is a document you collect; a notice is a document that arrives. One travels with money going out; the other anticipates a claim coming in. Confusing them is more than a vocabulary slip, because each workflow needs its own process and its own tooling, and the tooling market has served one side far better than the other.
Lien waivers: documents you collect
A lien waiver is a claimant's written surrender of lien rights, in exchange for payment. When you pay a subcontractor or supplier, you collect a waiver so the paid party can't later encumber the project for the same money. Waivers come in four familiar variants along two axes: conditional versus unconditional (does the waiver take effect only once the payment actually clears, or immediately upon signing?) and progress versus final (does it cover one payment period, or the whole scope through completion?). Several states prescribe statutory waiver forms and restrict what a waiver may say; as with everything lien-adjacent, the specifics are state law and belong with your counsel.
Operationally, waivers are an outbound-payment workflow. They ride the monthly pay-application cycle: a sub's application isn't complete without waivers from the sub and often from its own lower-tier subs and suppliers, and your accounting team reconciles collected waivers against payments issued. The risk of a broken waiver process is paying twice—money out the door to a first-tier sub, followed by a valid claim from an unpaid second-tier supplier whose waiver was never collected.
Lien notices: documents that arrive
A lien notice is the mirror image: a document someone sends to you, asserting or preserving a right to payment from the project. The category spans a spectrum of escalation. A preliminary notice, required in most states near the start of a claimant's work, preserves future lien rights and is usually routine—we've written about why it's also genuinely useful intelligence for a GC in How GCs Should Track Incoming Preliminary Notices. A notice of intent to lien signals that a payment dispute is live. A recorded lien affidavit is the escalation everyone fears: a filed instrument that clouds title and draws immediate attention from owners and lenders. And a release, arriving after resolution, closes the record.
Operationally, notices are an inbound-intake workflow. Nobody schedules their arrival; they show up by certified mail and email, on statutory forms and attorney letterhead, keyed to whatever the claimant calls your project. The work is receiving, reading, transcribing, matching to a project, routing to the responsible coordinator, and watching for the routine ones that turn into escalations. The risk of a broken notice process is being surprised—learning about a recorded lien from your owner rather than your log, then reconstructing months of history from inbox searches under deadline pressure.
Different deadlines, different risks
The two workflows also fail on different clocks. Waiver risk accrues at payment time: each check issued without the right waivers in hand is a discrete, quantifiable exposure, and the process gets natural enforcement from the payment cycle itself, since withholding payment until waivers arrive is standard practice. Notice risk accrues silently. A preliminary notice ignored costs nothing for months, right up until the claimant behind it records a lien, at which point response deadlines—which vary by state and are frequently short—start running whether or not anyone on your side is watching. Deadlines on both sides differ enough across jurisdictions that no general article should be your source for them; the operational point is that the waiver side enforces itself through payments while the notice side has no built-in enforcement at all. It has to be given one.
The tooling gap
Software vendors noticed the waiver side long ago, for a structural reason: waivers sit inside the payment workflow, and payment workflows are where construction financial software already lives. Pay-application platforms and construction-payment suites generate waiver requests, track collection against payments, and manage the exchange with subs as a matter of course. If your waiver process is manual today, mature tools exist, and they largely solve it.
The notice-intake side got no such attention. Notices arrive outside any system—on paper, addressed to a mailroom—and belong to no billing cycle, so no payment platform ever had a natural claim on them. The default remains what it has been for decades: someone opens the mail, someone scans it, and someone keys what they can into a shared spreadsheet whose reliability decays in all the ways we cover in Building a Master Lien Log Your Whole Team Trusts. The market built tools for the documents you send and left you alone with the documents you receive.
Covering the intake side
That receiving side is what Bex Liens exists to automate. Forward each scanned document to Bex and it extracts roughly 22 fields, classifies the document type—distinguishing a recorded, notarized instrument from a routine notice—matches the project against your project list, and emails its transcription back to the sender for verification. The master log stays current without anyone maintaining it, coordinators get alerted on the cadence you set, and routing rules can push a filed lien down a faster escalation path than a preliminary notice. Releases close out their matching records automatically. It runs entirely over email, which means your existing mail system keeps the complete audit trail—an arrangement whose security properties we describe in Bex's approach to data security and reliability.
Bex Liens doesn't process outbound waivers, and doesn't need to—that side of the house is well served. If the inbound side at your firm still runs on a scanner and a spreadsheet, that's the gap worth closing, and we'd be glad to demonstrate on your own stack of notices. The email link is below.