Lien waiver tracking for contractors: a release for every payment.

On a California job, a subcontractor or supplier who has served a preliminary notice is telling the property owner it could file a lien claim if it goes unpaid. A payment to the drywall contractor says nothing about whether the drywall contractor paid for the board. What CSLB tells owners to collect, payment by payment, is a signed release from each potential claimant, and the builder, as the direct contractor, is the one expected to gather them. So every payment needs its matching release in the file before the next draw is assembled.

That is a tracking job, and a supervised AI assistant can keep the tracker: logging notices as they arrive, pairing each payment with the releases it needs, drafting requests for the missing ones and listing the gaps before a draw. It never signs or sends a release, never submits a draw and never contacts the lender. This article is not legal advice. Lien rules vary by state, the California details below are one state's, and the builder confirms every deadline with a lawyer.

The Contractors State License Board (CSLB) writes its mechanics lien guidance for property owners, which makes it a useful list of what an owner in California will expect a builder to produce. As checked on 15 October 2026, it says the following.

• PRELIMINARY NOTICE

  Required from subcontractors and suppliers if there is a chance they may need to file a lien; without it they lose the right to file one. Laborers and the direct contractor do not give one.

• ITS TIMING

  It can be delivered before work begins or supplies arrive and up to 20 days afterwards. A later notice is allowed, but then payment is only required for work done from 20 days before it was delivered.

• KEEP AND DATE THEM

  CSLB's tip to owners is to save every preliminary notice and note the date it was received, to keep track of who is owed and when they are paid.

• CONDITIONAL RELEASE

  Before making a payment, get a signed conditional release from the possible lien claimants.

• UNCONDITIONAL RELEASE

  After payment, an unconditional release signed by each claimant paid for that portion of the work, and signed by the actual claimant.

• WHO COLLECTS

  The direct contractor is required to get the release signatures for the owner from the potential lien claimants.

• WITHHOLDING

  The owner may withhold the next payment until the unconditional releases for the previous payment have arrived.

• JOINT CHECKS

  A check made payable to both the contractor and the sub or supplier, after comparing the bill with the contract's payment schedule and the preliminary notices.

• NOTICE OF COMPLETION

  Filed by the homeowner with the county recorder within 15 days of completion, it shortens the time to record a lien from 90 to 60 days for a contractor and from 90 to 30 days for a subcontractor or supplier.

The state model follows one payment to one subcontractor. The assistant holds only the steps that are paperwork about paperwork; every step that moves money or carries a signature belongs to a person.

1. 01

   Pay application received

   Owner

   Tracker Bot

   Advances when

   The pay application is logged against its line in the contract's payment schedule, and a conditional release request is drafted

2. 02

   Conditional release requested

   Owner

   The builder

   Advances when

   The builder checks the amount and sends the request to the sub

3. 03

   Conditional release on file

   Owner

   Tracker Bot

   Advances when

   The signed release is attached and its amount compared with the payment the builder intends to make

4. 04

   Payment made

   Owner

   The builder

   Advances when

   The builder pays and records the date and amount; no Bot makes or confirms a payment

5. 05

   Unconditional release outstanding

   Owner

   Tracker Bot

   Advances when

   A request is drafted for the builder to send, and the line stays on every gap list until the release arrives

6. 06

   Closed

   Owner

   The builder

   Advances when

   The builder confirms the unconditional release is signed by the actual claimant and marks the line closed

   Ends when

   Closes only when the unconditional release for this payment is on file

Consider an illustrative custom home in California. The drywall hang-and-finish contractor submits a pay application for hanging the board, and early in the job a preliminary notice arrived from the supplier who delivered that board to the drywall contractor. The tracker therefore holds two lines for this one stage: the drywall contractor's own releases, and the supplier's.

