What the conditional actually conditions on
A conditional waiver usually states that the release becomes effective when the identified payment is received. “Received” can depend on the form’s words and applicable law; a check being printed, mailed, deposited, or finally collected are not interchangeable events.
The document should identify the payment and scope clearly enough for the parties to match it later:
- Claimant or subcontractor.
- Customer or hiring party.
- Project and property.
- Payment amount.
- Through-date or payment period.
- Progress or final scope.
- Retainage, disputed work, extras, or other reservations when the form permits them.
An unconditional waiver states the release without that payment condition. That makes timing important. A batch process that is appropriate for conditional requests can be dangerous for unconditional forms if it asks thirty vendors to attest to payment before the underlying facts are true.
Build the draw from one source list
Start with one project, one payment period, and the vendors included in that draw. For every row, keep the source amount and its reference: subcontract, purchase order, pay application, direct-cost bill, or a manual draw entered by the customer.
Do not force every payment into a contract record. A direct cost can be real even when no PO exists. The record should say what source was used rather than inventing a contract number to satisfy the software.
Before generating documents, resolve:
- Vendor and signer contact.
- Project and state.
- Amount and through-date.
- Conditional progress or conditional final.
- Retainage and known reservations.
- Whether a customer-approved state or company template is available for that workflow.
The goal is not “send all” as quickly as possible. It is to review a stable list once, preview every document, then send the approved batch without retyping each row.
Match the amount and through-date before sending
The amount answers “what payment is this tied to?” The through-date answers “what work period does this request cover?” If either field comes from a stale pay application, the sub may be asked to sign a document that does not match its own records.
Use the draw’s source document as the authority for the draft. If the customer changes an amount after generation, regenerate or invalidate the draft rather than editing a detached PDF. Keep the original source reference so a later reviewer can see why the amount appeared.
Final does not merely mean “last payment this month.” A final waiver is scoped to the job or contracted work through completion. Confirm that the project, subcontract, disputed items, retainage, and unfinished extras match the company’s final-closeout decision.
Handle joint checks and owner-funded checks explicitly
A joint check can include more than one payee and can change how the parties document receipt. The waiver should identify the payment actually being discussed and any reservation the form allows. Do not assume that one signature proves every participant received cleared funds.
Owner-funded checks create a similar matching problem. The GC may organize the waiver request, but the maker and payee can differ from the normal subcontract payment path. Where the enacted conditional form prints those facts, use the actual maker and payee names. SubLien does not ask for a check number, payment rail, receipt, evidence reference, or proof upload.
Keep payment evidence in the accounting record
A signed conditional waiver does not prove payment. The GC keeps payment evidence in its ordinary accounting and banking records; SubLien does not duplicate that ledger with a separate post-sign “Record payment” step. When the transaction calls for a later unconditional waiver, the customer starts that waiver from the actual project and payment facts.
State-specific form differences can change the sequence
Some states prescribe waiver forms or payment conditions. Others regulate timing without providing a routine fill-in form. A few workflows require notarization or an uploaded completion document rather than ordinary e-signature.
Examples in the current primary sources include:
- Texas provides current conditional and unconditional progress and final forms. SubLien does not offer historical pre-2026 form routes.
- Florida publishes waiver forms and includes payment-linked language in its statute.
- Utah prescribes progress and final forms with payment conditions; the supported variant set does not mirror the ordinary four-label model.
- Georgia’s statutory workflow includes a nonpayment period and does not map cleanly to the standard conditional/unconditional pair.
- New York and Rhode Island timing rules make an ordinary prepayment request unsafe as a default workflow.
Do not solve these differences by renaming a generic PDF. The customer should review the exact form, source, project state, waiver type, and template version before it becomes available to send.
A 30-sub draw checklist
Before the batch
- Confirm one project and one payment period.
- Reconcile the source amounts.
- Resolve missing vendor and signer contacts.
- Confirm the customer-approved form for every project-state workflow.
- Review retainage, final-payment, and joint-check exceptions.
Before send
- Preview every generated document.
- Verify vendor, project, amount, through-date, and waiver type.
- Remove any row that needs a different workflow.
- Send only conditional forms through the ordinary batch.
After send
- Track delivered, opened, signed, disputed, and bounced requests.
- Stop reminders when the requested document arrives or the ladder ends.
- Keep payment facts and evidence in the customer’s accounting records.
- Start a later unconditional waiver only when the actual transaction calls for it.
- Keep the source, signed PDF, consent, and audit events together.
What to do when a sub pushes back
A dispute should freeze the reminder chase and preserve what the sub reported. Common issues include the wrong amount, wrong project, work outside the through-date, retainage, disputed change orders, or a claim that payment already occurred.
Fix the source record first. Do not ask the vendor to sign an incorrect document and promise to clean it up later. If the facts change, regenerate a new draft and retain the event history showing why the first request stopped.
Primary state sources for timing differences
- Texas Property Code §§ 53.281–53.284, including prescribed forms and payment conditions.
- Florida Statutes § 713.20, including waiver forms and payment-linked language.
- Utah Code § 38-1a-802, including prescribed progress and final forms.
- Georgia SB 315, which revised the interim and final waiver workflow.
- New York Lien Law § 34 and Rhode Island § 34-28-1, addressing payment-timing restrictions.
- Delaware Code § 2706, for Delaware’s payment-linked waiver rule.
Where SubLien fits
SubLien keeps each lien waiver on its vendor and project record. Your team prepares and reviews each draft, sends it for signature, and can return to the waiver list to see signatures, opens, and reminders.
When a customer records payment against a signed conditional, SubLien can surface a draft for the matching unconditional workflow. Nothing sends automatically. Where the configured state workflow does not support that variant, the row is refused instead of relabeled.
SubLien records the document and customer-supplied facts. It does not determine that a waiver is enforceable, that payment cleared, or that a check may be released. Review the lien waiver software, or bring one real draw to a demo.