Quick answer: UFGS 01 32 01.00 10 is the Unified Facilities Guide Specification covering CPM network analysis schedules on USACE and other federal construction contracts. It sets scheduling-tier requirements by contract size, submission deadlines for the baseline and periodic updates, narrative reporting content, and the criteria reviewers use to accept or reject a schedule.
What UFGS 01 32 01.00 10 Is
UFGS 01 32 01.00 10 is one of the Unified Facilities Guide Specifications jointly maintained for use on US Army Corps of Engineers (USACE), NAVFAC, and other federal design and construction contracts. It is the standard section that defines how a contractor must develop, submit, and maintain a Critical Path Method (CPM) schedule in Primavera P6 for the life of the contract. Because it is a guide specification, the version attached to a specific contract may include project-specific modifications, so the project's own Section 01 32 01.00 10 (or a renumbered equivalent) always controls over general industry practice.
The specification exists to make schedule submissions predictable and comparable across contracts — the same activity coding conventions, the same update cycle, and the same acceptance criteria apply whether a Resident Engineer is reviewing a schedule for a flood control project or a vertical construction project.
Scheduling Specification Tiers
Federal scheduling specifications, including UFGS 01 32 01.00 10, typically scale their requirements to the size and complexity of the contract. Rather than applying the same level of detail to every project regardless of value, the specification sets tiers — sometimes labeled by contract dollar value or duration — where smaller or shorter-duration contracts have reduced requirements (fewer required activity codes, a simpler bar-chart or milestone schedule) and larger contracts require a fully developed, resource- and cost-loaded CPM network with more extensive reporting. The exact thresholds and tier definitions are set in the project-specific specification section, so the first step on any new contract is confirming which tier applies before building the schedule.
Baseline and Update Submission Timelines
The specification establishes two recurring submission obligations:
- The baseline schedule. The contractor submits an initial CPM schedule early in the contract period, within a number of calendar days set by the project's own specification section. This baseline has to be reviewed and formally accepted by the government before it becomes the schedule of record against which progress and delay are measured.
- Periodic updates. After baseline acceptance, the contractor submits schedule updates on a recurring cycle — monthly updates are the most common cadence on USACE contracts — reflecting actual progress, logic changes, and any schedule impacts that occurred during the period.
Missing either deadline, or submitting a schedule that does not meet the specification's technical requirements, typically triggers a resubmission cycle rather than acceptance, which is why confirming the exact submission dates and required format (P6 XER export is standard) before the deadline matters more than it might appear.
Narrative Reporting Requirements
Every baseline and update submission under UFGS 01 32 01.00 10 is expected to be accompanied by a written narrative, not just the schedule file itself. A compliant narrative generally addresses:
- A summary of progress during the reporting period and any change to the projected completion date.
- An explanation of the current critical path and near-critical paths.
- A description of any logic, duration, or constraint changes made since the prior update, and why they were made.
- Identification of delays encountered during the period, their cause, and any corrective action planned.
- Look-ahead information on upcoming work.
A schedule file submitted without a narrative, or with a narrative that only restates what the schedule already shows without explaining the changes, is one of the most common reasons a submission gets returned for revision.
Update Frequency
Monthly updates are the typical cadence specified, aligned with the progress payment cycle, though the project-specific specification governs. Some contracts also require interim updates tied to specific milestones, or a recovery schedule submission if the contractor falls behind by a threshold the specification defines.
Typical Review Criteria
Government schedulers and Resident Engineers reviewing a UFGS 01 32 01.00 10 submission generally check for the same categories of issues that any disciplined CPM quality review covers: logic density and open-ended activities, unjustified constraints, excessive lags used in place of real activities, cost- and resource-loading reconciliation to the contract value, correct activity coding for the project's work breakdown structure, and consistency between the narrative and the schedule data. Many of these line up closely with the widely used DCMA 14-point schedule check — see our explanation of the DCMA 14-point schedule check for how those individual metrics work. For the software mechanics behind building a schedule that survives this kind of review, see the most common Primavera P6 schedule errors that reviewers flag.
Practical Steps Before Your Next Submission
- Confirm the exact UFGS section number and any project-specific modifications attached to your contract — do not assume the generic specification language applies unmodified.
- Identify which scheduling tier your contract falls into and build the schedule to that tier's requirements from the start.
- Build the required activity coding structure into P6 before developing the detailed network, not after.
- Reconcile cost and resource loading to the contract value before every baseline and update submission.
- Write the narrative as a stand-alone explanation of what changed and why — not a restatement of schedule data a reviewer can already see in the file.
- Track submission deadlines for the baseline and every subsequent update against the specification's stated day counts, not the project's informal expectations.
For broader context on how USACE project controls systems connect to the schedule submitted under this specification, see USACE QCS and RMS: what contractors need to know.