Subcontractor lien notice deadline by state: a national overview of the remaining forty

A mechanic's lien attaches to the property, not to the GC. That is the leverage — but it runs on a per-state clock, and no legislature has harmonised its preliminary-notice or lien-claim deadline with any other. There is no federal mechanic's lien law. A subcontractor working across state lines keeps ten different clocks in their head for the top ten states, and a separate map for the other forty. The top-ten breakdown — California, Texas, Florida, New York, Illinois, Georgia, North Carolina, Pennsylvania, Arizona, Ohio — sits in our earlier subcontractor lien rights by state read. This one sweeps the rest. Drumtap is not a statutory calendar tool and does not publish a cross-state statutory reference today — the controlling statute for any specific job sits with construction counsel. The point is to give the sub who works across more than three states a regional rhythm they can keep in their head, then point them at the right counsel before the window closes.

The preliminary-notice row maps cleanly by region. In the Northeast, most states run a roughly twenty-to-sixty day preliminary notice after first labor; Rhode Island is tighter at roughly twenty days before the second progress payment; New Jersey is the regional outlier — no preliminary notice on most private projects, but strict service rules on the lien itself; New Hampshire sets a forty-five day clock. In the Mid-Atlantic and Southeast, Virginia asks for a Notice to Owner at or before the second month; South Carolina runs one of the tighter clocks — Notice of Mechanic's Lien within fifteen days of first labor; Maryland sits at ninety days; Alabama, Mississippi, and Tennessee each run the thirty-to-forty-five day range; Louisiana publishes no statutory preliminary notice on private work but enforces a tight recording window. In the Midwest, Minnesota runs the tightest clock in the country — a ten-business-day preliminary notice plus a separate mortgagee notice. Iowa, Kansas, and Missouri each ask for roughly twenty days; Wisconsin, Michigan, and the Dakotas publish moderate preliminary-notice rules with carve-outs. In the Mountain-West, Utah, Nevada, and New Mexico each set preliminary-notice clocks of fifteen to twenty days; Colorado compresses the recording window hard even though it publishes no statutory preliminary notice. In the Pacific-Northwest, Washington asks for a roughly ten-day notice of right to claim lien before recording; Oregon requires written preliminary notice to the lender and owner at the start of work with a separate pre-lien notice before recording. These are textbook regional rhythms — the actual statute always controls, and many states have carve-outs for residential, public, and direct-contractor scenarios that change the answer.

The claim-of-lien row follows a similar regional pattern. The Northeast typically measures the recording window from last labor or substantial completion: most states cluster around roughly ninety days; New Jersey sits at twelve months (one of the generous clocks); the District of Columbia at 90 days (not strictly a state, but every project inside it is bound by it). The Southeast is more variable: Louisiana at sixty days from substantial completion is tightest in the region; Alabama, Mississippi, and Kentucky each sit at roughly six months; Tennessee at 90 days. The Midwest mostly measures from last labor: Michigan, Iowa, Indiana, and North Dakota at ninety days; Minnesota and South Dakota at 120 days; Nebraska at four months; Wisconsin, Missouri, and Kansas each at six months (one of the longer clocks in the country). The Mountain-West compresses: Colorado at four months from completion, Utah at 180 days from last labor, Idaho at 90–120 days, Montana at 90 days, Wyoming at 150 days, New Mexico at 120 days. The Pacific-Northwest is moderate: Washington at ninety days from last labor (or substantial completion, whichever is later); Oregon at 75 days from completion; Alaska at 120 days. The rhythm underneath: the recording clock is almost always shorter than the trade expects it to be, and almost always measured from a project milestone that has nothing to do with the pay-app cycle you keep your own books against.

The operational fact underneath both rows is the same: surface the underpayment inside the window, prove the gap, and act on it before the clock closes. Drumtap's reconciliation does that. Every QuickBooks row is paired against the corresponding portal CSV row for the same pay-app; the change-order trail and the conditional/unconditional waiver status sit between them; the discrepancy list sums into the dollar amount of the dispute. That packet ships pre-filled inside the pay-app window, before the next month-end ages it out — and well before the preliminary-notice clock or the recording clock on whichever state the project sits in runs out. For the deeper read on what Drumtap catches at the line-item level — the G-01, G-02, and G-04 status codes, the SOV mechanics, the change-order sequencing — start with portal reconciliation: the core problem Drumtap solves and the how to read a GC payment application read. For the per-state statutory reference Drumtap pairs against for a specific job, the FAQ on mechanic's-lien and preliminary-notice deadlines calls out the Drumtap posture clearly: reconciliation yes, cross-state statutory calendar no.

The fastest way to lock in the Founding 25 rate is the /pricing page — Starter ships today at $199/month on the manual-upload reconcile, with Pro ($349/month, Coming next) and Auto ($499/month, Coming next) holding the reservation queue. Reserve the Founding 25 rate or sign up for Starter on /signup — Drumtap reads CSV uploads today, builds the evidence package per discrepancy, and you send it yourself.