The builder gets the drywall contractor's conditional release, pays, and receives the unconditional release a week later. The drywall line closes. The supplier's line does not, because nothing in the file says the supplier was paid, and its notice told the owner it could file a lien claim if it was not. The gap list before the next draw shows exactly that: one notice, no release.

What to do about it is the builder's decision, perhaps a request for the supplier's release through the drywall contractor, or a joint check on the next payment, and the builder's lawyer is the right person to ask which. The assistant's part is to make sure the open line cannot be overlooked because the more visible payment went through.

The tracker is a reviewable spreadsheet with defined columns, one of the result types Grok Bot's documentation suggests asking a Bot for. The Tracker Bot is a named Bot the builder creates in Grok Bot, which works on the account's cloud computer; the tracker's columns and the gap check are Aevrion's pattern, not a product feature. The tracker itself lives in the builder's own files and is read fresh on every run, because the documentation is clear that what a Bot remembers is no substitute for the authoritative record. Signed releases can be attached to the Bot's conversation as PDFs or images, and reading a construction accounting or document system directly is a custom integration, built and tested for that system, where its vendor's terms and API allow.

Based on the Grok Bot documentation at docs.x.ai as checked on 15 October 2026. Its statements on Bot rules, Bot-to-Bot messaging, routine triggers, connected apps, approval expiry and payments were rechecked against docs.x.ai and Cursor's help pages on 26 October 2026. The trade examples are Aevrion's illustrations, not documented Grok Bot use cases. Aevrion Ops is an independent consultancy. It is not affiliated with, endorsed by or a partner of xAI, SpaceXSI or Cursor. Grok Bot is named here only to describe it.

A gap check suits a routine: the same preparation run on a schedule the builder sets, two working days before each draw date the builder has entered. The routine reads the tracker and the lender's draw checklist, which the builder entered once from the loan documents, and returns one list: payments from the previous draw with no unconditional release, preliminary notices with no release at all, conditional releases whose amount differs from the payment made, and checklist items not yet on file.

When the routine is set up, the builder confirms what happens if the tracker cannot be opened, and the answer is that the routine reports the failure and stops rather than work from an old copy. It drafts release requests as editable emails for the builder to check and send. Because an approval raised by a routine with nobody watching expires after about ten minutes (Cursor's help pages say thirty) without running, the routine is designed to draft and list, never to send.

The tracker prepares; it does not decide. Whether to withhold a payment from a sub, write a joint check or respond to a lien claim, and which deadline applies, are legal and financial decisions for the builder and the builder's lawyer; recording a Notice of Completion is the property owner's step, and the tracker only notes whether and when the owner has recorded one. No Bot signs, sends or alters a release, submits a draw request, or writes to the lender. Payment confirmations go through a human taking over the computer, and the bank and lender logins belong in a separate user account or with the builder alone, because every Bot on an account shares one computer and its sign-ins. Cursor's help pages add a Vault, where saved logins and cards let a Bot sign in and check out without seeing them, and no setting asks for approval each time a saved card is used, so this design saves no card there.

Outside California the columns change: the field list comes from the builder's lawyer for that state, and the tracker is rebuilt from it rather than adapted from memory. Aevrion Ops can help a builder set up the tracker, the gap-check routine and integrations to the systems already in use, as far as each vendor permits and once tested; the reliable workflows article covers routine design across trades. For a builder whose releases currently live in email threads and truck cabs, the workflow automation readiness assessment is a sensible first step.

1. Paying a sub does not close a lien question; a signed release from each potential claimant for each payment is what CSLB tells owners to collect.
2. In California, CSLB says subs and suppliers serve preliminary notices, conditional releases come before payment and unconditional ones after, and the direct contractor collects them.
3. A paid sub's line can close while their supplier's stays open; the tracker keeps both visible.
4. A gap check before each draw lists missing releases and unmet lender checklist items; it drafts requests and never sends, signs or submits.
5. This is not legal advice: lien rules vary by state, and the builder confirms every deadline with a lawyer.