Progress payment applications: 3 timing rules to check

• The billing period and cut-off date are written in the contract or confirmed in writing.
• The date backup must be complete is on the job calendar, ahead of the cut-off.
• The review period and payment due date are noted for each application.
• Open change requests are listed and sent in writing before final payment.

A progress payment application is your request to be paid for work completed so far. On a job that runs for months, you may send a dozen or more of them, and each one starts its own clock. Those clocks control your cash flow, your leverage when a payment is late, and how quickly you can resolve a disagreement while the records are still fresh. Most owners and office leads focus on the dollar amount on the page. This post covers three timing rules that are easy to overlook.

The rules come from different places. Some live in your contract. Some come from a state statute or a federal clause. Where a source applies, this post links to it. None of this is legal advice, and none of it replaces the contract you signed. Read the documents that govern your job before you rely on any rule here.

The three rules work as a sequence. The first decides when an application is ready to send. The second decides what happens after it arrives. The third decides what is still open when the job is finished. A problem in one stage usually shows up in the next, so it helps to check all three before the first application goes out, not only when a payment is late.

Timing is also a cash question. A payment that arrives a full cycle late can strain payroll, supplier accounts, and subcontractor relationships, even when the owner has no intention of paying slowly. Owners feel the same pressure from their lenders and their own budgets. Understanding the clock on both sides makes it easier to plan, and easier to explain a delay without making it personal.

Start with the calendar. Your contract should say what period each application covers and when the owner must have the application in hand for it to be processed in that cycle. If the contract is vague, get the answer in writing before the first application goes out. Asking after the fact usually means you have already lost a cycle.

Pay attention to where the cut-off falls, not just the month. A cut-off can land before the last working day of the month, which means work finished in the final days may roll into the next application. Measurement also has to happen earlier than many people expect, because the backup for each line item must be ready before the packet is due. Quantities measured at the end of the period leave no room for a missed signature or a late photo.

Illustrative example: a cut-off before the period ends

In an illustrative 30-day billing period, the cut-off is day 25. The crew finishes a large part of the framing in the last week of the period. The superintendent assumes it will go on the current application, but the cut-off was set before the last working day. The framing moves to the next application, the payment arrives a full billing period later than planned, and the payroll has already gone out. Nothing in that story required a bad actor. It required a calendar nobody checked.

Keep measurements and backup on schedule

Cut-off timing also interacts with how you record quantities. If the field crew submits daily reports, decide which report counts as the measurement for the period, and whether a quantity recorded on the last day but verified on the next one counts for the current application. Those are small questions, but a reviewer will ask them the moment the numbers look off, and the answer should already be in the file.

Make sure each line on the application traces back to the schedule of values in your contract. When a number moves, the timing question is whether the change shows up in the current period or only in the next one. A reviewer who sees a surprise jump in one line is more likely to hold the whole packet than one who sees a clear, documented change.

A practical fix is a simple internal schedule that works backward from the cut-off. List the measurement date, the date backup is complete, the project manager's review date, and the submittal date. Put the schedule in the job file, not in one person's inbox. Staff changes are an easy way for a calendar to get lost in the middle of a job, and a new office lead who inherits a job should be able to find the schedule on day one. For related field records, see the work order checklist for dispatch handoffs.

Partial periods need a rule too. If work starts mid-month, or if the job closes out with a short final period, decide how the first and last applications will be measured and whether they follow the same cut-off. Write that decision into the schedule so no one has to guess later. Ask the owner's representative to confirm it in writing, too. A short email that states the first period's dates is cheap insurance.

This rule matters most when the owner goes quiet. Massachusetts has a statute that sets a framework for progress payments on certain construction contracts, and its timing logic is a useful model even if your job is elsewhere. Start with scope. The statute covers a contract for construction, meaning one for which a lien may be established under sections 2 or 4 of chapter 254 on a project where the contract with the project owner has an original contract price of $3,000,000 or more. It excludes projects containing or designed to contain one to four dwelling units. If your job falls outside that scope, the statute does not govern it, and you should look to your own contract and any other law that applies. (Massachusetts General Laws, Part I, Title XXI, Chapter 149, Section 29E)

Within that scope, the statute says every contract for construction shall provide reasonable time periods for three steps. The contractor submits written applications for periodic progress payments. The person receiving the application approves or rejects it, in whole or in part. The person approving the application pays the amount approved. Read the contract's review and payment periods closely and write them on your calendar. (Massachusetts General Laws, Chapter 149, Section 29E)

Silence has a consequence. An application that is neither approved nor rejected within the time period is deemed approved, unless it is rejected before the date payment is due. In practice, that means an owner who wants to contest an application has to act before payment is due, not after. If you are on the owner's side, the due date is the deadline to watch. If you are the contractor, that silence can work in your favor, but confirm the statute's text and your contract before you count on it. (Massachusetts General Laws, Chapter 149, Section 29E)

