Forecast completion is 15 Oct 2026, 442 calendar days before the contract completion date of 31 Dec 2027.
Data dateData dateThe moment the schedule was statused. Everything before it is history; everything after is forecast.30 Sep 2026P6: Data Date, as the contractor's P6 stored it.
ScheduleNo progress recorded, so it reads as a baseline (14 activities not started)
Contract completionContract completionThe date the contract requires, including approved extensions. Only an approved document moves it.31 Dec 2027Finish On or Before constraint on 1014 End Project.
Forecast completionForecast completionWhen this schedule says the work will finish. It is the contractor's own forecast, not a contract date.15 Oct 2026Early finish of the completion milestone 1014. The last open activity finishes 15 Oct 2026 (A1010).
P6 scheduled finish31 Dec 2027The project finish P6 stored at its last calculation. It differs from the latest activity finish above; the two agree in a file that was scheduled after its last edit. Ask which one is current before relying on either.
Variance442 calendar days to spareForecast completion minus contract completion, in calendar days.
Float at completionFloatHow long an activity can slip before it delays the work that follows. Zero or less means it is driving the finish date.10 working daysTotal float P6 calculated on 1014 End Project, in working days of its calendar (Standard 5 Day Workweek).
Least float10 working days on 1000 (calendar: Standard 5 Day Workweek). Open activities with negative float: 0.Total float as P6 calculated it, open activities only.
Critical, by P6's settingThe file does not state the project's own critical-path setting.P6: Schedule Options, "Define critical activities as", as the contractor's P6 stores it.
Critical, our analysisCritical pathThe chain of activities that decides the finish date. Anything that slips on it moves the finish.No open activity is at zero or negative float. The least-float path carries 10 working days. The critical path (Longest Path) is 4 activities.Our reading of the total float P6 wrote into the file (at or below zero), and the chain we trace through it. Not necessarily what P6 calls critical.
Every value above is read as P6 calculated and stored it; nothing is recalculated. It describes the schedule, not the work on site.
The critical path (Longest Path)
The activities that drive the schedule's finish: a day of delay on any of them is a day of delay to the finish date - even when the schedule already finishes late.
4 open activities, 01 Oct 2026 to 15 Oct 2026, traced here back from the last finish through the relationship that holds each one. The file does not carry P6's own longest-path mark.
Float in this file is measured against the schedule's own calculated finish (no Must Finish By date is set in P6).
Critical activity
All 4 activities on the critical path
#
Activity ID
Name
Start
Finish
Float (work days)
1
1010
Install mechanical HVAC ductwork on levels two through six
01 Oct 2026
15 Oct 2026
10
2
1011
Roof Membrane
01 Oct 2026
15 Oct 2026
10
3
1012
Interior Painting
01 Oct 2026
15 Oct 2026
10
4
1014
End Project
01 Oct 2026
15 Oct 2026
10
Checked against USACE UFGS 01 32 01.00 10 Project Schedule
What in the file does not meet the specification you chose, and what needs your judgment.
◆4 blocking findings. These are requirements the specification states in absolute terms. Resolve them before submitting.
4
◆Blocking
4
▲Needs your judgment
4
◇More data needed
4
●Passed
◆ Not ready to submit
4 of 12 checks came back clean. 4 block a submittal; 4 need a decision from you or the owner's representative.
This is our arithmetic over the findings below, not the Government's decision. No score predicts whether your submittal is accepted — that is the owner's representative's, on the whole submission.
What to fix
The same findings, arranged by activity instead of by rule. Activities carrying at least one: 3. Needing something done to that activity in particular: 3.
Findings about the project, a calendar, a relationship, a code dictionary or a required activity that is absent: 11. Each rule's section below lists them, and the evidence export has every one.
Cash flow and earned value
What your cost loading ($130k) plans to earn over time - by the early dates and by the late dates P6 calculated - against what has been earned and recorded by the data date.
Planned, by the early dates
Earned to date
Planned by the data date - early dates$0 0%
Earned to date$0 0%
Earned value is at or above what the early dates plan by the data date: the work is ahead of, or on, its forecast.
How it is read: each activity's cost is spread evenly over its dates (actual dates for work done); earned value is each activity's cost times its percent complete.
“Activities with a negative cost loading is not allowed.”
Where this requirement comes from: USACE's own published requirement. Nothing recorded for this project changes it, and your contract governs if it says otherwise.
“Non-procurement activities Original Durations (OD) are not to exceed 20 workdays or 30 calendar days.”
Where this requirement comes from: USACE's own published requirement. Nothing recorded for this project changes it, and your contract governs if it says otherwise.
1 45.0 work days (maximum 20)
Activity / relationship
Finding
Evidence in the file (table, line, field = value)
1008 — Structural Steel Erection [line 23]
45.0 work days (maximum 20)
TASK L23 task_name=Structural Steel Erection; TASK L23 status_code=TK_NotStart; TASK L23 target_drtn_hr_cnt=360 (45.0 working days (360 h at 8 h per day, calendar Standard 5 Day Workweek)); TASK L23 remain_drtn_hr_cnt=360 (45.0 working days (360 h at 8 h per day, calendar Standard 5 Day Workweek)); TASK L23 clndr_id=1 (calendar Standard 5 Day Workweek)
How to fix: This edition allows no tolerance — every non-procurement activity must be at or under 20 work days or 30 calendar days. Break long activities into shorter, separately trackable steps. Note that DCMA-14 allows 5% over 44 days, so a schedule that passes a generic health check can still fail here.
DUR-02Remaining duration of unstarted activitiesSection 3.3.19◆Blocking
1 unstarted activity has a remaining duration below their original
“The remaining duration for unstarted activities are not to be less than its original duration.”
Where this requirement comes from: USACE's own published requirement. Nothing recorded for this project changes it, and your contract governs if it says otherwise.
1 remaining 5.0 vs original 20.0 days
Activity / relationship
Finding
Evidence in the file (table, line, field = value)
1012 — Interior Painting [line 27]
remaining 5.0 vs original 20.0 days
TASK L27 task_name=Interior Painting; TASK L27 status_code=TK_NotStart; TASK L27 target_drtn_hr_cnt=160 (20.0 working days (160 h at 8 h per day, calendar Standard 5 Day Workweek)); TASK L27 remain_drtn_hr_cnt=40 (5.0 working days (40 h at 8 h per day, calendar Standard 5 Day Workweek)); TASK L27 clndr_id=1 (calendar Standard 5 Day Workweek)
How to fix: An activity that has not started cannot have less work left than it began with. Reset remaining duration to equal the original, or justify the change as a scope reduction.
“Use the activity coding structure defined in the Standard Data Exchange Format (SDEF) in ER 1-1-11. This exact structure is mandatory. Develop and assign all Activity Codes to activities as detailed herein.”
Where this requirement comes from: USACE's own published requirement. Nothing recorded for this project changes it, and your contract governs if it says otherwise.
1 code absent from the dictionary
Activity / relationship
Finding
Evidence in the file (table, line, field = value)
PHAS
code absent from the dictionary
How to fix: Create all eight codes — WRKP, RESP, AREA, MODF, BIDI, PHAS, CATW, FOW — at exactly the lengths ER 1-1-11 specifies. Note that UFGS 3.12.a requires these codes to be defined at PROJECT level, not Global or EPS level.
▲Requires your judgment4
PROC-01Procurement activities presentSection 3.3.4▲Needs your judgment
No procurement activities were identified in the schedule at all
“Include in the schedule activities associated with the critical submittals and their approvals, procurement, fabrication, and delivery of long lead materials, equipment, fabricated assemblies, and supplies. Long lead procurement activities are those with an anticipated procurement sequence of over 90 calendar days.”
Where this requirement comes from: USACE's own published requirement. Nothing recorded for this project changes it, and your contract governs if it says otherwise.
—no activity whose name suggests submittal, approval, procurement, fabrication or delivery
Notes
4 activities that only submit or review a document (a bond, a plan, a personnel list, product data) are NOT counted as procurement chains here — nothing in them is bought, made or delivered. First: 1003, 1005, 1006, 1007.
How to fix: Only you know which items in this project are long lead — a procurement sequence over 90 calendar days. Review the incomplete chains: if the item is long lead, add the missing stages as separate linked activities. If it is not, no requirement applies.
CONT-01Mandatory activities presentSection 3.3.5▲Needs your judgment
9 mandatory activities could not be found in the schedule
“Include the following activities in the initial project schedule and all updates. a. Submission, review and acceptance of SD-01 Preconstruction Submittals (individual activity for each). b. Submission, review and acceptance of features requiring design completion Submission, review and acceptance of design packages. c. Submission of mechanical/electrical/information systems layout drawings. d. Submission and approval of O&M manuals. e. Submission and approval of as-built drawings. f. Submission and approval of DD1354 data and installed equipment lists. g. Submission and approval of testing and air balance (TAB). h. Submission of TAB specialist design review report. i. Submission and approval of fire protection specialist. j. Submission and approval of Building Commissioning Plan, Controls testing plan, test data, and reports: [...] k. Contractor's pre-final inspection. l. Correction of punch list from Contractor's pre-final inspection. m. Government's pre-final inspection. n. Correction of punch list from Government's pre-final inspection. o. Final inspection.”
Where this requirement comes from: USACE's own published requirement. Nothing recorded for this project changes it, and your contract governs if it says otherwise.
testing and air balanceno matching activity found
TAB specialist design review reportno matching activity found
fire protection specialistno matching activity found
building commissioning plan controls testingno matching activity found
contractor pre-final inspectionno matching activity found
correction of punch list from contractor pre-final inspectionno matching activity found
government pre-final inspectionno matching activity found
correction of punch list from government pre-final inspectionno matching activity found
final inspectionno matching activity found
Notes
DD1354 data and installed equipment list — matched "DD1354 Data Submission" (wording differs from the spec)
mechanical electrical information systems layout drawings — possible match: "MEP Systems Layout Drawings" — confirm this is the same item
How to fix: The specification lists fifteen activities that must appear in the initial schedule and every update. Where an item is genuinely absent, add it. Where we matched wording that differs from the spec, no action is needed — the note is there so you can confirm we read it correctly.
LOG-05End Project finish milestone and float behaviourSection 3.3.8.2▲Needs your judgment
The closing milestone is in place, but its float could not be compared with the contract completion date - enter that date in the questionnaire
“The last activity in the schedule must be a finish milestone titled "End Project." Constrain the project schedule to the Contract Completion Date in such a way that if the schedule calculates an early finish, then the float calculation for "End Project" milestone reflects positive float on the longest path. If the project schedule calculates a late finish, then the "End Project" milestone float calculation reflects negative float on the longest path.”
Where this requirement comes from: USACE's own published requirement. Nothing recorded for this project changes it, and your contract governs if it says otherwise.
Notes
The contract completion date was not supplied, so one half of this requirement could not be evaluated: whether the float on this milestone agrees with the contract date. Everything above was read from your file. Supply the contract data and the float comparison runs too.
How to fix: The last activity must be a finish milestone titled "End Project", constrained to the Contract Completion Date so that an early finish shows positive float and a late finish shows negative float on the longest path.
CAL-01Adverse weather accounted forSection 3.3.9▲Needs your judgment
No weather calendar found. The specification permits another method, but it must be discussed at the SEKO meeting — make sure you have an answer
“Ensure anticipated adverse weather is accounted for in the Project Schedule. AACE 84R-13 provides methodologies for techniques in planning for adverse weather. The preferred methodology is the use of a weather calendar. If a method other than a weather calendar is proposed, discuss the reason during the SEKO meeting.”
Where this requirement comes from: USACE's own published requirement. Nothing recorded for this project changes it, and your contract governs if it says otherwise.
Notes
Not assessed from the file: whether the number of weather days matches your contract, or whether another weather method was agreed at the SEKO meeting.
How to fix: The preferred method for accounting for adverse weather is a weather calendar. If you use another method, be ready to explain it at the SEKO meeting.
◇Checks we can run if you supply more data4
COST-03Punch list correction cost-loaded at 1 percent minimumSection 3.3.20◇More data needed
Cannot evaluate — missing contract data: Present contract value in USD
Where this requirement comes from: USACE's own published requirement. Nothing recorded for this project changes it, and your contract governs if it says otherwise.
COST-04As-built drawings cost loading floorSection 3.3.20.1◇More data needed
Cannot evaluate — missing contract data: Present contract value in USD
Where this requirement comes from: USACE's own published requirement. Nothing recorded for this project changes it, and your contract governs if it says otherwise.
DUR-03Original duration changes require approvalSection 3.3.15◇More data needed
Requires two schedules — run with --previous
Where this requirement comes from: USACE's own published requirement. Nothing recorded for this project changes it, and your contract governs if it says otherwise.
LOG-03No unauthorised constrained datesSection 3.3.8◇More data needed
Cannot evaluate — missing contract data: Contract completion date
Where this requirement comes from: USACE's own published requirement. Nothing recorded for this project changes it, and your contract governs if it says otherwise.
10 activities on a 5- or 6-day calendar are not measured here: on a work-day calendar the 3.3.2 limit is the 20 workdays checked by DUR-01, whatever the activity spans in calendar days.
SUB-01Preliminary schedule scope and cost balanceSection 3.4.1○Not evaluable
Applies only to the preliminary submission. You did not say which submission this is, so it is treated as not preliminary.
SDEF-UNITUnit Cost Record viabilitySection 3.3.7 / ER 1-1-11 App A○Not evaluable
This file carries no unit-of-measure data, so no Unit Cost Records are produced
Notes
Unit Cost Records apply only to activities that are not lump sum. Most USACE construction is lump sum, and this is the normal result.
P6-03Activity duration type is Fixed Duration and UnitsSection 3.12.c○Not evaluable
This file does not record a duration type
NAME-01Activity names have a verb-noun structureSection 3.12.j○Not evaluable
Not checked in this report.
■Contract context4
COST-02No front-end loadingSection 3.2.1■Context
No sign of front-end loading: 27% of the cost-loaded value falls in the first third of the schedule, and value never runs more than 5 percentage points ahead of time (largest: +3). The curve is shown for your records; reasonableness itself is the Contracting Officer's judgement.
“Activity cost loading must be reasonable and without front-end loading.”
Value earned by elapsed time
% of time
% of value
Divergence
25%
26.7%
+1.7
50%
53.3%
+3.3
75%
73.3%
-1.7
INFO-01Withholding and payment rejection exposureSection 3.2.3■Context
Failure to meet the requirements of this specification may result in the disapproval of the preliminary, initial, or periodic schedule updates and subsequent rejection of payment requests until compliance is met. In the event that the Contracting Officer directs schedule revisions and those revisions have not been included in subsequent Project Schedule revisions or updates, the Contracting Officer may withhold 10 percent of pay request amount from each payment period until such revisions to the project schedule have been made.
“Failure to meet the requirements of this specification may result in the disapproval of the preliminary, initial, or periodic schedule updates and subsequent rejection of payment requests until compliance is met. In the event that the Contracting Officer directs schedule revisions and those revisions have not been included in subsequent Project Schedule revisions or updates, the Contracting Officer may withhold 10 percent of pay request amount from each payment period until such revisions to the project schedule have been made.”
Notes
Ten percent of each pay request, withheld until the revisions the Contracting Officer directed appear in the schedule. This is what a schedule deficiency costs on a USACE contract, and it is why the rest of this report is worth the half hour.
DUR-05Curing and acceptance periodsSection 3.3.2 / 3.3.10■Context
No activity models a cure, but 1 activity is work whose UFGS section has a paragraph on curing
“Non-procurement activities Original Durations (OD) are not to exceed 20 workdays or 30 calendar days. Develop calendars to accommodate any contract defined work period such as a 7-day calendar for Government Acceptance activities, concrete cure times, etc.”
A1010 — Concrete Foundations [line 24]section 03 30 00 Cast-In-Place Concrete has a paragraph on curing; no cure follows this work in the schedule
Notes
3.3.10 asks for calendars that accommodate contract work periods such as concrete cure times. If the cure is carried inside these durations, say so in the narrative; if it is not, add the cure as its own activity on a 7-day calendar. The sections are read from the federal guide specifications (UFGS) by each activity's name, or taken from your own WBS or activity codes where they name the section - confirm against your contract's specifications.
SDEF-IDActivity ID must be numeric, max 10 digitsSection ER 1-1-11 App A, ACTV note (2)■Context
The Activity ID consists of a right-justified field of ten (I0) integers each. The maximum activity number allowed under this arrangement is 9999999999.
“The Activity ID consists of a right-justified field of ten (I0) integers each. The maximum activity number allowed under this arrangement is 9999999999.”
Notes
For information, not a finding. ER 1-1-11 describes the SDEF activity ID as ten digits, but the current UFGS (3.12.i) limits an activity ID to 10 characters - letters included - and every real federal SDEF file we hold, USACE's own sample among them, uses letters. The 10-character limit is checked separately. And this concerns the SDEF file only: RMS also imports a P6 XML file (since October 2023) and lists P6 XER files in its import screen (since January 2026), and neither has SDEF's fixed columns. Ask your Resident Office which file your contract accepts.
Extend the check
Each item below is a check we can run if you supply the value. Nothing here is required — what you leave out is simply not checked, and is never counted against you.
Full contract number Enables: Confirms the file carries the contract number
Notice to Proceed date Enables: Schedule does not start before the NTP; the preliminary 90-day window
Contract completion date Enables: End Project constraint, negative float behavior, early completion
Present contract value in USD Enables: Minimum cost loading for punch list and as-built activities
Contract line items (CLINs), each with its value Enables: Cost balance against contract line items and BIDI code validity
The Government's P6 version (established at the SEKO meeting) Enables: Export is no newer than the Government's version
Project type: construction or design-build Enables: Which mandatory activities apply
Submission type: preliminary, initial or update Enables: Which submission requirements apply
Where is the project? The ZIP code, or the city and the state Enables: NOAA's rainy days for your area, against the weather calendar
What this check could not look at
Part of this specification cannot be verified from a schedule file: meetings to attend, documents that travel alongside the schedule, and decisions the contract reserves to the owner's representative. They are listed here so nothing is quietly dropped.
References, submittal procedure and scheduler qualifications · Paragraphs 1.1, 1.2, 1.3, 3.1, 3.3, 3.4, 3.5 The contract names the reference standards, the submittal route your schedule must travel, and the experience your scheduler must hold. Confirm the person preparing the schedule meets the stated qualifications and that the submittal goes through the specified channel.
Scheduling software · Paragraphs 2.1, 2.1.1, 2.1.2, 2.1.2.2 The specification states which software is acceptable and what you must provide if you use something other than the Government default. A file that opens on your machine is not evidence that it opens on theirs — confirm the version before submitting.
Meetings you must attend · Paragraphs 3.1.1, 3.6, 3.6.1, 3.6.2, 3.7 A Scheduling Expectations Kickoff Meeting at the start, a schedule update meeting each period, and weekly progress meetings throughout. The update you submit must be the one agreed at the meeting. Missing these is a compliance failure no file inspection can reveal.
Documents submitted alongside the schedule · Paragraphs 3.5.2, 3.5.3, 3.5.3.1, 3.5.3.2, 3.5.4, 3.5.4.1, 3.5.4.2, 3.5.4.3, 3.5.4.4, 3.5.4.5 A narrative report, a logic report, an earnings report by CLIN, and a network diagram showing continuous flow, milestone dates, the critical path and the required grouping and sorting. The schedule file alone is an incomplete submission. Where you supply a previous update, the progress section of this report computes the 3.5.3.2 earnings figures — grouped by CLIN, with CLIN and project percentages — from your own file. Assembling and submitting the documents is still yours to do.
Level of detail and the update cycle · Paragraphs 3.3.1, 3.4.2.1, 3.4.3 The required level of detail, design package fragnets for design-build work, and the periodic update cycle. Whether the schedule is broken down finely enough to measure progress honestly is a judgment made by the reviewer, not by a rule.
Time extensions and delay analysis · Paragraphs 3.8, 3.8.1, 3.8.2, 3.8.3, 3.8.4, 3.8.5, 3.8.6, 3.8.7 Justifying delay, distinguishing changes that do not cause delay, time impact analysis for prospective claims, forensic analysis for retrospective ones, fragnets, and the effect on an early completion schedule. These are procedures to follow when something goes wrong, not properties of the file.
Rights the contract reserves · Paragraphs 3.9, 3.9.2, 3.9.3, 3.10 Failure to perform, the recovery schedule the Government may require, and the ownership of float. Float belongs to the project, not to either party alone — meaning you cannot assume spare time in the schedule is yours to consume.
Uploading the schedule into the system of record · Paragraphs 3.11 The schedule data has to reach the Government's Construction Contract System of Record. Payment under FAR 52.232-5 depends on the Government receiving an acceptable and approvable electronic version — so this step is not administrative housekeeping, it is the step your progress payment is conditioned on.
Cost reasonableness is one of these. Where the specification says an amount must be "reasonable" or is "subject to approval", the decision belongs to the owner's representative. Confirm your cost loading with the owner before you submit, not after the first pay application is rejected.
None of the items above counts against this schedule. They are the parts of the specification a file cannot evidence, and they remain yours to satisfy.