A pay application missing backup, a waiver, or a clear date is much easier to delay than a complete, repeatable packet you can find later.

This article is about a filing habit, not legal advice. Arizona has rules about preliminary notices, prompt payment, and lien waivers. Your contract may set different steps. Read both the contract and the statutes, and talk to a construction attorney when the dollars matter. What follows is only a way to keep the documents and the dates in one place. If your job is outside Arizona, note that the rules described here are Arizona’s. Other states handle notices, prompt pay, and lien waivers differently, so check your own state’s rules and your contract.

A monthly packet you can repeat

Each month, build one dated package in the job file and use the same contents every time, adjusted to what the contract actually requires:

  • The pay application or billing
  • Schedule of values or backup for the work billed
  • Lien waivers, in the form your contract calls for, from you and from the subs and suppliers you are required to collect
  • Copies of any preliminary notices you sent or received that belong with this job's payment file
  • A short cover list of what is in the packet and the date it was submitted, and to whom

Name the folder or the PDF with the date and the period, so January and February cannot be confused: 2026-07-31_245_PAY_App06_July.pdf. Keep the whole package together. A waiver in one person's email and a pay app in another's is how a complete billing still ends up looking incomplete.

A simple log helps: period, date submitted, date certified or rejected, date paid, and a link to the packet.

Dates and notices worth tracking, not interpreting

Two Arizona clocks show up often enough that they belong in the filing habit. This is a general description only, not a complete statement of the law.

For a lot of private work, the Prompt Payment Act, see A.R.S. § 32-1182 and A.R.S. § 32-1183, generally gives an owner 14 days to certify or reject a payment request in writing, then 7 days to pay after approval, and generally gives a contractor 7 days after receiving payment to pay subcontractors and suppliers. Contracts can, in some cases, set different timing if they do so in the way the statute requires. Those clocks only help if the dates are in a file somebody can find.

Arizona also has a preliminary twenty-day notice that is, for many claimants, a prerequisite to a valid mechanic's lien. See A.R.S. § 33-992.01. In general terms, that notice is served not later than twenty days after the claimant first furnishes labor, professional services, materials, or equipment to the jobsite, with exceptions the statute spells out. I am not telling you whether you must send one or how to serve it. Keep a copy of any notice you send or receive, with the date of service, in the job file.

If a payment is certified, rejected, or paid late, file the written statement and the date you received it with the same monthly packet.

The miss this prevents

Here is how this usually plays out.

A pay application goes out missing a waiver, or with backup in a different email. The reviewer asks for the missing piece. Someone thought it was already sent. A week slides by. Subcontractors are waiting. The work was fine. The packet was not.

The cost is a payment sitting behind a document you already had.

How to run it in the job file

Give pay applications, waivers, and related notices their own folder in the Google Drive or Dropbox job file, and treat each month as a complete packet. The person who assembles the billing should know exactly where last month's package lives.

A person should still check that the waivers, the backup, and the dates match what was actually sent.

If last month's packet is already a mess

Start the repeatable package on the next billing cycle. If something is still outstanding from last month, put those missing pieces in a dated follow-up.

If you want help, I can set up the job file and a monthly payment folder, run document control on a retainer, or prepare closeout. Bring last month's pay application and whatever backup went with it.

The files stay yours. This is a filing habit, not legal advice.

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