How to build a credible construction baseline schedule: a review checklist
Once a baseline is accepted, every delay, claim and payment is measured against it. These are the questions to ask before you sign off, grouped the way the U.S. Government Accountability Office assesses schedules.
Updated 14 November 2026 · 7 min read
Comprehensive
- 1Capture all activities
- 3Assign resources to all activities
- 4Establish the duration of all activities
Well-constructed
- 2Sequence all activities
- 6Confirm the critical path is valid
- 7Ensure reasonable total float
Credible
- 5Trace the schedule horizontally and vertically
- 8Run a schedule risk analysis
Controlled
- 9Update using actual progress and logic
- 10Maintain a baseline schedule
Quick answer
A credible construction baseline schedule covers all the contract scope, links every activity with logic, uses durations based on quantities and productivity, has realistic calendars and contract milestones, shows a continuous critical path driven by logic rather than date constraints, has reasonable float, and documents its assumptions. Before accepting one, check each of these and send it back if the scope, logic, constraints or critical path fail.
Key takeaways
- Check scope first: missing activities are the most expensive error to find later.
- Every activity needs a predecessor and a successor; open ends hide delays.
- Date constraints and long lags are where unrealistic dates hide.
- A valid critical path runs continuously from start to finish through the logic.
- Write the assumptions down; they're what you'll argue about in a claim.
Why the baseline review matters
The baseline is the yardstick for the whole job: progress updates, delay analysis, payment and claims are all measured against it. GAO's Schedule Assessment Guide sets out ten best practices for reliable schedules, grouped as comprehensive, well-constructed, credible and controlled. The checklist below turns them into questions a project manager can ask of a construction baseline.
The review checklist
Work through it with the scheduler, ideally in the scheduling software rather than on a PDF, so you can check the logic behind each date.
0 of 14 checked
5 must-have items still open
Logic flaws that make a baseline look better than it is
Open end
An activity with no successor. If it slips, nothing downstream moves, so the slip never shows.
Hard constraint
A typed "must finish on" date overrides the logic and hides the real finish, sometimes as negative float.
Long lag
A 20-day lag is hidden work. Model curing, approvals or deliveries as activities so they can be statused.
Missing start logic
An activity that can start any time has huge float and drifts out of view until it's suddenly late.
Questions to ask the scheduler
- Which activities drive the completion date, and why those?
- Where do the durations come from: quantities and crew rates, or experience?
- Which dates are constrained, and is each one in the contract?
- What's in the calendars: work week, holidays, weather days?
- Which activities have the most float, and is that real or missing logic?
- What are the biggest risks to the milestones, and where's the contingency?
- How will it be updated, by whom, and from which field information?
Common reasons to send a baseline back
| Problem | Why it matters |
|---|---|
| Scope missing (procurement, submittals, inspections, owner work) | The real critical path may run through what's missing. |
| Activities without predecessors or successors | Slips can't travel to the milestones, so delays hide. |
| Many date constraints | Dates are typed, not calculated: the schedule can't forecast. |
| Long lags | Hidden work that can't be statused or managed. |
| Very long activities | Progress can't be measured reliably at each update. |
| Critical path broken or jumping | Nobody can say what drives completion. |
| Unexplained large or negative float | Missing logic, or a plan that already doesn't work. |
After it's accepted
Save it as the baseline and leave it alone. Update a copy with actual progress every period, and change the baseline only through an approved re-baseline. Then break the next few weeks into a detailed look-ahead the field can work from.
- 3WLA keeps baseline, monthly and 3-week schedules side by side for each project.
- The look-ahead is where field detail lives, so the baseline doesn't fill up with day-by-day tasks.
- On the Business plan, AI compares your look-ahead with the master schedule PDF so drift is spotted early.
Common questions
What makes a baseline schedule credible?
It covers all the scope, is linked by logic, uses realistic durations and calendars, shows a valid critical path and reasonable float, and documents its assumptions and risks.
Who should review the baseline?
The project manager and superintendent, with the scheduler, and the owner's representative if it's a contract submission. Trade partners should confirm their durations and sequences.
How long should activities be in a baseline?
Short enough to measure progress at each update. For construction work that usually means a few weeks at most; break longer work by area or phase.
Is a schedule risk analysis required?
Not on every job, but GAO counts it as a best practice: it shows how likely the key dates are and how much contingency the plan needs.
Run the field plan next to your baseline
Keep the baseline in your CPM tool and plan the next three weeks in 3WLA: detailed tasks, owners, constraints and progress, issued to every trade. Free for one project, with unlimited people.
Keep reading
- GuideBaseline vs progress vs look-ahead schedulesHow the baseline, the progress schedule and the 3-week look-ahead answer different questions: purpose, detail, ownership and update frequency compared.
- GuideHow to update a construction progress scheduleStatus date, actual starts and finishes, remaining durations and forecasts: how to update a construction schedule so delays show up early, not at the end.
- Comparison3WLA alongside Primavera P6 and Microsoft ProjectP6 and Microsoft Project run the master schedule; 3WLA runs the 3-week look-ahead beside it. What each is for and how to keep them in line.
Sources
- Schedule Assessment Guide: Best Practices for Project Schedules (GAO-16-89G)(opens in a new tab). U.S. Government Accountability Office, 2015.
