Indiana lien waiver requirements

Rules that change the workflow

1. No statewide four-form text. Nothing in the current mechanics-lien chapter prescribes conditional/unconditional progress or final payment-waiver wording. That bounded form finding does not erase §§ 32-28-3-1 and -15 through -18, recorded-lien-release law, public-bond statutes, agency forms, or ordinary release doctrine.

2. Covered prepayment requirements are void. Section 32-28-3-16 applies to contracts to construct, alter, or repair a building or structure other than defined Class 2 structures, auxiliary improvements, and specified regulated-utility property. Within that scope, a contract cannot require a provider to waive a real-estate lien or payment-bond claim before the provider is paid. It also cannot require an agreement not to file a lien notice. Section 32-28-3-17 prevents contractual evasion through another state's law or an out-of-state forum.

3. The statute regulates a requirement, not every imaginable standalone act. Section 32-28-3-16 does not say that every voluntarily delivered document is automatically conditional, define when a check or electronic transfer counts as paid, or prescribe the effect of dishonor. Before funds settle, use an expressly conditional document tied to the identified payment and withhold any unconditional confirmation. Do not tell users that every Indiana waiver is automatically ineffective until clearance; the located official authority does not establish that categorical rule.

4. Residential/utility no-lien contracts are a separate branch. Section 32-28-3-1 permits an owner and principal contractor to prevent lien attachment for defined Class 2 structures and auxiliary work, specified regulated-utility property, and Class 2 residential site preparation. Binding lower tiers requires a writing, legal description, deed-style acknowledgment, and recording no later than five days after execution. Earlier labor and materials remain outside the provision. A project address, a checkbox, or a draw waiver is not a substitute for the recorded contract.

5. Payment and consideration must match the released scope. For a covered required waiver, payment is the statutory timing gate. More generally, Bird treats a release as a contract governed by intent and proper consideration, while Turner enforces the actual object of the waiver. Record the exact amount, payment reference, through date, covered work, retainage, disputed extras, unpaid prior draws, and exclusions; preserve settlement evidence rather than relying on a recital that payment was received.

6. A lien release does not necessarily erase the debt. Turner held that the waiver before it relinquished security in the house but not the contractor's claim against the owner. A form that intends to affect a payment bond, contract balance, retainage, change order, or other claim must identify that right deliberately. Conversely, avoid broad all-claims wording when the business event is only a draw-specific lien release.

7. Pay-if-paid language cannot block covered lien enforcement. Under § 32-28-3-18, for contracts within that section's scope, upstream receipt from an unrelated third person cannot be a condition, limit, or defense to the provider's right to record or foreclose its lien. This rule shares the Class 2 and utility exclusions. It does not itself define payment under a waiver or decide the underlying contract-balance claim.

8. Payment-status accuracy has statutory consequences. Section 32-28-3-15 applies only when all stated elements are met: the payee accepts payment, knows of construction-related indebtedness, intentionally omits written notice with intent to defraud, and causes the payer loss. A final waiver should not auto-certify that every lower tier is paid without claimant verification. Rynard independently shows why the GC must never create, reuse, or notarize a lower tier's signature.

9. Routine payment waivers have no statutory notary block. The payment-waiver provisions checked prescribe no universal witness, acknowledgment, notarization, recording, or delivery form. Obtain explicit assent from an authorized claimant representative anyway. Indiana UETA supports electronic records and signatures only where the parties agreed to transact electronically; attribution, recipient-retainability, and final-record retention still matter. A required notarization can be electronic if § 26-2-8-110 and other applicable law are satisfied.

10. Three formal instruments must not be conflated. A routine draw waiver is contractual evidence. A § 32-28-3-1 no-lien contract prevents attachment in limited categories and has acknowledgment/recording formalities. A release of an already recorded mechanic's lien follows §§ 32-28-1-1 and 32-28-6-1: full payment, lawful tender, and discharge trigger record satisfaction; a partial release must say it is partial and describe what is released; after a qualifying owner demand, the lienholder has fifteen days to release or faces statutory damages.

11. Public work is a bond-and-contract-document workflow. State and local statutes protect payment through withheld funds, payment bonds, signed or verified claim statements, and short claim/suit clocks. IDOA's DAPW 156 is a notarized final-only subcontractor/supplier form tied to receipt of the final balance and is required by IDOA contract administration—not by the private lien chapter. State highway work is expressly routed elsewhere, and federal, tribal, mixed-funding, and project-specific requirements need separate classification.

Practical qualified GC workflow

1. Classify before generating. Record private or public owner; structure/use; whether the work is Class 2, auxiliary, site preparation, regulated-utility property, state public, local public, state highway, federal, tribal, or mixed. Escalate mixed-use or uncertain classifications.
2. Check recorded-contract status. On a potentially exempt Class 2/utility job, obtain the owner–principal-contractor agreement and recorder-stamped copy. Verify legal description, acknowledgment, execution date, recording date, parties, and whether the claimant furnished anything before recording. Do not infer a no-lien contract from the project type alone.
3. Map the claimant and rights. Verify legal entity, contracting tier, signer authority, property/project, private lien eligibility, payment-bond identity, notice status, and any recorded lien. Keep lien, bond, contract, retainage, and change-order rights separate.
4. Use payment-matched conditionality. Before settled funds, issue only counsel-approved conditional language tied to the exact draw, payment instrument, amount, and through date. Preserve retainage, later work, disputed extras, unpaid prior draws, and claimant-entered exceptions. Deliver an unconditional confirmation only after settlement evidence is available and the claimant confirms the scope.
5. Control execution and truthfulness. Obtain e-transaction agreement, claimant assent, authority evidence, attribution, timestamp, final-document hash, delivery, and a retainable copy. Never sign or notarize for a lower tier. Require the claimant—not the GC—to confirm any downstream-payment representation.
6. Route public work separately. Capture the public body, governing statute, bond, surety, final-acceptance date, contract forms, and claim deadlines. Use DAPW 156 only for an applicable IDOA final-closeout workflow; do not substitute it for a private waiver or assume it governs a local or highway project.
7. Close the record, not just the draw. Store the executed form with payment-clearance evidence and exceptions. If a lien was already recorded, obtain and record the proper full or partial satisfaction and calendar the fifteen-day post-demand rule. A payment waiver does not extend any lien, bond-notice, or suit deadline.