A pay application can be ready on paper and still be missing the information needed to submit it. An approval may be sitting in a project manager’s inbox, or a required attachment may not have reached the office.
A project-specific checklist gives the team a shared view of what is ready, what is missing, and who needs to act.
Start with the project’s instructions
Keep the billing deadline, submission method, required forms, and reviewer’s contact information together. Use the project’s contract and current billing instructions to build the checklist; requirements can differ from one customer to the next.
Work backward from the submission date to set an internal review date. Allow time to resolve questions before the final package is due.
Get a clear progress update
Ask the project lead to review the billing lines and provide the current progress information, with supporting notes or photos where needed. Keep the review tied to the correct billing period.
Flag anything that needs clarification instead of leaving the office to guess what happened on site.
Keep approvals and backup within reach
Maintain a current change-order log with links to the corresponding approval documents. Keep pending items clearly distinguished from approved ones so the reviewer can see their status.
Gather the supporting documents required for this project, which may include stored-material documentation, vendor backup, or waiver forms. Route documents that need signatures to the appropriate people early.
Obtain the right vendor and subcontractor waivers
Build a waiver checklist for each billing cycle. Identify which subcontractors and suppliers must provide releases under the project requirements, request them before the deadline, and track what is missing. A waiver from your own company does not replace releases required from those parties.
Check the legal business name, project, payment amount, period or through-date, signature authority, and any listed exceptions. Match each document to the relevant invoices and payment records. Review the form’s actual release language, not just its title.
Conditional versus unconditional: payment status matters
A conditional waiver generally makes the release effective only when the specified payment is actually received, subject to the form and applicable law. It is typically used when requesting or arranging a payment that has not yet been received.
An unconditional waiver states that payment has been received and can release rights without a payment condition. Do not treat a scheduled transfer or a check in the mail as confirmed payment. Verify receipt and clearance before signing or requesting an unconditional release.
Progress and final waivers are another distinction: progress waivers cover an interim payment; final waivers address final payment and can have broader consequences. Check how the form treats unpaid retainage, disputed amounts, and other exceptions.
Forms and enforceability vary by state. Use the forms required for the project’s jurisdiction and have unfamiliar or expanded release language reviewed by construction counsel.
Keep waivers tied to the billing cycle
For example, a project may require conditional progress waivers for the current payment request and unconditional progress waivers for the previous cycle after those payments have cleared. Confirm the actual requirements rather than assuming every customer uses that sequence.
Keep a log showing the vendor, invoice or payment reference, waiver type, amount, through-date, date requested, date received, and payment verification. Review discrepancies before including the waiver in the billing package, and follow up after payment for any required unconditional releases.
Track what happens after submission
Save the submitted package and record when and how it was delivered. Track reviewer questions, requested corrections, and the current status in one place.
Assign someone to follow up on unresolved items. The checklist should stay useful after the upload is complete, all the way through the customer’s review.