structuraline

Reference

Every requirement we check.

One entry per rule, with the paragraph it comes from and the sentence it rests on. Generated from the rule set the engine runs, so this page cannot describe a check that no longer exists.

Specification  USACE UFGS 01 32 01.00 10 Project Schedule
Edition  August 2026  ·  Agency  USACE
Source  https://www.wbdg.org/FFC/DOD/UFGS/UFGS%2001%2032%2001.00%2010.pdf
Blocking — stated absolutelyYour judgement — the spec defers to a personContext — reported, never graded

Paragraph 2.1  ·  1 rule

2.1.2.1SW-01

P6 export version not newer than the Government's

Blocking

If Primavera P6 is selected for use, provide the "xer" export file in a version of P6 importable by the Government system. Verify at the SEKO meeting which version of P6 is in use by the Government. Export the schedule in a version of P6 no newer than that used by the Government.

Paragraph 3.2  ·  4 rules

3.2.1COST-01

No negative cost loading

Blocking

Activities with a negative cost loading is not allowed.
3.2.1COST-02

No front-end loading

Your judgement

Activity cost loading must be reasonable and without front-end loading.
3.2.2COST-06

Submittal activities carry no cost

Blocking

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.
3.2 / 3.3.7.5COST-08

Cost loading balances to the contract line items

Blocking

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.

Paragraph 3.3  ·  46 rules

3.3.2DUR-01

Activity duration ceiling

Blocking

Non-procurement activities Original Durations (OD) are not to exceed 20 workdays or 30 calendar days.
3.3.2DUR-04

Activity calendar-day span

Your judgement

Non-procurement activities Original Durations (OD) are not to exceed 20 workdays or 30 calendar days.
3.3.2 / 3.3.10DUR-05

Curing and acceptance periods

Your judgement

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.
3.3.3CONT-03

Design and permit activities present

Your judgement

Include design and permit activities with the necessary conferences and follow-up actions and design package submission dates.
3.3.4PROC-01

Procurement activities present

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.
3.3.5CONT-01

Mandatory activities present

Your judgement

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.
3.3.6CONT-02

Government activities shown

Your judgement

Show in schedule, Government and other agency activities that could impact progress. These activities include, but are not limited to approvals, acceptance, design reviews, environmental permit approvals by State regulators, inspections, utility tie-in, Government Furnished Equipment (GFE) and Notice to Proceed (NTP) for phasing requirements.
3.3.7SDEF-00

SDEF coding dictionary present

Blocking

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.
3.3.7.1SDEF-01

Workers Per Day (WRKP) assigned

Your judgement

Assign Workers per Day for all field construction or direct work activities, if directed by the Contracting Officer. Workers per day is based on the average number of workers expected each day to perform a task for the duration of that activity.
3.3.7 / ER 1-1-11 App ASDEF-EXP

SDEF export viability

Blocking

Use the activity coding structure defined in the Standard Data Exchange Format (SDEF) in ER 1-1-11. This exact structure is mandatory.
3.3.7 / ER 1-1-11 App ASDEF-UNIT

Unit Cost Record viability

Your judgement

The Unit Cost Record must follow all Precedence Records. There must be one Unit Cost Record for every activity that is not lump sum activity.
3.3.7.2SDEF-02

Responsible Party (RESP) assigned

Blocking

Assign responsibility code for all activities to the Prime Contractor, Subcontractor(s) or Government agency(ies) responsible for performing the activity.
3.3.7.3SDEF-04

Area of Work (AREA) assigned

Your judgement

Assign Work Area code to activities based upon the work area in which the activity occurs. Define work areas based on resource constraints or space constraints that would preclude a resource, such as a particular trade or craft work crew from working in more than one work area at a time due to restraints on resources or space. Activities cannot have more than one Work Area Code.
3.3.7.4SDEF-05

Modification Number (MODF) usage

Your judgement

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.
3.3.7.5SDEF-03

Bid Item (BIDI / CLIN) assigned

Blocking

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.
3.3.7.5SDEF-BIDI

Every BIDI value is a CLIN that exists in the contract

Blocking

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.
3.3.7.6SDEF-06

Phase of Work (PHAS) assigned

Your judgement

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.
3.3.7.7SDEF-07

Category of Work (CATW) assigned

Your judgement