Rejections have a form requirement. Under the same statute, a rejection of an application, whether in whole or in part, must be made in writing. It must include an explanation of the factual and contractual basis for the rejection, and it must be certified as made in good faith. A verbal response without the required written explanation and certification does not meet that standard. When you receive a rejection, log the date it arrived, check whether it has all three elements, and respond in writing if it does not. (Massachusetts General Laws, Chapter 149, Section 29E)

The statute also voids any contract term that requires a party to delay commencement of the procedure until a date later than 60 days after a rejection. Read your contract for any clause that sets a long wait after a rejection, and flag it to counsel if you see one. (Massachusetts General Laws, Chapter 149, Section 29E)

How to read a review clause: look for four things. What period the owner has to respond. What counts as a response. Whether a partial approval also settles the rest of the application. And when payment is due after approval. Many disputes come from one of those four being unclear. If the clause uses a word like "reasonable" without anything more specific, write down what both sides understand that word to mean before the job starts.

When the owner goes quiet, send a short written follow-up before the due date. State the application number, the date it was submitted, the amount, and the date the response is due under the contract. Keep the tone factual. The point of the follow-up is to create a record and give the owner one more chance to act. It is not the moment to argue about the work itself. For related correspondence, see the late fee payment reminder guide.

Each application also deserves its own response file. It should hold the application as submitted, the date it was received, every approval or rejection with its date, and any correspondence about amounts. When a dispute reaches a lawyer or an auditor, that file is what gets read first. Keep it current as you go instead of rebuilding it from email months later.

The same rules look different depending on which side you sit on. An owner's office wants a review window it can meet, a rejection that will hold up if challenged, and a payment date it controls. A contractor's office wants a short, predictable review, a clear written record of any rejection, and a payment date it can plan around. Both sides benefit from agreeing on the review window before the job starts.

Keep in mind that the review window depends on your own office too. If an application reaches the owner late, the owner's response period may not start when you expected. Confirm the date an application is treated as received, and make sure your records show when it actually left your office.

Changes tend to surface late. A design revision in month six, a delay caused by someone else, or an extra inspection may not be priced until the job is nearly finished. Many offices treat those items as separate from the progress billing, and that is where money gets lost.

The federal Changes clause shows why timing matters. Under FAR 52.243-4, a contractor's proposal for an equitable adjustment is not allowed if it is asserted after final payment under the contract. Check whether this clause is part of your contract. Compare any release signed at closeout with your unresolved change requests.

Raising a change early does not mean starting a fight. A short written note that describes the change, its cost impact, and its schedule impact gives the owner a chance to decide while the work is still happening. It also gives your office a record. Waiting until the closeout meeting turns a simple decision into an argument about what was said and when.

A useful change request says what was asked, who asked for it, what it changes in the work, what it costs, and how long it adds. Leave out opinions about fault. Those can come later in a separate discussion. The request itself should read like a record that someone could pick up cold six months from now and understand.

Changes are not the only items that arrive late. Stored materials, owner-supplied items, and work delivered but not yet installed can each raise the same question: which application should carry them? Decide the answer in the schedule of values and apply it the same way each month. Inconsistent treatment is one of the easiest ways to make a reviewer doubt the whole packet.

Many contracts hold back part of each payment until closeout. That holdback is a timing item in its own right. Check two things: when it is released, and whether its release is tied to the final payment, a punch list, or documents such as lien waivers. If the release date is not written down, it tends to drift, and the amount sits in the owner's account while the contractor's cash runs short.

Before the final application, pull together the open change list, the last approved application, the lien waivers you have collected, and any owner correspondence about unresolved items. Do not assume the owner's file matches yours. Compare the two, and close each gap in writing.

Before anyone signs a final release, compare the release against the list of open items and resolve or document each one.

Put every cut-off, review date, and payment due date into one calendar at the start of the job. Include the entire contract period, not only the next application. Assign an owner to each date: the person who prepares backup, the person who reviews it, and the person who sends it. Hold a short check-in a few working days before each cut-off, where the team confirms what is complete and what is at risk.

Update the calendar whenever the owner changes a date in writing, and file that change with the contract. A calendar that matches the contract is worth more than a perfect one that does not.

When the job is delayed, rebuild the remaining schedule rather than shifting the old one by a few days. Delays change which application covers which work, and a rough estimate of when the job will finish is not enough to plan the cash.

• Assuming a late application still counts for the cycle. Check the cut-off before you assume the work made it onto the current application.
• Treating silence as a final answer. Record the response date and keep any follow-up with the application.
• Accepting a verbal rejection. Ask for the disputed quantities, supporting records, and relevant contract clause in writing.
• Signing a final release early. Finish the open-items list first.
• Letting the schedule live in one person's head. When that person is out, the next application is often the one that slips.

Open your contract today and put the next application's cut-off, review date, and payment due date on the job calendar.

What if the billing cut-off is unclear?

Get the billing period and cut-off confirmed in writing before submitting the application. Keep that confirmation in the job file with the calendar.

What should the application response file contain?

Keep the submitted application, its arrival date, dated responses, and correspondence about amounts together. Update the file as each response arrives.

What should you gather before the final application?

Gather the open change list, the last approved application, collected lien waivers, and correspondence about unresolved items. Compare your records with the owner's file.