Every check a GC or federal prime must run before a project schedule baseline goes to the owner for approval. From CPM logic integrity through contract milestone alignment and scheduling spec compliance.
Why schedule baseline reviews fail, and what the approval process actually needs
A schedule baseline is not a Gantt chart. It’s a contractual document. Once the owner approves it, that schedule becomes the measure against which every delay claim, every change order time impact, and every liquidated damages calculation is evaluated. Getting the baseline wrong costs money, not in a “we could have been more efficient” way, but in a “the contractor lost a $2.1 million delay claim because the baseline schedule had a critical path logic error that voided the time impact analysis” way.
That outcome is more common than the construction industry admits. Owners approve schedules without running logic checks. Primes submit schedules that were built to look good in the baseline review meeting, not to survive the forensic schedule analysis that happens 18 months later when the project is delayed. By the time anyone looks closely, the baseline has been accepted, the project is 60 days behind, and the contractor is trying to prove a delay using a schedule that doesn’t hold up.
The checks on this list exist because most project schedule review meetings are not schedule reviews. They’re presentation meetings. The PM walks the owner through the schedule in a conference room, shows the critical path, confirms the milestones hit, and the owner signs off. Nobody runs a logic check. Nobody verifies that the baseline resource loading is consistent with the sub buyout. Nobody checks whether the schedule specs, the CDRL, the project controls requirements, the contract specification Section 01 32 16, are actually reflected in the schedule format and update cycle.
The 16 checks here are the items that actually get rejected during a government contracting officer’s baseline schedule review, and the items that kill delay claims in forensic analysis. Run this checklist before you submit the baseline. Not after the contracting officer returns it.
Who this checklist is for
- General contractors submitting project schedule baselines to owners and construction managers
- Prime contractors on federal projects complying with contract scheduling specifications (Section 01 32 16 or equivalent CDRLs)
- Project controls engineers responsible for baseline schedule preparation and submission
- Scheduling consultants reviewing contractor schedules before owner submission
- Project managers approving the baseline internally before it goes to the owner
If your project involves a time impact analysis for change orders or delays, this baseline checklist is also the starting point. A clean baseline is the foundation of any credible TIA.
The 16-point baseline review
The checklist covers 16 things every schedule baseline must pass before owner submission:
- Verify CPM logic is complete. No open ends except project start and finish. Every activity except the project start milestone must have at least one predecessor. Every activity except the project finish milestone must have at least one successor. Open-end activities (danglers) create a fragmented critical path that collapses under delay analysis. Run a “Relationships” check in P6 or MS Project; zero open ends is the standard.
- Confirm no lags on Finish-to-Start relationships without written justification. FS lags greater than 5 days are the most common schedule manipulation technique. They create artificial float and can mask critical path activities. Every FS lag above 5 days must be documented with a field-verifiable justification (cure time, procurement lead time, access restriction) that the owner can independently verify.
- Check that the critical path runs from project start to project finish. Run the critical path filter. The longest path should flow continuously from the project start milestone to the project finish milestone without breaks. A “floating” critical path, one that terminates before the finish milestone, means the schedule has a logic gap that will distort every time impact analysis downstream.
- Validate that all contract milestones appear as activities with matching dates. Pull every milestone from the contract, substantial completion, phased occupancy, system commissioning, interim deliverables, and verify each appears in the schedule as a milestone activity with a constrained or calculated date that matches the contract. Missing milestones don’t show up in baseline reviews; they show up in delay claims.
- Confirm schedule data date matches contract notice-to-proceed date. The baseline data date (status date) must equal the contract NTP date. A data date that precedes or follows the NTP date creates artificial early-start offsets that inflate float on near-critical-path work. Federal contracting officers catch this immediately.
- Verify activity durations are consistent with the project scope and crew sizes. A 3-day duration for “Install 400 LF of 8-inch underground mechanical” on a single-crew project is not credible. Cross-check durations against the quantity takeoff and the sub buyout. Activities with unrealistically short durations create artificial float that disappears the moment the field starts.
- Confirm resource loading matches sub buyout and manpower plan. If the schedule is resource-loaded (required on many federal projects and increasingly on private CM-at-risk projects), resource histograms must be consistent with the subcontract values and the project’s manpower plan. A resource-loaded schedule where the labor histogram shows 400 workers peak but the site logistics plan supports 200 will be rejected.
- Check that the schedule update cycle and submittal format match the spec. Pull the scheduling specification (typically Section 01 32 16 or the applicable CDRL) and verify the schedule format, update cycle, narrative report requirements, and submittal package components match what the spec requires. A schedule submitted in XER format when the CDRL requires P6 native plus a PDF and a schedule narrative is a non-conforming submission.
- Verify all owner-furnished equipment and long-lead items appear in the schedule. Every OFE item and long-lead procurement item must appear in the schedule with a delivery activity. Delivery activities need logical connections to the installation activities they feed. Missing OFE activities is one of the most common baseline gaps.
- Confirm weather contingency days are included and documented. For outdoor work in climates with seasonal weather, the baseline should include weather contingency days consistent with the NOAA historical weather data for the project location and duration. A schedule with zero weather contingency for 12 months of outdoor work in Minnesota will not survive a delay claim.
- Check that the schedule is free of hard constraints on intermediate activities. Hard constraints (Must Start On, Must Finish On, As Late As Possible) on activities other than project milestones suppress float calculation and create artificial critical paths. Run a constraint report; only contract milestones and regulatory milestones with fixed dates should carry hard constraints.
- Verify that subcontractor-furnished schedules are integrated into the baseline. On projects with major subcontractors, each sub’s work plan must be logically integrated into the prime’s schedule, not floating as a separate sub-schedule outside the logic network. Sub-schedule fragments that aren’t integrated can’t be used to support delay claims or time impact analyses.
- Confirm closeout and commissioning activities appear in sufficient detail. Closeout, startup, commissioning, testing, punch-list, and owner training activities are consistently underrepresented in construction schedule baselines. A government agency or CM-at-risk owner with a phased occupancy requirement needs to see each system’s commissioning sequence. Underrepresented closeout surfaces in the last 10% of every project.
- Check that the critical path narrative matches the schedule logic. The baseline submission typically includes a schedule narrative describing the critical path, major phase transitions, and key milestone sequences. Run the critical path filter and compare what the schedule says is critical against what the narrative says. If they don’t match, the narrative was written before the schedule was finalized. An easily caught error that undermines the submission’s credibility.
- Verify the schedule file name, version number, and revision history match the submittal log. When the owner’s delay expert is pulling schedule revisions 2 years into a project and the file naming doesn’t allow them to reconstruct the revision history, credibility suffers. Establish the naming convention at baseline and maintain it through every update.
- Confirm the baseline is submitted within the contract-required timeframe. Most construction contracts require the baseline schedule to be submitted within 30, 45, or 60 days of NTP. Federal contracts often require it within 30 days with a 60-day approval cycle. Late submission of the baseline is itself a contract compliance finding and can affect the contractor’s ability to claim delay damages for early-project events.
How to run the review before submission
Run this checklist once internally before the baseline is submitted to the owner, and once after the owner’s review comments come back to verify every comment was addressed:
- Mark
- Pass, Fail, or
- N/A (with justification for N/A) for each item.
- Any Fail item gets an owner, a correction, and a date. Do not submit the baseline while Fails are open. A submitted baseline with known defects waives your ability to argue those defects after acceptance.
- Attach the completed checklist to the submittal package. Owners who run forensic schedule analysis later will want to see evidence the prime ran a pre-submission review.
- After owner approval, archive the baseline schedule file, the checklist, and the owner’s written approval together. These three documents are the foundation of every future time impact analysis on this project.
Stop managing baseline approvals through email chains
The 16 checks above take a project controls engineer 2–3 hours on a well-organized schedule. On a disorganized one, it’s a day. Multiply by 8 active projects with staggered baseline submission windows and you’ve got a planning bottleneck that delays submittals. Contracts Connected’s approval workflows module routes the baseline checklist review through a structured approval chain, PM review, PE sign-off, internal approval, then owner submission, with version control built in so the baseline file and its approval are always in the same place.
For educational purposes. These templates, checklists, and trackers are operator-built starting points designed to help you move faster on the kind of work that usually drowns construction admins in email chains. They are not legal, insurance, accounting, or tax advice. Each project, jurisdiction, and contract has its own quirks. Review the document, refine the language, and consult your attorney, broker, CPA, or compliance officer before relying on it for a live project decision.
Frequently asked questions about schedule baseline approval
What’s the difference between a baseline schedule and a project schedule?
The baseline schedule is the approved as-planned schedule. The plan of record at project start, or at the time of a re-baseline after a major scope change. The project schedule is the current working schedule updated with progress. Once approved, the baseline typically stays fixed (or is formally revised with owner concurrence) and serves as the comparator for delay analysis. Project schedules are updated weekly or biweekly against the baseline.
When does a project schedule need to be re-baselined?
When cumulative scope changes or owner-directed changes materially alter the project duration or sequence, the parties often agree to re-baseline. Federal contracts typically require a change in contract duration of more than 10% or 60 days (whichever is less) before a formal re-baseline is required. Private contracts are more variable, the contract language controls. A re-baselined schedule should go through the same 16-check process as the original baseline.
What scheduling software outputs are typically required for federal projects?
Most federal construction contracts specify the scheduling software format in the CDRL or scheduling specification. Common requirements: P6 XER file, a PDF of the Gantt chart, a PDF or Excel schedule narrative, and sometimes a P6 global project XML. DoD and Corps of Engineers projects often require P6-compatible files specifically. Verify the CDRL before building the schedule in a tool that can’t export the required format.
How detailed does the baseline schedule need to be?
Activity detail is typically driven by the contract specification. Federal scheduling specs often require activities no longer than 20 working days (the 20-day rule) with exceptions for long-lead procurement activities. Some private CM-at-risk contracts require 10-day maximum activity durations. Beyond contract requirements, the practical standard is: activities should be detailed enough that the PM can measure progress without guessing.
What is a time impact analysis and how does the baseline affect it?
A time impact analysis (TIA) is the methodology used to calculate the schedule impact of a change or delay event. It compares the schedule before the event against the schedule after the event is modeled in. A baseline with logic errors, missing milestones, or unsupported lags will fail TIA scrutiny. The opposing party’s scheduling expert will challenge the baseline as unreliable, and the TIA built on it is vulnerable. A clean baseline is your best insurance.
Can this checklist be used for design-phase schedules?
The checklist is written for construction phase baselines, but most items apply to design-phase CPM schedules with minor adaptation. Replace construction milestones with design milestones (design development submittal, owner review cycles, permitting). Replace subcontractor integration with design consultant integration. Items 11 and 12 (hard constraints and sub integration) are especially important on design-phase schedules where owners routinely impose fixed milestone dates that suppress float.