Monitoring contractor progress is the continuous work of verifying that what the contractor is doing on site matches what the contract says the contractor is supposed to be doing, at the pace the contractor committed to, with the quality the contract requires. It runs from the day construction NTP issues until the day you sign the final acceptance.

Two clocks run at the same time during performance. The performance clock is the calendar the contractor is racing against to reach substantial completion, governed by FAR 52.211-10 and the NTP. The pay clock is the monthly cycle where the contractor bills for work performed and the government pays based on verified progress. The contracting officer's job on the monitoring side is to make sure these two clocks stay honest relative to each other. If the pay estimate is showing 60 percent complete but the schedule update is showing the project is two months behind, something is wrong with at least one of those numbers.

The contractual hook for requiring a contractor schedule is FAR 52.236-15, Schedules for Construction Contracts. It is prescribed at FAR 36.515. The clause is short. It requires the contractor to prepare and submit to the contracting officer, for approval, a practicable schedule showing the order in which the contractor proposes to perform the work, and the dates on which the contractor contemplates starting and completing the several salient features of the work, including acquiring materials, plant, and equipment. The clause also gives the CO the right to require the contractor to update the schedule if the contractor falls behind.

On operational contracting work, the schedule is usually a bar chart, sometimes called a Gantt chart. Each row is an activity. Each bar runs along a calendar showing planned start and finish. Major milestones (mobilization, demolition, rough-in, dry-in, substantial completion) are called out. Monthly updates overlay actual progress against the planned bars so you can see what is on track, what is ahead, and what is behind.

The clause does not specify the format. The operational details come from the project spec section on schedules, which varies by contract. Read the spec before your first monthly progress meeting so you know what format the contractor owes you, what the update cadence is, and what the narrative requirements look like.

The contractor's baseline schedule comes in as a submittal, the same way product data and shop drawings come in. See I-13 Material Submittals for the mechanics of how submittals are reviewed. The schedule runs through the same loop: contractor prepares it, contractor sends it in, government reviews it, government returns it with an action.

Reviewing a baseline schedule is a specific kind of submittal review. The things to check are practical rather than legal:

• Does the schedule end on or before the contract completion date? If the contractor's planned finish is after the contract completion date, the schedule is not practicable on its face. It needs to come back.
• Are the major milestones all represented? Mobilization, long-lead submittals, long-lead procurement, critical predecessor activities, substantial completion, punch list, final acceptance.
• Is the sequencing logical? You do not need to run a CPM analysis to see if the contractor has the roof going on before the deck is down.
• Do the durations look reasonable? Field experience on the government side is the check here. CE and the COR should be part of this review.
• Is there float left at the end? A schedule that uses every single day up to the contract completion date leaves the contractor no room for weather, delivery delays, or the hundred things that go sideways. A schedule with zero float on day one is a red flag.

The baseline schedule typically needs to be approved before construction NTP issues. That is how the government makes sure there is an agreed-upon picture of how the project is going to run before the clock starts. Monthly updates during performance are not separate submittals in the same formal sense; they are status reports against the approved baseline, usually submitted with or as part of the monthly pay estimate package.

The payment side of the monitoring problem is governed by FAR 52.232-5, Payments Under Fixed-Price Construction Contracts. It is prescribed at FAR 32.111(a)(6) and is the standard payment clause for fixed-price construction. Every operational CO should be able to find this clause quickly because it comes up every single pay cycle.

The core rule is that the government will make progress payments monthly as the work proceeds, based on estimates of work accomplished which meet the standards of quality established under the contract, as approved by the contracting officer. That sentence is doing a lot of work. A few pieces of it matter a lot on the monitoring side.

The CO is not a rubber stamp on the contractor's pay estimate. The CO is the decision authority on how much gets paid. In practice this means the CO relies heavily on CE, the COR, and QA for site verification, but the CO owns the final number.

Before the first pay estimate can be processed, the contractor has to give the government a schedule of values. This is a breakdown of the total contract price into payable line items, usually organized by specification division or by major work activity. Each line has a dollar value, and the sum of all lines equals the contract price. The schedule of values is the ruler you measure the monthly pay estimates against.

