As-built activity loaded at $10,000, required $50,000 (the greater of $35,000 and 1 percent, capped at $200,000)
"If there is no separate contract line item (CLIN) for as-built drawings, cost load the "Submission and approval of as-built drawings" activity not less than $35,000 or 1 percent of the present contract value, whichever is greater, up to $200,000."
How to fix: Where there is no separate CLIN for as-builts, load the submission and approval activity to the greater of $35,000 or 1 percent of the present contract value, up to $200,000.
"Non-procurement activities Original Durations (OD) are not to exceed 20 workdays or 30 calendar days."
1008 — Structural Steel Erection [line 23]45.0 work days (maximum 20)
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.19Blocking
1 unstarted activities have a remaining duration below their original
"The remaining duration for unstarted activities are not to be less than its original duration."
1012 — Interior Painting [line 27]remaining 5.0 vs original 20.0 days
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."
PHAScode 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.
"Assign a Bid Item Code to all activities using the Contract Line Item Number (CLIN) to which the activity belongs, even when an activity is not cost loaded. An activity can have only one BIDI Code."
1 of the 7 are milestones, which carry no work of their own. Milestones are the rows most likely to be accepted without a BIDI code - look at the remaining work activities first.
How to fix: Code every activity to the CLIN it belongs to, including activities that carry no cost. An activity may carry only one BIDI code, and the field is six characters.
LOG-02Mandatory constraints that override logic prohibitedSection 3.3.8Blocking
1 activities carry a Mandatory constraint, which overrides logic
"Mandatory constraints that ignore or affect network logic are prohibited."
How to fix: Mandatory Start and Mandatory Finish override the network. Replace with a Start On or After / Finish On or Before constraint, or with proper logic.
LOG-04NTP Acknowledged start milestone with Start On constraintSection 3.3.8.1Blocking
The opening milestone does not match the specification
"The first activity in the project schedule must be a start milestone titled "NTP Acknowledged," which must have a "Start On" constraint date equal to the date that the NTP is acknowledged."
1000 — NTP Acknowledged [line 16]constraint — instead of Start On
How to fix: The first activity must be a start milestone titled "NTP Acknowledged" with a Start On constraint equal to the date the NTP was acknowledged.
REL-01Only two open-ended activitiesSection 3.3.11Blocking
4 open ends — the specification permits only two
"Only two open ended activities are allowed: the first activity "NTP Acknowledged" is to have no predecessor logic, and the last activity "End Project" is to have no successor logic."
1000 — NTP Acknowledged [line 16]no predecessor + no successor
How to fix: Exactly two activities may be open: the first, named "NTP Acknowledged", with no predecessor, and the last, named "End Project", with no successor. Every other activity needs logic on both ends.
REL-02Required relationship types on every activitySection 3.3.11Blocking
2 activities lack a required relationship type
"Except as noted above, each activity must have at least a start-to-start or finish-to-start relationship with its predecessor and a finish-to-finish or finish-to-start relationship with its successor."
A1010 — Concrete Foundations [line 24]no finish-to-finish or finish-to-start successor
1010 — Install mechanical HVAC ductwork on levels two through six [line 25]no start-to-start or finish-to-start predecessor
How to fix: Having a predecessor is not enough — it must be the right kind. Each activity needs an SS or FS link to its predecessor and an FF or FS link to its successor. No generic schedule tool checks this.
1008 [line 23] → A1010 [line 24]negative lag of -2.0 days (FS)
How to fix: Leads are prohibited outright. Replace each with a proper relationship type — usually an SS link with a positive lag expresses the same intent.
The schedule is set to progress override, which is expressly prohibited
"Schedule calculations must retain the logic between predecessors and successors ("retained logic" mode) even when the successor activity starts and the predecessor activity has not finished (out-of-sequence progress). Software features that in effect sever the tie between predecessor and successor activities when the successor has started and the predecessor logic is not satisfied ("progress override") are not be allowed."
Schedule Options [line 13]progress override instead of retained logic
How to fix: In P6: Schedule Options, set "When scheduling progressed activities use" to Retained Logic. Progress override severs predecessor links once a successor starts, which hides the real effect of out-of-sequence work.
SDEF-CSTROnly ES and LF constraints survive SDEF exportSection ER 1-1-11 App A, ACTV note (6)Blocking
1 constraints are neither ES nor LF — the export will lose them
"The valid values for the constraint type are as follows: ES - The constraint date must replace an activity's early start date, if the early start date is prior to the constraint date. LF - The constraint date must replace an activity's late finish date if the late finish date is after the constraint date."
1011 — Roof Membrane [line 26]Mandatory Start — cannot be represented in SDEF
How to fix: SDEF carries only ES (early-start replacement) and LF (late-finish replacement). Mandatory Start, Mandatory Finish and As Late As Possible have no representation and are silently dropped.
COST-06Submittal activities carry no costSection 3.2.2Blocking
1 submittal activities carry cost outside the permitted exceptions
"No costs are to be assigned to activities for the preparation, review, or approval of submittals, except as described under paragraph COST LOADING OF CLOSEOUT ACTIVITIES, paragraph AS-BUILT DRAWINGS, design submittals, and paragraph O&M MANUALS."
1002 — SD-01 Preconstruction Submitta [line 17]loaded at $10,000
How to fix: Costs may not be assigned to preparing, reviewing or approving submittals, except for closeout activities, as-built drawings, design submittals and O&M manuals. Move the value to the physical work it represents.
SDEF-EXPSDEF export viabilitySection 3.3.7 / ER 1-1-11 App ABlocking
2 fields will not fit the SDEF fixed-column format — the RMS upload will fail
"Use the activity coding structure defined in the Standard Data Exchange Format (SDEF) in ER 1-1-11. This exact structure is mandatory."
Export failures by field
Field
Failures
activity_id
1
description
1
A1010 — Concrete Foundations [line 24]activity ID "A1010" is not numeric (SDEF requires an integer)
1010 — Install mechanical HVAC ductwork on levels two through six [line 25]description is 58 characters (columns 17–46 allow 30)
How to fix: SDEF is a fixed-column format: each field has a start column and a width, and a value that overruns makes the record malformed. These failures are invisible in P6 — the schedule looks correct right up to the moment RMS rejects the upload. Shorten the offending values, renumber alphanumeric activity IDs, and make sure every activity carries a calendar. Where a code carries two values on one activity, remove one: the format has a single column per code.
COST-08Cost loading balances to the contract line itemsSection 3.2 / 3.3.7.5Blocking
2 balance problems between the schedule and the contract line items
"Assign a Bid Item Code to all activities using the Contract Line Item Number (CLIN) to which the activity belongs, even when an activity is not cost loaded."
Activities carrying no BIDI code$55,000 is loaded on activities carrying no BIDI code
How to fix: RMS reconciles the cost-loaded schedule against the contract line items and rejects the upload when they disagree. Every activity must carry a BIDI code naming its CLIN, and the total loaded against each CLIN must equal the contract value for it. Cost sitting on activities with no BIDI code has nowhere to land.
O&M manuals activity loaded at $10,000, minimum required is $20,000
"Cost load the "Submission and approval of O&M manuals" activity not less than $20,000. Activity will be declared 100 percent complete upon the Government's approval."
1005 — Submit O&M Manuals [line 20]$10,000
How to fix: Cost load the O&M manuals submission and approval activity to at least $20,000.
Requires your judgement (14)
COST-02No front-end loadingSection 3.2.1Needs your judgement
27% of the value cost-loaded in this schedule falls in its first third (maximum divergence from the time line: +3 percentage points)
"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
1000 — NTP Acknowledged [line 16]$10,000 — 7.7% of total value
1002 — SD-01 Preconstruction Submitta [line 17]$10,000 — 7.7% of total value
1003 — Design Package Submission [line 18]$10,000 — 7.7% of total value
1004 — MEP Systems Layout Drawings [line 19]$10,000 — 7.7% of total value
1005 — Submit O&M Manuals [line 20]$10,000 — 7.7% of total value
1006 — As-Built Drawings Approval [line 21]$10,000 — 7.7% of total value
1007 — DD1354 Data Submission [line 22]$10,000 — 7.7% of total value
1008 — Structural Steel Erection [line 23]$10,000 — 7.7% of total value
How to fix: This is not a finding of non-compliance. The specification leaves the judgement of "reasonableness" to the Contracting Officer and requires you to provide documentation only if asked. A divergence above roughly 15 percentage points in the first third is what reviewers commonly question. Prepare a justification for the activities listed above — usually mobilisation, long-lead procurement or pre-paid equipment.
PROC-01Procurement activities presentSection 3.3.4Needs your judgement
"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."
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.5Needs your judgement
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 / 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."
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
mechanical electrical information systems layout drawings — possible match: "MEP Systems Layout Drawings" — confirm this is the same item
DD1354 data and installed equipment list — possible match: "DD1354 Data Submission" — 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-03No unauthorised constrained datesSection 3.3.8Needs your judgement
1 constrained dates do not appear in the contract
"No constrained dates are allowed in the schedule other than those specified herein."
1011 — Roof Membrane [line 26]Mandatory Start on 2027-02-01 — not among the contract dates
How to fix: Only dates the contract specifies may be constrained. Remove the rest and let the logic drive them, or submit them to the Contracting Officer for approval.
CAL-01Adverse weather accounted forSection 3.3.9Needs your judgement
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."
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.
SDEF-IDActivity ID must be numeric, max 10 digitsSection ER 1-1-11 App A, ACTV note (2)Needs your judgement
1 activity IDs are not valid for SDEF — the export will fail
"The Activity ID consists of a right-justified field of ten (I0) integers each. The maximum activity number allowed under this arrangement is 9999999999."
A1010 — Concrete Foundations [line 24]ID "A1010" is not numeric
Notes
ER 1-1-11 states this requirement plainly, but USACE's own sample project - the one distributed inside sdef.zip as the worked example of a compliant schedule - uses alphanumeric activity IDs throughout (CT01093, FW01070). The likeliest explanation is that the conversion utility renumbers activities when it writes the SDEF file, in which case your P6 IDs never reach it. This is reported so you can raise it, not as a failure: ask your Contracting Officer whether their converter renumbers before you renumber a live schedule, which is disruptive and hard to undo.
How to fix: SDEF requires a right-justified integer of up to ten digits. P6's default alphanumeric IDs such as A1010 or MOB-001 cannot be exported. Renumber the activities before attempting the RMS upload — this is invisible in P6 until the upload is rejected.
SDEF-DESCActivity description maximum 30 charactersSection ER 1-1-11 App A, ACTV note (3)Needs your judgement
1 activity descriptions exceed 30 characters and will be truncated on export
"The Activity Description must be a maximum of 30 characters. Descriptions must be limited to the space provided."
101058 characters
Notes
These are not refused - the converter simply cuts each description at 30 characters and the upload proceeds. What you lose is the end of the name: "Rough-in Fire Detection & Alarm System" reaches the Government as "Rough-in Fire Detection & Alar". Put the words that identify the work in the first 30 characters, as UFGS 3.12.j asks, so the reviewer can still tell your activities apart.
How to fix: SDEF allows 30 characters for the description. Shorten the names, keeping the distinguishing words at the front.
SUB-03File identifies its schedule type, contract number and data dateSection 3.5.1Needs your judgement
1 identification fields are missing from the file
"The electronic file is to identify the type of schedule (Preliminary, Initial, Update), full contract number, Data Date and schedule file name. Each schedule must have a unique file name and use project specific settings."
How to fix: Each file must identify the schedule type, the full contract number, the data date and a unique file name.
SDEF-05Modification Number (MODF) usageSection 3.3.7.4Needs your judgement
14 activities carry a Modification Number across 1 modifications
"Assign a Modification Number Code to any activity or sequence of activities added to the schedule as a result of a Contract Modification, when approved by Contracting Officer. Key all Code values to the Government's modification numbering system. An activity can have only one Modification Number Code."
Modification numbers in use
Modification
Activities
000000
14
Notes
Check that every value below matches an approved Government modification number. Activities added under a modification that is not yet approved should not carry a Modification Number.
How to fix: Define MODF in the activity code dictionary even when no modification has been issued yet. Key the values to the Government's own modification numbering, and apply them only to work added by an approved modification.
SDEF-06Phase of Work (PHAS) assignedSection 3.3.7.6Needs your judgement
14 activities have no PHAS code
"Assign Phase of Work Code to all activities. Examples of phase of work are design phase, procurement phase and construction phase. Each activity can have only one Phase of Work code."
The specification states this code is to be assigned to all activities, so this is a real requirement and not a suggestion. Whether it is enforced on milestones and administrative rows differs from project to project - check the requirements written into your own contract before deciding how far to take it. This is reported for your judgement, not as a rejection.
2 of the 14 are milestones, which carry no work of their own. Milestones are the rows most likely to be accepted without a PHAS code - look at the remaining work activities first.
How to fix: Assign a Phase of Work code to every activity - design, procurement, construction, and any separately defined performance period your contract names. The field is two columns and an activity may carry only one.
CAL-03Working days, weekends and holidaysSection 3.3.10Needs your judgement
18 observations about the working calendars
"Develop the default Calendar to match the physical work plan with non-work periods identified including weekends and holidays."
Working days by calendar
Calendar
Work week
Hours/day
Activities
Holidays set
Federal holidays not set
Standard 5 Day Workweek
Mon-Fri (5 days)
8
10
33
0
Standard 5 Day Field Work
Sun-Sat (7 days)
8
2
0
-
Site Work No Holidays
Mon-Fri (5 days)
8
2
0
16
Standard 5 Day Field WorkNamed as a 5-day calendar but the data works 7 days a week
Site Work No HolidaysNo holiday at all is marked non-working in this calendar
Site Work No Holidays2026-09-07 Labor Day — a working day in this calendar
Site Work No Holidays2026-10-12 Columbus Day — a working day in this calendar
Site Work No Holidays2026-11-11 Veterans Day — a working day in this calendar
Site Work No Holidays2026-11-26 Thanksgiving Day — a working day in this calendar
Site Work No Holidays2026-12-25 Christmas Day — a working day in this calendar
Site Work No Holidays2027-01-01 New Year's Day — a working day in this calendar
Site Work No Holidays2027-01-18 Birthday of Martin Luther King, Jr. — a working day in this calendar
Site Work No Holidays2027-02-15 Washington's Birthday — a working day in this calendar
Site Work No Holidays2027-05-31 Memorial Day — a working day in this calendar
Site Work No Holidays2027-06-18 Juneteenth National Independence Day — a working day in this calendar
and 6 more — see the attached CSV
Notes
Which holidays apply to your project is set by the contract, not by this tool. The eleven US federal holidays (5 U.S.C. 6103) are shown as a starting point — confirm the observed days with the Contracting Officer.
How to fix: Open each calendar in P6 and set its non-working days — weekends first, then every holiday the contract recognises. A holiday left as a working day quietly shortens every duration that crosses it, so the schedule promises dates the crew cannot meet.
P6-01Activity codes defined at project levelSection 3.12.aNeeds your judgement
6 activity codes are not defined at project level
"Ensure Primavera P6 settings provide a schedule capable of fulfilling the requirements of the contract. The following settings are mandatory and required in all schedule submissions to the Government: a. Activity Codes must be Project Level, not Global or EPS level."
AREAdefined at AS_Global instead of project level
BIDIdefined at AS_Global instead of project level
FOWdefined at AS_Global instead of project level
MODFdefined at AS_Global instead of project level
RESPdefined at AS_Global instead of project level
WRKPdefined at AS_Global instead of project level
Notes
Paragraph 3.12 calls these settings mandatory in all schedule submissions. They are P6 preferences that an exported file records only indirectly, so this is reported for your judgement rather than as a rejection — confirm the setting in P6 and against the requirements written into your contract.
How to fix: In P6, activity codes come in three scopes — Global, EPS and Project. 3.12.a requires Project. Re-create the eight SDEF codes as project-level codes and reassign the values, then re-export. Note this is the opposite of the older P3 guidance, which called for global codes.
P6-02Calendars defined at project levelSection 3.12.bNeeds your judgement
2 calendars in use are not project calendars
"b. Calendars must be Project Level, not Global or Resource level."
Standard 5 Day Field Workis a CA_Base calendar
Site Work No Holidaysis a CA_Base calendar
Notes
Paragraph 3.12 calls these settings mandatory in all schedule submissions. They are P6 preferences that an exported file records only indirectly, so this is reported for your judgement rather than as a rejection — confirm the setting in P6 and against the requirements written into your contract.
How to fix: Global and resource calendars travel badly between databases — the receiving system may not have them. Copy each one into the project as a project calendar and reassign the activities before exporting.
QCS-02Prime contractor responsibility code is PRIMSection QCS Manual 2.38 / Prime ContractorNeeds your judgement
The prime contractor code is not present
"Responsibility Code - This code must match the Contractor's scheduling package if one is being used. It must be PRIM and cannot be assigned to any other subcontractor for this contract. Be sure to advise your scheduler of the Prime Contractor responsibility code of PRIM."
Responsibility codes in use
Code
Activities
GC
14
Prime contractor codeNo activity uses "PRIM". Codes found: GC
Notes
Each subcontractor's responsibility code must also be unique - QCS will not let the same code stand for two different subcontractors on one contract.
How to fix: Code the prime contractor's own activities PRIM, and give every subcontractor its own distinct code. This requirement comes from QCS, not from the specification - UFGS 3.3.7.2 offers DOR, ELEC, MECH and GOVT as examples and never mentions PRIM - but QCS matches its Prime Contractor record to the schedule by that exact code. Confirm the convention with your Contracting Officer before renaming codes across a live schedule.
Checks we can run if you supply more data (4)
DUR-03Original duration changes require approvalSection 3.3.15More data needed
Requires two schedules — run with --previous
CHG-01Activities added, deleted, or renamed without approvalSection 3.3.14More data needed
Requires two schedules — run with --previous
CHG-02Artificially improving progressSection 3.9.1More data needed
Requires two schedules — run with --previous
PROG-02PActual dates rewritten between updatesSection 3.3.12More data needed
Requires two schedules — run with --previous
Checked and compliant (25)
DUR-05Curing and acceptance periodsSection 3.3.2 / 3.3.10Passed
No curing or acceptance period exceeds the duration cap
LOG-05End Project finish milestone and float behaviourSection 3.3.8.2Passed
The closing milestone is correct and float is consistent with the contract date
CAL-02Calendars developed and assigned appropriatelySection 3.3.10Passed
Calendar structure is sound (4 calendars)
Calendars and activity assignment
Calendar
Hours per day
Activities
Standard 5 Day Workweek
8
10
7 Day Government Acceptance
8
0
Standard 5 Day Field Work
8
2
Site Work No Holidays
8
2
How to fix: Calendars with no activities assigned: 7 Day Government Acceptance — either assign them or delete them. Whether each activity sits on the calendar it "logically belongs" to is your judgement. Review the distribution table and confirm it makes sense.
REL-05Lags not used to absorb or create floatSection 3.3.16Passed
No positive lags in the schedule
PROG-01Default progress data disallowedSection 3.3.12Passed
No phased completion was detected. If your contract specifies interim completion dates, each phase needs a "Start Phase X" milestone and an "End Phase X" milestone, and the interim date must be constrained.
0 activities started; percentages are internally consistent
Percent complete distribution
Percent complete
Activities
0
12
1-25
0
26-50
0
51-75
0
76-99
0
100
0
Notes
Whether each percentage is a realistic assessment of earned value cannot be determined from the file — an activity half built and reported at 100 percent looks identical to an honest one. Review the percentages against what is physically in place on site before submitting.
An activity may be declared 100 percent complete when only minor punch list work remains and it does not hold up its successors — but the budgeted cost must then be reduced by the amount needed to correct the deficiency, and that amount added to the closeout activity.
SUB-04Initial schedule submitted on time and covering the full contractSection 3.4.2Passed
Initial schedule timing and coverage are consistent with the contract data supplied
Notes
The data date shows when the schedule was calculated, not when it was submitted. If it was submitted on time with an earlier data date, this is not a finding.
P6-04Percent complete type is PhysicalSection 3.12.dPassed
Every activity uses Physical percent complete
Notes
Paragraph 3.12 calls these settings mandatory in all schedule submissions. They are P6 preferences that an exported file records only indirectly, so this is reported for your judgement rather than as a rejection — confirm the setting in P6 and against the requirements written into your contract.
P6-05Calendar work hours per day is 8.0Section 3.12.ePassed
Every calendar in use is set to 8.0 hours per day
Notes
Paragraph 3.12 calls these settings mandatory in all schedule submissions. They are P6 preferences that an exported file records only indirectly, so this is reported for your judgement rather than as a rejection — confirm the setting in P6 and against the requirements written into your contract.
P6-07All work calendars end the day at the same hourSection 3.12.kPassed
All work calendars end the day at 17:00
Could not be evaluated (3)
SUB-01Preliminary schedule scope and cost balanceSection 3.4.1Not evaluable
Applies only to a preliminary submission (you specified: initial)
SDEF-UNITUnit Cost Record viabilitySection 3.3.7 / ER 1-1-11 App ANot 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.cNot evaluable
This file does not record a duration type
Contract context (1)
QCS-01Actual dates must match the Daily QC ReportsSection ER 1-1-11 / QCS importContext
QCS refuses a schedule update whose actual start and finish dates disagree with the dates already entered in your Daily QC Reports. This check cannot be run here — those reports live in QCS, not in the schedule file — but it is one of the most common reasons an update is refused, and no paragraph of the specification warns you about it. Before submitting an update, reconcile the actual dates in the schedule against the Daily QC Reports. QCS will list every mismatch in a report called "Invalid Actual Starts/Finish Dates on Schedule"; if the QC Report itself is wrong, it has to be returned to you for correction before the schedule will import.
"When QCS is asked to import a schedule update it will check the SDEF file to ensure that the Scheduler has used the Actual Start and Actual Finish dates as were entered in the Daily QC Reports. If the dates do not match, QCS does not allow the updated schedule to be imported."
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.
This specification has 85 numbered requirements. 44 of them can be verified from a schedule file and were checked above. The remaining 41 cannot be — they are meetings to attend, documents that travel alongside the schedule, and decisions the contract reserves to the Contracting Officer. 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.
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 judgement 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 Contracting Officer. Confirm your cost loading — the punch list allowance, the as-built drawings and O&M manuals amounts, and the front-end weighting of early activities — with the Government 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.