Trade payment for lien rights, and get the retainage back

Mark on each subcontract agreement whether a signed waiver is required before payment is released. The requirement then travels with the firm rather than living in one person's memory of what was agreed.

Why: Chasing waivers after the money has gone out is chasing a signature from someone who no longer needs anything from you. Set as a condition of payment, the same request answers itself, because the party who wants the check is the party who has to sign.

Upload each signed waiver against the firm that gave it and the period it covers, so the file sits with the payment it belongs to rather than in an inbox. What is still missing is a list, not a recollection.

Why: Exposure on a job runs to everyone who supplied labor or material, not only the firms you hold a contract with. A waiver you cannot produce on request is, for practical purposes, a waiver you do not have, and the moment you need it is the moment somebody further down the chain says they were never paid.

Record the waiver against the payment application it releases, choosing across the two axes that matter: conditional or unconditional, partial or final. Waivers accumulate as a history rather than overwriting each other, so every period keeps its own release.

Why: The two axes are the whole point. Conditional means the release takes effect when the money actually lands; unconditional means it already has, and signing one before the funds clear gives away the leverage for a payment that can still fail. Partial covers the period, final closes out the job. Getting the pair right is the difference between a release and a gift.

Set the event that releases retainage on the contract itself, then release against it when the event occurs. The percentage held and the event that frees it are contract terms, so they are recorded once with the contract rather than renegotiated at the end from memory.

Why: Retainage is the contractor's own money, withheld for a while and then quietly forgotten by everyone who is not owed it. Tied to a named event it becomes due on a date somebody can point at; left informal it becomes the last unresolved line on a job nobody wants to reopen, and it is routinely the largest sum still outstanding when a project closes.

Reconcile the payments against the waivers held for them, so the answer to what has been paid and what has actually been released is one view rather than two lists somebody compares by hand.

Why: A payment without its matching release is not a closed transaction, it is an open exposure that looks closed in the ledger. The gap between the two lists is the thing a lender, a surety or a title company will ask you to produce, usually at the point where the job is otherwise finished.