A small roof replacement might have a schedule of values with ten to fifteen lines: mobilization, demolition, deck repair, insulation, membrane, flashing, accessories, closeout, as-builts, demobilization. A larger project breaks into more lines. Each line is valued up front, usually during the submittal phase, and approved by the CO.

The monthly cycle then runs like this:

1. Contractor submits a pay estimate. The contractor reports percent complete on each schedule of values line, multiplies percent complete by line value to get earned this period plus previously earned, subtracts retention and previous payments, and arrives at the amount due this period.
2. Government walks the site. CE, the COR, and QA walk the work in place and verify the percent complete claimed. The government can adjust any line down if the site does not match the claim.
3. The CO reviews and approves. The CO signs the adjusted pay estimate and authorizes payment.
4. Contractor invoices through WAWF. The contractor submits the approved pay estimate as an invoice through Wide Area Workflow (WAWF), which routes through the government acceptance and payment process.
5. Government pays. Payment issues per the contract terms and FAR 52.232-27 Prompt Payment for Construction Contracts, which governs the timing of progress payments on construction.

Retention is the portion of each progress payment the government holds back, releasing it later when performance milestones are met. There are two layers of retention under FAR 52.232-5 and most project specs, and they are often confused.

The second one is the lever. When a contractor is falling behind and the usual conversation and recovery plan are not getting traction, the CO can increase retention under 52.232-5(e) to put real cash pressure on the contractor without having to escalate to a cure notice, a show-cause letter, or a termination. It is a graduated response. The contractor feels the slippage in its own cash flow, and that alone often produces the recovery the government wanted.

Using this tool requires a finding by the CO that progress is unsatisfactory. That finding should be documented in the contract file, explained in writing to the contractor, and tied to specific observed slippage (schedule variance, missed milestones, stalled work) rather than generalized dissatisfaction. Document the trigger, document the increased retention, document what the contractor would have to show to get it released.

Slippage happens on almost every construction project. The question is not whether the contractor will fall behind; the question is what the CO does about it when it starts showing up in the schedule updates and the site walks.

The usual response ladder, in rough order of escalation:

• Flag the slippage in the monthly progress meeting. Put it on the record, ask the contractor for a written explanation, ask for a recovery plan.
• Require a recovery schedule. The contractor submits an updated schedule showing how it intends to get back on track, including any acceleration, rescheduling, or added crew or shift that will bring the finish date back to the contract completion date.
• Reduce the current pay estimate. If work that was supposed to be done is not done, the pay estimate for that line comes down accordingly. That is not retention, it is simply billing only for what was actually accomplished.
• Increase retention under 52.232-5(e). The CO makes the unsatisfactory progress finding and holds additional retention until progress improves.
• Issue a cure notice. Formal notice under FAR 49.402-3 that gives the contractor a specified period (usually ten days) to cure the default or face termination for default. This is a major escalation and should not be the first move.
• Termination for default. The nuclear option. Rare, consequential, and document-heavy. Not something to reach for lightly.

Underneath the monthly pay cycle is the daily reporting layer. Most construction contracts require the contractor to submit a daily Quality Control report covering what work was performed, what crews and equipment were on site, weather conditions, any incidents or deficiencies, and any tests or inspections performed. The government, in turn, maintains a daily log on the government side, kept by the COR or CE inspector, recording what the government observed.

These two records are the continuous paper trail of performance. When a dispute later turns on what happened on a specific day, the daily reports and the daily logs are the first place the record gets built. They are also the source material for the monthly pay estimate and schedule update, because everything that shows up as percent complete or as progress on an activity is supposed to trace back to the daily record of what was actually done.

The monthly progress meeting is where all of this comes together. A typical agenda walks through the updated schedule, the pay estimate, open RFIs, open modifications, upcoming work, schedule concerns, safety statistics, and any administrative items. The meeting produces minutes that document what was said and decided, in the same way preconstruction conference minutes do. See I-12 Preconstruction Conferences for the minutes discipline that carries forward into these monthly meetings.