Assign a Category of Work Code to all activities. Category of Work Codes include, but are not limited to design, design submittal, design reviews, review conferences, permits, construction submittal, procurement, fabrication, weather sensitive installation, non-weather sensitive installation, start-up, and testing activities. Each activity can have no more than one Category of Work Code.
3.3.7.8SDEF-08

Feature of Work (FOW) assigned

Your judgement

Assign the appropriate Feature of Work Code to all activities based on the Definable Feature of Work to which the activity belongs based on the approved QC plan. An activity can have only one Feature of Work Code.
3.3.8LOG-01

Artificial float constraints prohibited

Blocking

The use of artificial float constraints such as "zero free float" or "zero total float" are prohibited.
3.3.8LOG-02

Mandatory constraints that override logic prohibited

Blocking

Mandatory constraints that ignore or affect network logic are prohibited.
3.3.8LOG-03

No unauthorised constrained dates

Your judgement

No constrained dates are allowed in the schedule other than those specified herein.
3.3.8.1DATE-01

Project start not earlier than NTP

Blocking

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.
3.3.8.1LOG-04

NTP Acknowledged start milestone with Start On constraint

Blocking

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.
3.3.8.2LOG-05

End Project finish milestone and float behaviour

Blocking

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.
3.3.8.3 / 3.3.8.3.1 / 3.3.8.3.2MILE-PH

Phase milestones and interim completion dates

Your judgement

Constrain contractually specified interim completion dates to show negative float when the calculated late finish date of the last activity in that phase is later than the specified interim completion date. Use a start milestone as the first activity for a project phase. Call the start milestone "Start Phase X" where "X" refers to the phase of work. Use a finish milestone as the last activity for a project phase. Call the finish milestone "End Phase X" where "X" refers to the phase of work.
3.3.9CAL-01

Adverse weather accounted for

Your judgement

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.
3.3.10CAL-02

Calendars developed and assigned appropriately

Your judgement

Schedule activities on a Calendar to which the activity logically belongs. Develop calendars to accommodate any contract defined work period such as a 7-day calendar for Government Acceptance activities, concrete cure times, etc. Develop the default Calendar to match the physical work plan with non-work periods identified including weekends and holidays. Develop Seasonal Calendar(s) and assign to seasonally affected activities as applicable.
3.3.10CAL-03

Working days, weekends and holidays

Your judgement

Develop the default Calendar to match the physical work plan with non-work periods identified including weekends and holidays.
3.3.11REL-01

Only two open-ended activities

Blocking

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.
3.3.11REL-02

Required relationship types on every activity

Blocking

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.
3.3.12PROG-01

Default progress data disallowed

Blocking

Actual Start and Finish dates must not automatically update with default mechanisms included in the scheduling software. Updating of the percent complete and the remaining duration of any activity must be independent functions. Disable program features that calculate one of these parameters from the other.
3.3.12PROG-02P

Actual dates rewritten between updates

Your judgement

Actual Start and Finish dates must not automatically update with default mechanisms included in the scheduling software.

Runs only when a previous update is supplied.

3.3.13PROG-02

Out-of-sequence progress

Your judgement

Activities that have progressed before all preceding logic has been satisfied (Out-of-Sequence Progress) will be allowed only on a case-by-case basis subject to approval by the Contracting Officer.
3.3.14CHG-01

Activities added, deleted, or renamed without approval

Your judgement

Do not delete activities from the project schedule or add new activities to the schedule without approval from the Contracting Officer. Activity ID and description changes are considered new activities and cannot be changed without Contracting Officer approval.

Runs only when a previous update is supplied.

3.3.15DUR-03

Original duration changes require approval

Your judgement

Activity Original Durations (OD) must be reasonable to perform the work item. OD changes are prohibited unless justification is provided and approved by the Contracting Officer.

Runs only when a previous update is supplied.

3.3.16REL-03

Leads (negative lags) prohibited

Blocking

Leads (negative lags) are prohibited.
3.3.16REL-04

Start-to-Finish relationships prohibited

Blocking

Start to Finish (SF) relationships are prohibited.
3.3.16REL-05

Lags not used to absorb or create float

Your judgement

Lags must be reasonable as determined by the Government and not used in place of realistic original durations, must not be in place to artificially absorb or create float, or to replace proper schedule logic.
3.3.17CALC-01

