Preliminary Notice and Notice-to-Owner Management on the AP Side

Walk into the AP department of any active general contractor and you will find a folder — physical or digital — full of documents with names like "Preliminary Notice," "Notice to Owner," "Notice of Furnishing," or "20-Day Preliminary Notice." They arrive in the mail, by certified delivery, and increasingly by email. They come from parties the GC has a contract with, and from parties the GC has never heard of. Most AP teams stamp them received, file them, and move on.

That is the wrong instinct. An incoming preliminary notice is not paperwork to be archived — it is a structured disclosure of who is on the project, what they are owed, and what lien exposure the GC and the owner are carrying. Read correctly, the notice file is one of the most useful risk inputs an AP team has. Read carelessly, it is a missed warning that turns into a lien claim, a held-up draw, or a payment dispute that lands on the GC's desk months later.

What a Preliminary Notice Is

A preliminary notice — called a notice to owner in Florida, a notice of furnishing in Ohio and several other states, a pre-lien notice elsewhere — is a formal document that a party performing work or supplying materials sends near the start of its involvement on a project. Its legal purpose is to preserve that party's right to file a mechanics lien later if it is not paid.

In most states, sending the preliminary notice is a precondition to lien rights. A subcontractor or supplier that fails to serve the notice within the statutory window generally loses the ability to lien the property, no matter how legitimately it is owed money. Because the notice protects a real legal right, parties send it routinely and early — usually within the first one to four weeks of starting work or first delivering materials.

The notice itself is informational, not adversarial. It typically identifies the project and owner, the party serving the notice, who hired that party, a general description of the labor or materials being furnished, and sometimes an estimated value. Receiving one does not mean anyone is unpaid or unhappy. It means a party with potential lien rights has put the project on notice that those rights exist.

Why a GC's AP Team Receives Them

Here is the part that confuses AP teams: many of the notices a GC receives come from parties the GC has no contract with. A general contractor hires subcontractors. Those subcontractors hire sub-subcontractors and buy from material suppliers. Those suppliers, in turn, may buy from distributors. Every one of those lower-tier parties has potential lien rights against the project — and to preserve them, they serve preliminary notices.

Statutes generally require the notice to go to the property owner, the original contractor, and often the construction lender. The GC is the original contractor. So the GC's AP department becomes the receiving point for notices from the framing sub's lumber supplier, the electrical sub's gear distributor, the drywall sub's second-tier labor crew, and the rental-equipment company three layers down the chain. The GC never signed a contract with any of them, but their notices land on the GC's desk by statutory design.

This is intentional. The notice system exists so that upstream parties — the GC and the owner — learn who is actually on the project below the surface. A GC that pays attention to incoming notices knows its real exposure. A GC that ignores them is, in effect, choosing not to know.

What an Incoming Notice Tells You

Each notice is a small intelligence report. The most valuable field is the "hired by" line — the party identifying who engaged the sender. When a supplier's notice says it was hired by ABC Electric, and ABC Electric is one of your subcontractors, you have just confirmed a tier-two relationship that may not appear anywhere in your contract files. You now know that ABC Electric's payment health affects whether that supplier gets paid, and whether that supplier can lien your project.

Aggregate the notices for a single project and you get something better still: a tier map. You can see, without asking anyone, that your mechanical sub has three suppliers and a labor broker beneath it, that your concrete sub is buying rebar from a national distributor, and that a rental company has equipment on site through a sub two layers down. That map is the practical scope of your lien exposure. Every party on it can, if unpaid, file a claim against the owner's property — and the owner will look upstream to the GC.

Notice Deadlines Vary by State

Preliminary notice rules are entirely a creature of state law, and they vary widely. The variation matters to AP because part of reading an incoming notice is judging whether it was served in time — a notice served outside the statutory window often does not preserve lien rights, which changes how seriously the GC needs to treat that party's exposure.

An AP team does not need to be a lien-law expert, but it does need to know the rules for the states where the company actually builds. A GC working in three states should have a one-page reference for each: the notice deadline, who must serve, and what a late notice means. When a notice arrives, that reference tells you whether it landed inside the window or outside it — a fact that meaningfully changes the risk that party represents.

Tying Incoming Notices to Sub Payment and Waivers

The reason notice management belongs in AP — not in legal, not in a filing cabinet — is that the notice file should directly inform how the GC pays. The link is the lien waiver. When a notice from a lower-tier supplier tells you that party is furnishing materials through one of your subs, you should not consider that sub fully paid until you have collected waivers that account for that supplier.

In practice this means progress and final payments to a direct sub are conditioned not just on that sub's own waiver, but on waivers from the lower-tier parties whose notices you have received under that sub. If your electrical sub generated three supplier notices, a final payment to that sub without three corresponding lower-tier waivers leaves the GC exposed: any of those suppliers could still lien the project even though the sub above them has been paid in full.

The same logic applies to retention and final closeout. Before releasing retainage on a sub's scope, the notice file tells you which lower-tier parties were in play and therefore which final unconditional waivers you should have in hand. A GC that releases retention without reconciling against the notices it received is releasing money while a known lien path is still open.

Tracking Notices Against the Vendor and Sub List

A notice file only works as a control if it is organized so the cross-checks above are fast. A shoebox of PDFs sorted by date is nearly useless at payment time. The notice file needs to be structured around two keys: the project, and the direct subcontractor through whom each lower-tier party connects to the GC.

This is exactly the kind of cross-referencing that becomes unmanageable on paper and trivial in software. An AP platform that captures incoming notices, links each one to a project and a direct sub, tracks state-specific deadline windows, and ties each notice to the corresponding lien-waiver record turns the notice file into a live exposure view. The AP team stops asking "do we have all the waivers?" and starts seeing, per sub and per project, exactly which notices are still unmatched. The notice stops being correspondence to file and becomes a gating input to the payment run.

Bottom Line

Preliminary notices and notices to owner are not nuisance mail. Each one is a disclosure of a party with potential lien rights against a project the GC is responsible for. The AP team that files them unread is throwing away a free map of its own lien exposure. The AP team that logs them, maps them to direct subs, checks them against state deadlines, and reconciles them against lien waivers before paying turns that map into a control — one that catches an unrecognized lower-tier claimant before it becomes a lien, and prevents a final payment from going out while a known lien path is still open. It costs a structured log and a habit, and it prevents the kind of surprise that closes out a project months late.