Lien waivers, checked against the payments they cover.

A specialty contractor sits in the middle of the waiver chain. Each pay cycle you give your GC a waiver for what you billed or were paid, and you collect waivers from the suppliers and sub-tier subs you paid on that job. A project accountant keeps both sides straight beside the pay app and the check run.

In the proof of concept, AI reads the same waivers and checks each one against the payment it covers: signer, job, type, amount, through date and exceptions. It also lists the waivers each cycle should have had and didn't. Nothing is signed or sent.

The type has to fit the moment. A waiver is conditional or unconditional, and covers a progress payment or the final one. A conditional waiver takes effect when the payment it names is received; an unconditional waiver gives up the rights when signed, paid or not. So the check is not only whether a waiver exists, but whether each unconditional waiver lines up with a payment that has cleared, and whether a final waiver arrived while retainage is still owed.

The project's state decides the form. Some states, California and Texas among them, set the wording of each waiver type by law. Others leave it to the parties, and many GCs send their own. A shop working in several states keeps several versions of the same four waivers. On public jobs there are generally no lien rights against the property, so a payment bond stands in and the release may be a bond claim waiver. The proof of concept gives no legal advice; it checks each waiver against the version your team or counsel already uses for that state.

Amounts, dates and exceptions have to agree with the money. The amount on a progress waiver should match the check or joint check it covers, and the through date should match the pay period, not run past it. Exceptions written on it, such as retainage, pending change orders or disputed extras, have to be carried into the log. Names matter too, since a supplier selling to you on several jobs can sign for the wrong one.

The GC's portal adds its own rules. On Oracle Textura, a sub submits an unconditional waiver to get paid; the system strips the signature and holds it until the GC disburses. Where a GC tracks sub-tiers there, missing sub-tier waivers make your company ineligible for payment on that draw. Other GCs use GCPay or email, each with its own forms.

Your reviewer's short list: unconditional waivers with no cleared payment behind them, a final waiver with retainage still open, amounts or through dates that don't match, a form that doesn't fit the project's state, and waivers a cycle should have had.

With your reviewer's yes, the same checks run on new waivers for about 30 days, roughly one pay cycle on each open job.

The system signs, sends and releases nothing. A person approves each waiver check and decides what to chase, and your team still signs every waiver going to a GC.

The live job gets its fixed price before you sign. What follows is quoted on its own, with monthly support once it runs.