Retained logic required, progress override prohibited

Blocking

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.
3.3.18PROG-03

Percent complete reflects earned value

Your judgement

Update the percent complete for each activity started, based on the realistic assessment of earned value. Activities which are complete but for remaining minor punch list work and which do not restrain the initiation of successor activities may be declared 100 percent complete to allow for proper schedule management.
3.3.19DUR-02

Remaining duration of unstarted activities

Blocking

The remaining duration for unstarted activities are not to be less than its original duration.
3.3.20COST-03

Punch list correction cost-loaded at 1 percent minimum

Blocking

Cost load the "Correction of punch list from Government pre-final inspection" activit[y][ies] not less than 1 percent of the present contract value.
3.3.20.1COST-04

As-built drawings cost loading floor

Blocking

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.
3.3.20.2COST-07

O&M manuals cost loading floor

Blocking

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.
3.3.21SCH-01

Early completion schedule must be fully resource loaded

Your judgement

No IPS indicating an Early Completion will be accepted without being fully resource-loaded (including crew sizes and hours) and the Government agreeing that the schedule is reasonable and achievable.

Paragraph 3.4  ·  2 rules

3.4.1SUB-01

Preliminary schedule scope and cost balance

Your judgement

Within 15 calendar days after the NTP is acknowledged, submit the Preliminary Project Schedule defining the planned operations detailed for the first 90 calendar days for approval. The approved Preliminary Project Schedule will be used for payment purposes not to exceed 90 calendar days after NTP. Completely cost load the Preliminary Project Schedule to balance the contract award CLINS shown on the Price Schedule.
3.4.2SUB-04

Initial schedule submitted on time and covering the full contract

Your judgement

Submit the Initial Project Schedule for approval within 42 calendar days after notice to proceed is issued. The schedule must demonstrate a reasonable and realistic sequence of activities which represent all work through the entire contract performance period.

Paragraph 3.5  ·  1 rule

3.5.1SUB-03

File identifies its schedule type, contract number and data date

Your judgement

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.

Paragraph 3.9  ·  1 rule

3.9.1CHG-02

Artificially improving progress

Your judgement

Artificially improving progress by means such as, but not limited to, revising the schedule logic, modifying, or adding constraints, shortening activity durations, or changing calendars in the project schedule is prohibited.

Runs only when a previous update is supplied.

Paragraph 3.12  ·  6 rules

3.12.aP6-01

Activity codes defined at project level

Your judgement

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.
3.12.bP6-02

Calendars defined at project level

Your judgement

b. Calendars must be Project Level, not Global or Resource level.
3.12.cP6-03

Activity duration type is Fixed Duration and Units

Your judgement

c. Activity Duration Types must be set to "Fixed Duration & Units".
3.12.dP6-04

Percent complete type is Physical

Your judgement

d. Percent Complete Types must be set to "Physical".
3.12.eP6-05

Calendar work hours per day is 8.0

Your judgement

e. Time Period Admin Preferences must remain the default "8.0 hr/day, 40 hr/week, 172 hr/month, 2000 hr/year". Set Calendar Work Hours/Day to 8.0 Hour days.
3.12.kP6-07

All work calendars end the day at the same hour

Your judgement

k. The daily ending hour for all work calendars must be the same.

Binding on the file, but not from this section  ·  5 rules

ER 1-1-11 / QCS importQCS-01

Actual dates must match the Daily QC Reports

Context

When QCS is asked to import an Activity 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.
QCS Manual 2.38 / Prime ContractorQCS-02

Prime contractor responsibility code is PRIM

Your judgement

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 P3 scheduler of the Prime Contractor responsibility code of PRIM.
ER 1-1-11 App A, ACTV note (6)SDEF-CSTR

Only ES and LF constraints survive SDEF export

Blocking

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.
ER 1-1-11 App A, ACTV note (3)SDEF-DESC

Activity description maximum 30 characters

Your judgement

The Activity Description must be a maximum of 30 characters. Descriptions must be limited to the space provided.
ER 1-1-11 App A, ACTV note (2)SDEF-ID

Activity ID must be numeric, max 10 digits

Your judgement

The Activity ID consists of a right-justified field of ten (I0) integers each. The maximum activity number allowed under this arrangement is 9999999999.

HomeCoverage