Lien waiver exchange & deadline tracking

The cycle starts itself: a pay application approved in the construction platform — or simply the monthly cycle date — wakes the project's task. The subcontracts, schedule of values, and notice log are already attached from last month; the task persists across cycles.

Grain rebuilds the party ledger — 31 subs, their tiers, notices, waivers on file, payment status — and runs the statutory rulebook per state. The forms are prescriptive: waiver language that deviates from the statute is void, and asking a sub to waive rights on money that hasn't cleared is the one mistake the gate never lets through.

The facts, per party and per state: what's due on the pay app, what's on file, which clocks are live. The checks are equally plain — everything that matches, the two subs with no waiver at all, and the one request blocked until a payment clears.

Out comes the month's exchange, packaged: thirty pre-filled statutory forms with per-state language, the request emails, an exceptions memo for the ones held back, and warnings for the deadline windows that matter. Validations catch a form-statute mismatch or an amount that disagrees with the pay app before any request is marked sendable; an independent pass re-walks every party on the pay app against the packet.

Dana approves the batch in the chat and moves on — and asks Nia the questions a spreadsheet can't answer, like which windows tighten if completion records this week. When Ridgeline's payment clears, Nia wakes the task, flips the conditional to an unconditional request, and asks once for approval. A Notice of Completion recorded mid-cycle re-runs the warnings overnight.