Preliminary Notice

Definition — what it is

A preliminary notice is a document a contractor, subcontractor, or supplier serves early in its involvement on a project — typically on the owner, general contractor, and sometimes the lender — to preserve its future right to file a mechanic's lien or make a payment-bond claim if it is not paid. In many states, serving a valid preliminary notice within a strict statutory window (commonly 20 days from first furnishing labor or materials) is a mandatory precondition to lien or bond-claim rights, and failing to serve it forfeits those rights entirely regardless of how much money is owed. It is a protective, forward-looking instrument, not a demand for payment or an accusation of nonpayment. A preliminary notice is not a lien and does not encumber the property — it is the ticket that keeps the option of a lien alive, and it must usually be served whether or not any payment problem yet exists.

Also known as: Prelim, Preliminary 20-Day Notice, Notice to Owner, Notice of Furnishing, Pre-Lien Notice

Why it matters — what it protects

The preliminary notice is a precondition to getting paid on distressed projects, and it must be served before anyone knows the project will go bad. In states that require it, a party that skips the notice has no lien or bond-claim leverage when payment stops, no matter how valid the debt. Because it must be sent at the start of the work, when relationships are good and no one anticipates a problem, it is the classic protection people neglect precisely when they most need to send it.

It is bounded by hard statutory deadlines that do not forgive good intentions. The window — frequently 20 days from first furnishing, with variations by state and by role — is unforgiving: serve it a day late and the lien rights for the earlier work may be permanently lost. There is no discretion and no equitable rescue for a missed statutory notice in most jurisdictions, which is why calendaring the deadline from the first-furnishing date is essential.

It levels the payment chain by giving lower tiers visibility and standing. The notice tells the owner and lender exactly who is furnishing to their project, so they can protect themselves through joint checks or by confirming payment flows down. For the sender, it converts an anonymous supplier several tiers down into a party with recognized lien standing, which materially changes how seriously its invoices are treated.

Getting the notice's content and service method right is itself a legal act, because defects invalidate it. Many statutes prescribe the required recipients, the exact information, the service method (often certified mail with proof), and the timing, and a notice that omits a required party or uses the wrong service method can be as worthless as no notice at all. The discipline is not just sending something — it is sending the statutorily correct thing to the statutorily correct parties on time.

Lifecycle — how it moves

1. First furnishing

   The clock starts the day the party first delivers labor or materials to the project. Establishing and documenting this date is essential, because every deadline runs from it and disputes over it decide whether a notice was timely.

2. Project and party information gathering

   The sender identifies the correct legal owner, the general contractor, the lender if any, and the accurate property description. Wrong or missing party information is a leading cause of defective notices.

3. Notice preparation

   The notice is prepared in the form the governing state requires, with the statutorily mandated content — the parties, the property, a description of the labor or materials, and often an estimate of value. Form defects here invalidate the protection.

4. Service within the window

   The notice is served on all required recipients within the statutory deadline, by the required method — commonly certified or registered mail with return receipt, though some states allow other proof of delivery. Late or improperly served notices are void.

5. Proof of service retained

   The sender keeps proof of service — certified-mail receipts, delivery confirmations, affidavits — because in a later lien fight the burden is on the sender to prove the notice was validly served on time.

6. Ongoing furnishing tracking

   The party tracks whether additional or changed scope requires a supplemental notice, since new or expanded furnishing can fall outside an original notice's coverage in some states.

7. Payment or dispute

   If paid, the notice simply lapses unused, having cost little. If not paid, the preserved notice is the foundation for a timely mechanic's lien or bond claim, which have their own subsequent deadlines.

8. Escalation to lien or claim

   Where payment fails, the party proceeds — within the separate lien-recording or bond-claim deadlines — to file the lien or claim the preliminary notice preserved. No valid preliminary notice, no valid lien in the states that require it.

Anatomy — the data it carries

First-furnishing date

The date labor or materials were first supplied, from which the notice deadline runs. The single most important fact to establish and document.

Claimant/sender

The party preserving its rights and its role (sub, sub-sub, supplier). Role can change the required recipients and the deadline.

Owner information

The correct legal owner of the property. A notice to the wrong owner entity can be void; public projects change the recipient entirely.

General contractor / hiring party

The party the sender contracted with and, in the chain, the GC. Required as a recipient in most statutory forms.

Lender / construction lender

Where a construction loan exists, the lender is often a required recipient so it can protect its disbursements. Omitting it can invalidate the notice.

Property description

The project's address and, in many states, the legal description sufficient to identify the property for a future lien.

Description of labor/materials

What the sender is furnishing. Must be accurate enough to tie the future lien to the work actually performed.

Estimated value

An estimate of the total value to be furnished, required in some states. It puts the owner on notice of the potential exposure.

Service method and date

