A month of completed work can still sit unpaid when the waiver packet, the backup, or the dates are incomplete, or when nobody can find them. The work is in place, but owners, lenders, and sometimes upper-tier contractors will not move money until the packet looks complete. One missing lien waiver, or backup that lives in someone's inbox, is enough to hold the month.

The story below is a typical case, not a specific job, and the dollar figures are examples.

This is not legal advice. Lien rights, waiver forms, and payment clocks depend on your contract and on Arizona law. Read both, and talk to a construction attorney when the dollars matter. What follows is a filing habit: keep the packet together, with dates, in a place you can find. If your job is outside Arizona, note that the rules described here are Arizona’s. Other states handle lien waivers and payment clocks differently, so check your own state’s rules and your contract.

How it usually goes

The month's work is done. The schedule of values is ready, or close to it. Invoices from a few subs are in, others are late, and lien waivers are trickling in by email, as scans, or not at all. Someone assembles the pay application under time pressure and either sends what they have or holds it, waiting on one more document.

Then the owner or the lender comes back: the packet is incomplete. A waiver is missing for a sub who was on site. Backup does not match a line. A date is wrong, or a form is the wrong one for this job. The month sits.

Meanwhile, a sub wants to know when they will be paid. The missing document is in an inbox, on a phone, or still with a sub who has moved on to the next task. A week or two goes by. The work was real. The file just was not ready.

What that costs (example figures)

The cost is cash flow, and the pressure that puts on you and your subs. A pay application in the range of $100,000 to $250,000 sitting two to four weeks longer than it should is a serious cash-flow event for a contractor running several jobs at once, even if every dollar is eventually paid. That range is an example of a month's billings, not an average.

The rest of the cost is quieter. A sub who did the work and is still waiting gets tense. Someone in the office, or your superintendent, spends hours reconstructing a packet that should have been a dated folder. Payment timing under your contract, and on a lot of private work in Arizona under the Prompt Payment Act, runs on dates. If the packet is incomplete, those clocks may not start the way you think they do. See, generally, A.R.S. § 32-1182 and A.R.S. § 32-1183. This is not legal advice; your contract may set different steps.

The basic controls that would have caught it

Treat the pay application as a dated packet, not a pile of emails. In the job file, keep a folder for pay apps and lien waivers. Each month gets its own dated set: the application, the schedule of values, invoices, backup, and the waivers that belong with that month. If a document is not in the packet folder, it is not in the packet.

Track waivers the way you track submittals. A simple list (subcontractor, form needed, date requested, date received, filed in this month's packet) makes the missing one obvious before you submit. Ask for waivers on a cadence, not in a panic.

Keep notices and related payment documents in the same job file. Arizona has a preliminary notice practice on a lot of jobs (see A.R.S. § 33-992.01). Track those documents and their dates as files, not as inbox items. I am not telling you how to perfect a lien or which form to use. I am telling you not to lose the paper.

"Arizona Schedule Pressure: Heat, Monsoon, and Notice Deadlines" covers why those dates matter in this state.

If the monthly packet is already a scramble

If the monthly packet is already a scramble, that is a reason to get help with the file, not a reason to feel behind.

I can set up the job file, run document control on a retainer, or prepare closeout. The work can be complete and the month can still sit. The packet has to be as easy to find as the work was to inspect.

If you want help, not just a checklist

Some jobs run fine on a clean file and a superintendent who gives the log fifteen minutes twice a week. Others do not: revisions are moving fast, closeout is already behind, or the field simply has no hours left for paperwork.

That is where I come in. I set up the job file, run the logs on a retainer, or prepare closeout before the scramble starts. Your files stay yours, and there is no software contract to sign.

Email travis@builtonrecord.com Get the free Job File Kit