How to Build a Project Schedule, Step by Step

Welcome

Hello, and welcome. This is Super Structures General Contractors — a national general contractor headquartered in Powhatan, Virginia — here to help you and your clients build something that lasts. We're glad you're with us, and we look forward to connecting with you.

Here's one that matters more than its name lets on — How to Build a Project Schedule, Step by Step. If you remember one thing, make it this: A real schedule is built in a fixed order — scope, activities, logic, durations, calendars, critical path, baseline — and then kept alive with a disciplined monthly update. Do this right and the schedule becomes a tool the whole team believes.

The scheduling course covered the concepts: CPM, float, the critical path, the Last Planner System. This lesson is the procedure for actually producing a baseline schedule and keeping it current.

Step 1 — Define the scope and milestones

Read the contract: notice to proceed, substantial completion, interim milestones, liquidated damages, owner-furnished items, phasing, and any constraints (hours, seasons, occupied areas). List the milestones first.

Step 2 — Build the work breakdown structure (WBS)

Break the project into areas or phases (site, foundations, structure, enclosure, interiors by floor, MEP, site finishes, closeout) and then into activities — each one a piece of work with a clear start and finish, usually 3 to 20 working days long. Include procurement activities (submittal, approval, fabrication, delivery) for long-lead items, inspections, and owner decisions.

Step 3 — Sequence with logic

Link activities with predecessors and successors: finish-to-start is the default; use start-to-start with lags for overlapping work (drywall following framing floor by floor). Every activity except the first and last needs at least one predecessor and one successor — no open ends. Avoid hard-coded constraint dates; let logic drive dates.

Step 4 — Assign durations

Base durations on quantities and production rates — 12,000 square feet of drywall at a crew rate gives you days, not a guess — and confirm them with the subs who'll do the work. Use working days on a project calendar with holidays and, where relevant, weather days.

Step 5 — Calculate and review the critical path

Run the schedule. Check: does the end date meet the contract? Is the critical path believable (it should run through the real drivers — structure, enclosure, MEP, finishes, commissioning)? Are there activities with enormous float that suggest missing logic? Fix the logic before you compress durations.

Step 6 — Add resources and cost (as needed)

Load crews or labor hours to see manpower peaks; load cost to the schedule of values if the contract requires a cost-loaded schedule.

Step 7 — Baseline and distribute

Review with the super and key subs, get the owner's acceptance if the contract requires, and save the baseline. Issue it with a narrative: assumptions, the critical path, and the risks.

Step 8 — Update monthly, plan weekly

Each month: record actual start and finish dates and remaining durations, re-run, compare to the baseline, and write a short narrative of what moved and why. Each week: the three-week lookahead derived from the schedule. Never overwrite the baseline; keep every update as its own file — it's your delay record.

Going Deeper (Intermediate)

Tools by scale: Microsoft Project and Smartsheet for straightforward commercial jobs; Oracle Primavera P6 as the standard for large, public, and owner-specified schedules; Phoenix Project Manager and Asta Powerproject as contractor-friendly CPM tools; Procore Scheduling, Buildertrend, and Autodesk Build for integrated, simpler schedules; Touchplan or LeanTaker-style tools for pull planning and lookaheads. Many owner specifications require P6 and a specific format for updates — read Division 01.

Advanced / Pro-Level

Pros run a schedule health check before issuing: no open ends, few constraints, no negative float, reasonable activity durations, a logic-driven critical path, and no excessive leads or lags. They keep a time-impact analysis method ready: when a delay hits, insert a fragnet for the event into the current update and measure the shift — that is how a time extension gets granted. They build procurement and submittal logic into the schedule, so a late approval shows up as a schedule impact and not a surprise.

Practice Challenge

Your baseline shows the elevator installation on the critical path with a 14-week delivery. The elevator submittal was approved three weeks late. What do you do in the next update? (Answer: record the actual approval date, let the logic push fabrication and delivery, confirm the new completion date, run a time-impact comparison against the baseline, and issue the update with a narrative and written notice if the delay is owner- or designer-caused; then look at re-sequencing — can finishes near the shaft proceed, can an alternate hoist be used — to recover.)

In Practice

A PM who builds the schedule from quantities and sub input, then updates it monthly, has a critical path the owner believes and a record that wins time extensions. A PM who draws bars to hit the end date has a pretty picture nobody uses.

Common Mistakes to Avoid

• Durations guessed instead of derived from quantities and rates
• Open ends and date constraints that hide the real critical path
• Leaving out procurement, inspections, and owner decisions
• Overwriting the baseline instead of saving monthly updates

Takeaway: A real schedule is built in a fixed order — scope, activities, logic, durations, calendars, critical path, baseline — and then kept alive with a disciplined monthly update.

Educational content. Software products, features, ownership, and pricing change often — verify current details with each vendor before you buy. Product names are the trademarks of their owners; no endorsement is implied.