UFGS 01 32 17 monthly update review
On NAVFAC contracts the contractor submits a cost-loaded P6 schedule update every month, and the government accepts it before the invoice is processed. Below: what the update must contain, what the reviewer checks, and a free check of the .xer file in your browser.
The monthly update
- When: "within 5 calendar days of the data date", every month, even with no progress and no invoice (1.4.2.b).
- Why it matters: "The submission of an accepted, updated NAS to the Government is a condition precedent to the processing of the Contractor's invoice" (1.4.2.a).
- File: native P6 .xer, exported as version 17 or earlier; data converted from other software is cause for rejection (1.8). The file name carries the project name and the data date as yyyy-mm-dd (1.10.3.c).
- Reports with it (1.10.3): the time-scaled logic diagram with the longest path in red; a comparison with the previous update (previous month as the baseline, start and finish deltas, longest path filter); the P6 scheduling log; the narrative; earned value and cash-flow reports; longest-path diagrams for the next 60 days and to the contract completion date; the monthly update checklist signed by the scheduler.
- Meeting: a monthly update meeting where the scheduler presents in P6 (1.4.1).
What the reviewer checks
NAVFAC's Monthly Project Schedule Review Checklist (January 2025) has 120 items, each certified by the contractor and reviewed by the government. The main rules, with what the free check on this page covers:
| Rule | Spec | On this page |
|---|---|---|
| Native .xer, P6 version 17 or earlier | 1.8 | The P6 version and export date are shown |
| Every activity has a predecessor and a successor, except contract award and the contract completion milestone | 1.10.1.2.a | Counted (DCMA check 1, missing logic) |
| No leads or lags without the Contracting Officer's approval | 1.10.1.2.c | Counted (checks 2 and 3), with the activities listed |
| No date constraints beyond the contract's unless accepted | 1.10.2.a | Hard constraints counted (check 5) |
| No progress after the data date | Checklist item 28 | Actual dates after the data date counted (check 9) |
| Negative float on the longest path when projected completion is after the contract completion date, explained in the narrative | 1.10.2.c, checklist 26 | Negative float counted and listed (check 7, float finder) |
| Critical activities defined as the longest path | 1.10.1.3 | Critical activities listed in start order |
| Task Dependent activities only, no Level of Effort | 1.10.1.2.h | Activity type shown in the table |
| On-site construction activities at most 20 working days | 1.10.1.5.6 | Original duration shown in the table and the CSV (the DCMA check flags over 44 days) |
| Retained logic, no out-of-sequence progress | 1.4.2.f | Not checked |
| Activities not deleted or renamed; IDs not reused | 1.10.1.2.e-g | Not checked: needs the previous update |
| Cost loading equals the contract value, not front-end loaded | 1.10.1.10 | Not checked: costs are not read |
Sources, read 24 October 2026: UFGS 01 32 17.00 20 (May 2025) and NAVFAC's review checklist (January 2025). The bracketed options in the spec are set per contract; check yours.
The narrative and the changes
Every update comes with a narrative that lists each change since the previous update, by activity ID and name, with the date and reason: added or deleted activities, durations, logic, constraints, calendars, cost loading (1.10.3.e). The schedule narrative template has these sections in order. Checking that the narrative matches the file means comparing this update with the last one, activity by activity.
USACE contracts: UFGS 01 32 01.00 10
The USACE section (August 2026) asks for an update at least monthly with a meeting within five days of the data date, the .xer in a P6 version no newer than the government's, the longest path as the critical path and retained logic. It also prohibits leads and start-to-finish links, and allows only two open ends. The Contracting Officer "may withhold 10 percent of pay request amount" when required revisions are not made (3.2.3) (UFGS 01 32 01.00 10).
Check this month's .xer
Open the update below. The file is read in your browser and never uploaded, so it stays on your computer; you can download the results as CSV or print them for the review file.
Primavera P6 .xer, or MS Project saved as .xml (File > Save As > XML). It is read on your computer and never uploaded.
Your monthly schedule update review, mostly done
Every logic, duration, float and date change since the last update and the baseline, in the browser, without Claim Digger. The UFGS / FDOT review checklist filled in, and a draft narrative for the owner: what moved, why the finish date changed, whose activities are affected.
One review report a month
One update, no subscription
For teams that review many contractors
Join the waitlist and we will write to you once when it is ready to try.