Start with a team recordkeeping routine
Make each payment cycle easy to find and review.
Waiver paperwork is easier to follow when the request, received file, review, and follow-up share one project and payment-cycle reference. Treat the steps below as an internal organization method. Confirm which parties and documents apply to each project through the contract, project process, and qualified legal guidance.
01 · Organize the file path
Group records by project, then subcontractor or payee, then cycle.
Give every project a stable name or code. Under it, keep a separate record for each subcontractor or payee whose paperwork your project process tracks. Add one entry for each draw, invoice, or payment cycle, using the cycle reference and date range your team already uses. This structure helps a reviewer find the right document without mistaking one payee, project, or period for another.
If your process identifies lower-tier subcontractors or suppliers that need their own paperwork, list them separately and connect them to the relevant project and cycle. Do not assume one file for a subcontractor covers every party, payment, or period. Track only the parties and forms required by the applicable contract and project process.
Project code / Subcontractor or payee / Payment cycle / Received version
02 · Keep a complete cycle record
Record what arrived, what it covers, and what your team decided next.
Keep the original received file and a dated entry for each review. Capture these fields so another team member can see which cycle the document belongs to and what remains open.
| Record field | What to keep |
|---|---|
| Project and subcontractor or payee | Use the project identifier and the exact subcontractor or payee name shown in the project records. Track each party separately when the project process calls for separate documents. |
| Payment cycle | Record the draw, invoice, or payment reference and the cycle date range so a document can be matched to one review period. |
| Covered amount or period | Capture the amount and/or through-date or period stated on the received document. Preserve exceptions, exclusions, retainage, or other carve-outs as written. |
| Received version | Keep the actual file, document type or label, version, and received date. Preserve superseded copies so the team can see what changed. |
| Reviewer and review outcome | Record who reviewed it, when, what project or contract reference they checked, and a factual workflow result such as “clarification requested” or “replacement received; review pending.” |
| Follow-up owner and due date | Name the person responsible for the next action, what they need to do, and the date the team plans to revisit it. Record the close-out date when resolved. |
Keep the record factual. “Received; review pending,” “clarification requested,” and “replacement received; review pending” describe the team's process. They do not establish that a waiver is legally effective or that a payment has cleared.
03 · Review and close the loop
Make the next action visible, not just the missing document.
Before a payment cycle is closed in your internal tracker, compare the received version with the project's approved request and record what the reviewer did. If a detail is unclear or an exception is listed, write down the question and route it to the person authorized by your company process to resolve it.
- Record the reviewer, review date, and the project or contract reference used.
- Describe exceptions or gaps as written; avoid silently editing the document.
- Assign one follow-up owner, a specific next action, and a due date.
- When a replacement arrives, retain the earlier version and link the new one.
- After the team resolves the open item, record the outcome and close-out date.
A file upload alone is not proof of payment, acceptance, or legal sufficiency. Keep payment confirmation and any contract or legal decision in their proper records.
Keep legal requirements project-specific
Use this as a tracking routine, not a nationwide waiver rule.
The organization recommendations above are general recordkeeping practices. They do not select a waiver form, set a request deadline, determine who must send a notice, or decide what a waiver releases. State law, contract language, project type, and the parties' roles can affect those questions. Texas law, for example, addresses waiver and release requirements and forms in Property Code Chapter 53, Subchapter L; Florida's construction lien statute includes notice-to-owner provisions and timing rules for certain circumstances. These are examples, not a state-by-state checklist.
Before using or accepting a form, confirm the current state and contract requirements for that project with your construction counsel or other qualified advisor. A Sub Vault record, checklist, or status label does not provide legal advice or determine that a waiver, notice, payment, or project is compliant.
Sub Vault subcontractor compliance records
Keep waiver records alongside the subcontractor file.
Sub Vault's subcontractor compliance workspace can keep lien waivers and other compliance documents with each subcontractor, including document dates and review status. Your team supplies and reviews the records; the workspace does not interpret state law or decide whether a waiver meets a contract requirement.
Official state references
Examples of state-specific rules
These official statutes illustrate why a general tracking workflow cannot replace project-specific legal review. They are reference starting points, not a complete survey or legal interpretation.
- Texas Property Code, Chapter 53, Subchapter L
Sections 53.281–53.284 address lien or payment-bond waiver and release requirements and prescribed forms.
- Florida Statutes § 713.06
The statute includes notice-to-owner provisions and timing rules for certain participants and circumstances.
General information only. Requirements can change and may depend on the jurisdiction, contract, project, and parties involved. Consult qualified counsel for advice on a specific project.