How and when the notice was served, per the statute — often certified mail with return receipt. Wrong method can void an otherwise perfect notice.

Proof of service

The receipts and confirmations proving valid, timely service. The sender bears the burden of proof in any later dispute.

Statutory form reference

The specific state statute and form the notice follows. Using another state's form or generic language risks invalidity.

Failure modes — how it breaks

Never served at all

The party assumes it will be paid, so it never sends the notice in a state that requires it. When payment stops months later, it discovers it has no lien or bond-claim rights whatsoever, and the debt is unsecured.

Served late

The notice goes out after the statutory window from first furnishing has closed. In most states the earlier work is permanently unprotected, and no argument about good faith or actual knowledge revives it.

Wrong or missing required party

The notice omits the construction lender or names the wrong owner entity. A statute that requires those recipients treats the omission as a fatal defect, and the notice protects nothing despite being sent on time.

Improper service method

The notice is emailed or sent by regular mail where the statute requires certified or registered mail with proof of delivery. The service is invalid, and the sender cannot prove timely, proper delivery when it matters.

Wrong first-furnishing date

The sender miscalculates the deadline because the first-furnishing date is undocumented or misremembered. A notice believed timely is actually late, and the error is invisible until a lien is challenged.

Public project treated like private

On a public job, where property cannot be liened, the party serves a private-project lien notice instead of the required bond-claim notice. It preserves a right that does not exist and forfeits the one that does.

No proof of service retained

The notice was served correctly but the certified-mail receipts and confirmations are lost. In the lien fight, the sender cannot carry its burden to prove valid, timely service, so the notice is treated as if it never happened.

Metrics — how it is measured

Notice service rate

Share of projects where a required preliminary notice was actually served. In notice-required states, gaps here are direct forfeitures of lien rights.

On-time service rate

Share of notices served within the statutory window from first furnishing. The metric that most directly protects lien and bond-claim rights.

Party-completeness rate

Share of notices served on all statutorily required recipients (owner, GC, lender). Catches the fatal omitted-lender defect.

Proper-service rate

Share served by the statutorily required method with proof retained. Measures whether the notice would survive a challenge.

First-furnishing documentation rate

Share of projects with a documented, defensible first-furnishing date. The foundation of every deadline calculation.

Days from first furnishing to service

Elapsed time to serve, against the statutory limit. A tightening buffer signals process risk before a deadline is actually missed.

Preserved-rights realization

Share of nonpayment situations where the preserved notice actually enabled a valid lien or claim. The outcome measure of the whole program.

The AI shift — what actually changes

Conversational

You can ask the notice program where it stands: which active projects in notice-required states have no preliminary notice served, which are approaching the statutory deadline from first furnishing, and which served notices are missing a required recipient like the lender — with the specific project, deadline, and defect identified.

Generative

Notices are generated in the correct state statutory form with the owner, general contractor, lender, property description, and labor/material description populated from project data, and the deadline computed from the documented first-furnishing date, so a person reviews a conforming notice rather than researching a form each time.

Orchestrated

The notice becomes tied to the project setup: the first-furnishing date captured when work or delivery begins, the required recipients and service method derived from the project's state and public/private status, the deadline calendared automatically, and proof of service filed against the project so the record is complete if a lien later follows.

Autonomous

The notice perimeter runs itself: first-furnishing dates captured at project start, deadlines calendared and escalated well before they close, draft notices prepared in the correct state form for every qualifying project, and proof-of-service tracked — while a human verifies the party and property information, decides where a notice is required, and authorizes every service, because a wrong or missed notice is a forfeited legal right.

Prompts — put it to work

Tool-agnostic and copy-ready. Adapt the specifics — thresholds, contract windows, cost codes — to your own project before you run them.

Conversational — Checking whether your lien rights are protected across active projects.

Review our active projects and tell me where our preliminary-notice protection stands. For each project in a state that requires a preliminary notice, tell me whether we have served one, the documented first-furnishing date, the statutory deadline that runs from it, and how many days remain. Flag every project with no notice served, every one approaching its deadline, and every served notice that appears to be missing a required recipient such as the construction lender or that used an improper service method. Separate public projects, where we need a bond-claim notice rather than a lien notice, and tell me if any of those are mishandled.

What good output looks like: A project-by-project protection status with deadlines and days remaining, flagging unserved, late-risk, and defective notices and separating public bond-claim situations from private lien ones.

Follow-ups:

• Which notices must go out this week to stay within the statutory window?
• For the projects with no documented first-furnishing date, what do we need to establish it?
• Which served notices would not survive a challenge and why?

Generative — A new project just started and you need the notice drafted correctly.

