A master schedule is the single source of truth for when every scope item happens, who's responsible, what has to happen first, and what the critical path is. Built correctly, it exposes float, predicts conflicts weeks before they hit, and creates the documented baseline you need to support delay claims when the owner, architect, or a subcontractor blows a milestone.
This guide covers how to build a master schedule from first principles — work breakdown, sequencing, duration estimation, critical path identification, resource loading, and schedule maintenance — and how construction time tracking software feeds actual labor data back into the schedule to close the loop between planned and actual.
This guide explains how to build a master construction schedule from first principles. It covers work breakdown structure, dependencies, duration estimates, critical path, resource loading, procurement, schedule updates, and how GPS timesheets for contractors help connect field labor data to the schedule.
Master schedule = project-level schedule showing all major work activities, milestones, dependencies, and the critical path from Notice to Proceed to Substantial Completion.
Not the same as:
The master schedule sits at the top. It sets the framework. Everything else integrates under it.
Contractors using project management software for general contractors can keep schedule updates, field notes, jobsite photos, and team communication easier to reference throughout the project.
Before any dates, build the Work Breakdown Structure (WBS) — the complete list of scope items organized into a logical hierarchy.
WBS hierarchy for a commercial project:
Project ├── Phase 1: Site Work │ ├── Demolition │ ├── Earthwork / Grading │ ├── Underground Utilities │ └── Paving ├── Phase 2: Foundation │ ├── Excavation │ ├── Formwork │ ├── Rebar │ ├── Concrete Placement │ └── Waterproofing ├── Phase 3: Structure │ ├── Steel Erection │ ├── Metal Decking │ └── Concrete on Deck ├── Phase 4: Enclosure │ ├── Exterior Wall Framing │ ├── Roofing │ └── Exterior Glazing ├── Phase 5: MEP Rough-In │ ├── Mechanical Rough-In │ ├── Electrical Rough-In │ └── Plumbing Rough-In ├── Phase 6: Interior Build-Out │ ├── Interior Framing │ ├── Insulation │ ├── Drywall │ ├── Painting │ └── Flooring ├── Phase 7: MEP Trim-Out │ ├── Mechanical Trim │ ├── Electrical Trim │ └── Plumbing Trim ├── Phase 8: Finishes │ ├── Ceilings │ ├── Millwork / Casework │ └── Specialty Items └── Phase 9: Closeout ├── Punch List ├── Inspections / Certificate of Occupancy └── Owner Training / Commissioning The WBS becomes the activity list in your scheduling software. Every activity in the master schedule maps to a WBS element. No activity without a WBS parent — and no WBS element without activities.
Once all activities are listed, define the relationships between them. No schedule runs without correct logic.
Finish-to-Start (FS): Activity B can't start until Activity A is complete.
Start-to-Start (SS): Activity B can't start until Activity A starts.
Finish-to-Finish (FF): Activity B can't finish until Activity A finishes.
Lag: Deliberate time between two activities.
Lead (negative lag): Overlap between activities.
Duration estimation for each activity requires three inputs: scope quantity, production rate, and crew size.
Duration formula:
Duration (days) = Quantity / (Daily Production Rate × Crew Size) Example — framing 10,000 SF of metal stud interior partitions:
Where production rates come from:
Historical data from past projects is the most accurate source. A contractor whose construction time tracking app captures hours by cost code has actual production rate data — not RS Means estimates, not gut feel. GPS-verified construction time tracking records show exactly how many field hours it took to complete a given quantity of work on previous projects. That data becomes the production rate input for the next project's schedule.
Productivity factors that affect duration:
Build productivity factors into your durations, not as surprises after the fact.
A contractor using construction time tracking resources can review actual hours by project, worker, and cost code. This helps project managers understand how long similar work took on previous jobs.
The critical path is the longest path through the network of activities — the sequence of activities that determines the minimum project duration. Any delay on a critical path activity delays the project's end date by the same amount.
Float (total float): How many days an activity can be delayed before it affects the project end date. Activities on the critical path have zero float.
Critical path calculation: Every scheduling tool (Primavera P6, Microsoft Project, Procore, etc.) calculates the critical path automatically once activities, durations, and dependencies are entered.
Forward pass: Calculates Early Start (ES) and Early Finish (EF) for each activity, working forward from project start.
Backward pass: Calculates Late Start (LS) and Late Finish (LF) for each activity, working backward from project end.
Float = Late Start − Early Start (or Late Finish − Early Finish)
What to do with the critical path:
A schedule that doesn't account for resource constraints isn't a schedule — it's a wish list. Resource loading answers: do we have enough people, equipment, and money to execute this schedule as planned?
For each activity:
When the schedule is resource-loaded, you can see peak labor demand by week or month. If the schedule shows 35 carpenters needed in week 14 and you can only staff 20, the schedule must be adjusted — before week 14, not during it.
Construction crew time tracking connects resource planning to reality: When actual crew sizes and hours are tracked against the cost code matching each scheduled activity, the PM can compare planned vs. actual resource consumption in real time. An activity planned for 4 carpenters running 8 days that's showing only 2 carpenters on the construction time clock app is behind — visible before it becomes a schedule variance.
Same concept — list equipment needed per activity. A tower crane that's needed for steel erection and concrete pours simultaneously is a conflict to resolve in the schedule, not on the job site.
Load contract amounts against scheduled activities to produce a cash flow projection by period. See Construction Cash Flow Management for integrating schedule-based cash flow into financial management. The WIP report (Construction WIP Report) uses the schedule's percent complete as the basis for over/under billing analysis.
Contractors can use jobsite photos and daily progress tracking to support what happened on site, when it happened, and whether critical path work was delayed.
Every project has activities that can't start until something is purchased, fabricated, or delivered — and that fabrication or delivery takes months.
Common long-lead items:
Plot long-lead procurement as a parallel track in the master schedule. The procurement milestone (purchase order issued) must happen early enough that delivery lands before the field activity needs the material. Missing a long-lead delivery is one of the most common causes of critical path delays — and one that must be documented carefully for potential delay claims.
Teams that need better visibility into materials, deliveries, and field coordination can review this construction delivery tracking case study.
Gantt Chart: Horizontal bar chart showing activities against a calendar timeline. Best for owner communication and field team use. Most scheduling software outputs Gantt by default.
Precedence Diagram Method (PDM): Network diagram showing activities as nodes and dependencies as arrows. Best for understanding logic relationships and identifying critical path. Primavera P6 and MS Project use PDM logic under the hood.
Linear Schedule (Time-Distance): For repetitive linear work — road projects, pipeline, multi-story buildings with repeating floors. Shows location on one axis and time on the other.
For most commercial GCs: Gantt with underlying PDM logic, produced in Primavera P6, MS Project, or Procore Scheduling, is standard.
A schedule built at project start and never updated is a historical document, not a management tool. Schedules require regular updates.
Update frequency:
Update process:
Where construction timesheet app data feeds the update:
Hours logged by cost code in the contractor time tracking app map directly to scheduled activities. When the PM updates percent complete on an activity, they can compare planned hours (from the resource-loaded schedule) to actual hours (from the time tracking system). An activity that's 50% complete but has consumed 70% of its planned hours is running inefficient — the remaining duration estimate needs to increase. Catching this at the 50% mark is recoverable. Missing it until 90% is a schedule crisis.
Forensic scheduling: If a delay dispute arises, the schedule update history — combined with GPS-verified daily labor records from the construction time keeping app — creates a contemporaneous record of what happened and when. See Construction Project Delay for how to document and pursue delay claims.
Contractors comparing field documentation options can review the TaskTag vs CompanyCam comparison to see how construction teams can manage photos, communication, and documentation in one workflow.
When the schedule shows a late completion, two options exist: crash or fast-track.
Crashing: Add resources to critical path activities to shorten their duration.
Fast-tracking: Run activities in parallel that were planned sequentially.
What not to do: Remove logic from the schedule to make it look compliant when it isn't. A schedule with missing predecessors and unrealistic remaining durations satisfies no one — and creates liability when the project doesn't finish on time and the documented schedule showed on-time completion.
TaskTag helps contractors organize field photos, time records, daily reports, and project communication in one place. If your team wants better schedule visibility from the field, you can create a free contractor account or schedule a construction software demo.
Build stronger schedules with real jobsite data, photos, time records, and daily field updates.
With TaskTag, contractors can track progress from the field and keep project teams aligned from planning through closeout.
|
Tool |
Best For |
Notes |
|---|---|---|
|
Primavera P6 |
Large commercial/public projects |
Industry standard for large GCs, complex logic, resource loading |
|
Microsoft Project |
Mid-size commercial |
Widely used, integrates with Microsoft ecosystem |
|
Procore Scheduling |
GCs already on Procore |
Integrated with RFIs, submittals, daily reports |
|
Buildertrend |
Residential / smaller commercial |
User-friendly, lower learning curve |
|
Smartsheet |
Simpler projects, PM-focused teams |
Gantt + collaboration, not as powerful for critical path |
For most commercial GCs: Primavera P6 (large projects) or MS Project (mid-size) connected to Procore for field management is the standard stack.
Schedule build:
Schedule maintenance:
TaskTag Features
Related Blog Posts