Skip to main content
Payment applicationsSupporting documentsBilling backup

Construction Pay Application Supporting Documents Checklist

Quick answer:

A complete construction pay application package may include the current payment application, updated Schedule of Values, approved change orders, stored-material backup, lien waivers, daily reports, progress photos, delivery tickets, time-and-material records, certified payroll, and project-specific forms.

The contract, GC, owner, architect, or lender decides what is required. Use this checklist to organize the package, then confirm the submission rules for your project.

Clean math is essential, but reviewers also need enough documentation to understand what changed, what was installed, and why the requested amount is supportable.

PayAppPro produces AIA-style outputs and does not distribute licensed AIA forms. Follow the contract and reviewer requirements for every submission.

What is pay application supporting documentation?

A pay application states how much the contractor believes has been earned and requested for the current billing period. Supporting documents—often called pay app backup or billing backup—give the reviewer records needed to evaluate particular amounts or contract requirements.

Supporting documentation does not replace correct G702/G703-style math. The current contract sum, SOV, prior billing, work completed this period, stored materials, retainage, and amount due must still reconcile. Backup explains and supports the underlying request.

Start with the contract. There is no universal attachment package for every project. Review billing exhibits, submission instructions, lender requirements, and the GC or owner’s current checklist before assembling the package.

Construction pay application document checklist

Use the categories below as a review framework, not as a substitute for project-specific requirements.

1. Current pay application

The current summary and continuation detail showing previous work, this-period work, stored materials, retainage, and the amount requested.

2. Updated Schedule of Values

The approved billing breakdown should total to the current contract sum and identify approved change-order lines clearly.

3. Daily construction reports

Dated records of work performed, labor, locations, deliveries, inspections, conditions, delays, and field events.

4. Progress photographs

Dated and captioned images that show installed work, delivered materials, storage conditions, or the condition behind a change.

5. Approved change orders

Executed authorization and pricing that match the change number, amount, and SOV treatment used in the pay application.

6. Stored-material backup

Supplier invoices, delivery records, photos, storage location, insurance evidence when required, and a stored-material rollforward.

7. Time-and-material records

Daily labor, classification, hours, materials, equipment, rates, signatures, and references to the originating instruction or event.

8. Lien waivers

Conditional or unconditional progress waivers in the form, amount, through-date, and party sequence required by the project.

9. Certified payroll and compliance

Certified payroll, prevailing-wage records, participation reports, or other public-project compliance documents when required.

10. Project-specific forms

Cover sheets, sworn statements, insurance certificates, vendor backup, schedules, affidavits, or lender forms named in the contract.

How daily reports support progress billing

A daily report is not a valuation or an approval certificate. It is a contemporaneous field record that can help the office test whether the billing story is consistent with what happened on site.

Useful daily-report details

  • Work performed by activity and location
  • Crew counts and labor hours
  • Deliveries and materials received
  • Inspections, tests, and access events
  • Weather and actual production effects
  • Potential changes and originating instructions
  • Photos with dates and captions

What a daily report does not do

  • Authorize extra work by itself
  • Establish the correct percent complete by itself
  • Replace a signed change order
  • Override contract notice requirements
  • Make a pending change billable
  • Prove that every recorded cost is reimbursable

DailyLogsPro construction daily log software helps field teams capture these records consistently. Its PayAppPro integration can pull PayAppPro projects into the field workflow and send approved DailyLogsPro change orders back as SOV lines.

The systems preserve an important boundary: field records support review, while authorization and contract rules determine what becomes billable.

Match billing lines with the right backup

SOV or billing itemExample requestHelpful supporting documents
Electrical rough-in$18,000 work completed this periodDaily reports by area, crew history, inspection records, and captioned progress photos
Rooftop equipment$42,000 stored materialsSupplier invoice, delivery or storage record, insurance evidence when required, location details, photos, and ledger history
CO-004: Added conduit$6,500 approved change workOriginating field record, scope and pricing, signed approval, change-order number, and evidence of work performed
T&M service relocation$3,275 time-and-material requestDaily labor and material detail, equipment, rates, instruction reference, photos, and required daily signatures

Examples are illustrative. Required documents and billing treatment depend on the contract and reviewer.

Pay special attention to stored materials and change orders

Stored materials

Stored-material billing receives additional scrutiny because the material may not yet be visible in installed work. Keep the supplier amount, amount previously billed, amount still stored, amount transferred into installed work, storage location, and photographs consistent across billing periods. See the stored materials ledger workflow.

Change orders

Make sure the signed amount matches the contract-sum adjustment and SOV line. Pending changes should remain separate unless the contract and reviewer expressly allow another treatment. Review how to bill approved change orders and approved versus pending changes.

Lien waivers

Check waiver type, amount, through-date, claimant identity, and conditional status against the current request. A clean pay app can still be delayed when the waiver package does not match.

Monthly supporting-document workflow

1. Confirm requirements

Review the contract, current submission checklist, billing deadline, and file-format rules.

2. Reconcile progress

Compare proposed SOV progress with field records, approved changes, stored-material activity, and prior billing.

3. Assemble backup

Use clear file names, dates, change numbers, SOV references, and captions so reviewers can trace each item.

4. Review the package

Check tie-outs, approvals, amounts, through-dates, signatures, and required attachments before submission.

Common pay application backup mistakes

  • Uploading many photos without dates, locations, or captions
  • Submitting daily reports that do not identify the work or area
  • Using a change-order amount that differs from the signed approval
  • Billing stored materials without current invoices or storage evidence
  • Including pending changes in approved contract totals
  • Providing lien waivers with the wrong amount or through-date
  • Sending filenames that do not map to an SOV line or billing category
  • Assuming last month’s submission requirements still apply without checking

For the broader process, read the Construction Payment Application Guide and use the pay application rejection checklist before submitting.

Frequently asked questions

Common supporting documents include an updated Schedule of Values, approved change orders, stored-material invoices and photos, daily reports, progress photos, delivery tickets, time-and-material records, lien waivers, certified payroll when required, and any project-specific forms named in the contract.

Not always. The contract and reviewer requirements control what must be submitted. Even when daily reports are not mandatory attachments, they can help the contractor verify work dates, locations, labor, deliveries, delays, and the history behind a questioned billing line.

Include progress photos when the contract requires them or when they help verify installed work, stored materials, deliveries, changed conditions, or another questioned amount. Use dated, relevant photos with captions rather than an unorganized photo dump.

Reviewers commonly request supplier invoices, proof of payment when applicable, delivery or storage records, photographs, identification of the storage location, insurance evidence, and a ledger showing what remains stored versus what has been installed.

Do not assume a pending change is billable. Many contracts and reviewers require executed approval before a change affects the contract sum or SOV. Follow the contract and keep pending changes separate from approved billing totals.

Build a cleaner pay application package

Keep SOV progress, retainage, stored materials, approved changes, and supporting files organized in one PayAppPro workflow.