Prepare a preliminary notice for our new project in this state. We are a second-tier subcontractor and first furnished materials on the date provided. Use the state's required statutory form and language, name all statutorily required recipients — the property owner, the direct contractor we contracted with, the general contractor, and the construction lender — with the information provided, include the property description, describe the labor and materials we are furnishing, and include an estimated value where the statute requires it. State the exact statutory service deadline computed from the first-furnishing date, specify the required service method, and flag any recipient information that is incomplete or that I need to verify before service.

What good output looks like: A conforming preliminary notice in the state's statutory form with all required parties and content, the computed service deadline, the required service method, and flags on any information needing verification.

Follow-ups:

• What proof of service do we need to retain to survive a later challenge?
• Would a change in our scope later require a supplemental notice in this state?
• Prepare the equivalent bond-claim notice if this were a public project instead.

Orchestrated — Wiring preliminary notices into project setup so none are missed.

For every new project we take on, tie preliminary-notice protection to project setup. From the project's state, its public-or-private status, and our role and tier, determine whether a preliminary notice (or bond-claim notice) is required, who the statutorily required recipients are, the required service method, and the deadline measured from the first-furnishing date we capture at kickoff. Cross-check the owner, general contractor, and lender information we hold for completeness and accuracy, and identify what is missing. Return, for each new project, a notice-requirement determination with the deadline, the recipient list, the required method, and a gap list of information we still need before a valid notice can be served.

What good output looks like: A per-project notice-requirement determination with recipients, method, deadline, and an information-gap list, tying the notice obligation into project setup rather than leaving it to memory.

Follow-ups:

• Generate the draft notices for the projects that are ready.
• Which projects are missing lender or owner information blocking service?
• Build me the calendar of all notice deadlines across new projects.

Autonomous — Standing policy for never missing a preliminary-notice deadline.

Manage preliminary-notice protection across all projects under these rules. At every project kickoff, capture and document the first-furnishing date, determine from the state, public/private status, and our tier whether a notice is required and who must receive it, and calendar the statutory deadline. Prepare a draft notice in the correct statutory form for every qualifying project and escalate to the credit manager at 10 days before the deadline and again at 5 days if it has not been served. Track proof of service and file it against the project. Flag any project missing required owner, GC, or lender information. Never serve a notice yourself, never decide that a required notice can be skipped, and never rely on an undocumented first-furnishing date — route the party/property verification and every service authorization to a named human with the draft and the deadline.

What good output looks like: A continuously managed deadline calendar with prepared draft notices and escalations, where humans verify party/property data and authorize every service, backed by a complete proof-of-service record.

Follow-ups:

• Show me every notice deadline in the next 15 days and its readiness.
• Which projects still lack a documented first-furnishing date?
• List all draft notices awaiting human authorization to serve.

Get the full Construction AI Prompt Catalog — every prompt in the library in one document.

Maturity — locate yourself honestly

0. Level 0 — Trust and hope

   Notices are sent rarely or never because payment problems are not anticipated, so lien rights are routinely forfeited on the projects that go bad.

1. Level 1 — Manual and reactive

   Notices are sent when someone remembers, deadlines are tracked in a spreadsheet, and defects in party, form, or service surface only when challenged.

2. Level 2 — Linked

   Notice requirements and deadlines are tied to project setup and first-furnishing dates, with required recipients and service method derived from state and role.

3. Level 3 — Assisted

   Conforming state-form notices are generated, deadlines are computed and escalated, and missing-party and improper-service risks are surfaced for review.

4. Level 4 — Operated

   Deadline calendaring, draft preparation, escalation, and proof-of-service tracking run unattended, while humans verify party/property data and authorize every service.

Common questions

If I have not been paid a cent, why must I send a preliminary notice at the start?

Because in many states the preliminary notice is a precondition to lien and bond-claim rights that must be served within a short window from first furnishing, long before any payment dispute arises. If you wait until you are unpaid, the statutory deadline has usually already passed, and your lien rights are gone regardless of how valid the debt is. The notice is not a demand or an accusation; it is a routine protective step sent at the beginning of essentially every project in a notice-required state, whether or not you expect a payment problem.

What happens if I serve the preliminary notice late?

In most states a late notice forfeits lien or bond-claim rights for the labor and materials furnished before the notice was properly served, and in some states it can defeat the rights entirely. The statutory deadlines are generally strict and unforgiving, with no equitable exception for good faith or for the owner's actual knowledge of your involvement. That is why the first-furnishing date must be documented and the deadline calendared from it, and why serving early rather than at the last moment is the safe practice.

Do preliminary notices work the same way on public projects?

No. Public property generally cannot be liened, so on public work the protection is a claim against the contractor's payment bond rather than a mechanic's lien, and the required notice is a bond-claim notice with its own recipients and deadlines under the Miller Act or the applicable state Little Miller Act. Serving a private-project lien notice on a public job preserves a right that does not exist while missing the bond-claim notice that does, so identifying the project as public or private is the first thing to get right.