△
Schedule Cue
Task-specific guidance for ordinary duration, logic, and calendar issues.
Project 05
Build a Residential Construction Schedule
Build and gain approval for one resource-informed baseline residential construction schedule tied to the work breakdown structure, sequence logic, procurement, inspections, milestones, and contractual conditions, using approved project documents as the controlling information.
Field Cue System
These cues appear at the point of work. They identify scheduling, resource, milestone, and authority issues before they become missed dates, hidden delay, or an unusable baseline.
✋
Critical Schedule Cue
A missed contractual milestone, hidden delay, or false baseline is possible.
⛑
Field Coordination Cue
Practical resource, crew, and trade coordination affecting the schedule.
▤
Authority Alert
Permit, inspection, or authority review timing varies. Verify before assuming.
▧
Contract Instruction Cue
Follow the executed agreement's specific terms for milestones and notice.
▱
Documentation Cue
Recordkeeping, version-control, and traceability guidance for the schedule.
Job Overview
This project qualifies you to build and gain approval for a baseline residential construction schedule — the controlling time document that converts the approved work breakdown structure and sequence logic into estimated durations, calendar dates, milestones, resource checks, and a defensible critical path. The finished work product is one approved, version-controlled baseline schedule supported by a schedule narrative, a risk review, and a defined update procedure.
You will confirm the schedule purpose and calendars, import the approved WBS activities and sequence logic, estimate durations from production data rather than guesswork, enter fixed contractual dates and milestones, calculate the initial schedule, identify the critical path and float, check the schedule against inspections, procurement, and owner decisions, check resource demand for trade stacking and impossible crew loads, run a schedule-risk review, and obtain authorized approval of the frozen baseline.
This project depends directly on the work already completed in Project 01 through Project 04. The approved scope statement, the job file, the work breakdown structure, and the sequence logic chart are the controlling inputs here — this project does not redefine scope, invent a new WBS, or re-derive sequence logic. It converts approved logic into approved dates. Every later project in this book depends on the baseline produced here: the two-week lookahead in Project 06, the procurement plan in Project 07, trade coordination in Project 08, and every schedule status reviewed in coordination meetings, RFIs, changes, and closeout through the Chapter 20 capstone.
Skills You Will Demonstrate
- PM-025 — Estimate task durations.
- PM-026 — Assign start and finish dates.
- PM-027 — Build milestone dates.
- PM-028 — Schedule inspections.
- PM-029 — Identify float.
- PM-030 — Create a baseline project schedule.
Where This Skill Fits
The baseline schedule produced here is the time backbone of every remaining project-management document in this book. The two-week lookahead in Project 06 exists to convert this baseline into executable field commitments; it cannot function without an approved baseline behind it. The procurement plan in Project 07 calculates release dates backward from the installation dates fixed in this schedule. Trade coordination in Project 08 links handoff readiness to schedule activities created here. Job-cost reporting in Project 15 compares progress against this same baseline. The punch process in Project 14 and the final walkthrough in Project 19 both trace back to the milestone conditions defined here.
The discipline of separating the frozen original baseline from forecast dates — taught in this chapter — is the same discipline used later to preserve schedule history through delay, recovery, and approved changes without ever concealing or resetting a missed commitment.
Scope and Intended Use
This project covers:
- confirming schedule purpose, level of detail, reporting cycle, calendars, and contractual milestones before entering activities
- importing the approved WBS activities and sequence-logic relationships without altering their technical order
- estimating durations from quantity, production rate, crew size, subcontractor commitment, access, and complexity
- including submittal, review, fabrication, shipping, permit, inspection, curing, drying, and commissioning durations
- entering fixed external dates only where their authority is confirmed, and entering required milestones
- calculating the initial schedule, identifying critical path, near-critical paths, and float
- checking inspection, concealment, delivery, owner-decision, and resource logic for completeness
- leveling resources without destroying required milestones or concealing delay
- running a schedule-risk review and developing mitigation for the highest risks
- obtaining authorized approval, freezing the baseline, and defining the update and rebaseline rules
This project does not authorize the learner to:
- invent milestone dates, contractual deadlines, or production rates not supported by the executed agreement, approved estimate, subcontractor commitments, or field data
- remove required inspections, cure periods, safety controls, or approved design steps to compress the schedule
- reset the original baseline merely to hide delay or a missed commitment
- redesign the work breakdown structure or the sequence logic while building the schedule; both remain the controlling inputs from Project 03 and Project 04
Any conflict between the sequence logic, the estimate's duration assumptions, subcontractor proposals, and contractual milestones must be identified and resolved in writing before the baseline is approved.
Reference Conventions
Establish these references before duration estimating begins, and do not change them mid-document without a recorded revision.
| Term | Definition |
|---|---|
| Baseline schedule | The one current, approved version of the schedule all progress and forecast reporting is measured against |
| Calendar duration | The number of workdays an activity spans on the project calendar, including non-labor time such as curing or drying |
| Effort hours | The labor time required to perform an activity, independent of how many calendar days it spans |
| Critical path | The longest connected chain of activities in the schedule; a delay on this path delays the project finish date |
| Total float | The amount an activity can be delayed without delaying the project finish date |
| Free float | The amount an activity can be delayed without delaying the early start of its successor |
| Forecast date | The current expected date for an activity, which may differ from the baseline date and must state why |
Schedule Baseline Record
Before distributing the approved baseline schedule, record the baseline identification directly on the schedule-approval record:
Project name: ______ Project address: ______ Baseline number: ______ Revision: ______
Date approved: ____________ Approved by (name and role): ____________ Project manager: ____________
Prerequisites
- An approved scope baseline (Project 01), project job file (Project 02), work breakdown structure (Project 03), and sequence-logic chart (Project 04) for the residential project
- Access to the approved estimate, executed agreement, subcontractor and supplier proposals, and the Book 25 permit-and-inspection plan
- Identification of the person or role with authority to approve the schedule baseline before calculation begins
- Scheduling software or an approved template capable of calculating logic, critical path, float, and resource demand
- A defined confidentiality and document-distribution rule for subcontractor pricing and commitment information contained in the schedule
Common Field Fundamentals
Every schedule in this book, from this chapter's residential baseline to the Chapter 20 capstone project schedule, follows the same sequence: confirm purpose, import logic, estimate durations, fix milestones, calculate, check, level, assess risk, approve, freeze. Learning that sequence here, on one residential project, means every later schedule update and lookahead starts from a method you already trust.
CalendarsWorking days, holidays, shutdowns, seasonal restrictions, and weather allowances
DurationsEstimated from quantity, production rate, crew size, and confirmed commitments
MilestonesPermit, dry-in, rough inspections, utilities, substantial completion, handoff
Critical pathThe longest connected chain of activities controlling the finish date
FloatTotal and free float identified without assigning it exclusively to one trade
Resource checkTrade stacking, crew loads, and competing use of cranes, lifts, and access checked
Risk reviewLong-lead items, weather, inspections, utilities, and owner decisions assessed
Baseline approvalWritten approval, freeze, archive, and defined update and rebaseline rules
Duration, Logic, and Milestone Integrity
Every schedule activity must trace to an approved WBS work package and preserve the predecessor, successor, and lag relationships approved in the Project 04 sequence-logic chart. Do not create a new logic relationship while building the schedule; if the logic appears wrong or incomplete, return to Project 04 and revise the logic chart through its own approval process before continuing. A schedule that quietly changes logic to fit a desired finish date is not a baseline — it is an unrecorded redesign of the project sequence.
PM-025 – PM-030
Schedule Development / Planning Qualification
Residential Baseline Construction Schedule
A. Finished-Project Specification
Deliverable: one approved residential baseline construction schedule, containing complete WBS-linked activities and logic, working calendars, estimated durations with recorded sources, fixed dates with confirmed authority, required milestones, a calculated critical path with identified float, a checked resource demand, a documented schedule-risk review, a written narrative, and written approval with an assigned baseline number and date.
B. Schedule Document Schedule
| Section | Content | Source | Purpose |
|---|---|---|---|
| Purpose and detail level | Reporting cycle, calendar, and contractual milestones the schedule must support | Agreement, project management plan | Establishes what the schedule must be able to answer |
| Calendars | Standard workdays, holidays, shutdowns, seasonal restrictions, authorized overtime, weather allowances | Company policy, agreement, local conditions | Defines the working time base for every duration |
| Activities and logic | WBS-linked activities with predecessor, successor, and lag relationships | Project 03 WBS, Project 04 sequence-logic chart | Converts approved logic into a schedulable activity list |
| Durations | Estimated duration, source, and basis for every activity, including submittal, procurement, permit, and inspection time | Estimate, subcontractor proposals, field history | Establishes realistic time requirements rather than assumed ones |
| Fixed dates and milestones | Confirmed external dates and required project milestones | Agreement, permits, lender, owner selections | Anchors the schedule to contractual and regulatory commitments |
| Critical path and float | Calculated critical path, near-critical paths, total float, free float | Calculated from logic and durations | Identifies which activities control the finish date and which have flexibility |
| Resource check | Resource demand by trade, crew, and equipment; identified stacking and conflicts | WBS, subcontractor commitments, equipment plan | Confirms the schedule is executable, not only logically correct |
| Risk review | Schedule risks for long-lead items, weather, inspections, utilities, owner decisions, hidden conditions, with mitigation | Procurement plan, permit plan, field experience | Identifies where the baseline is most likely to slip and what will be done about it |
| Narrative | Explanation of calendars, milestones, critical path, major constraints, and risks | Prepared by the scheduler | Gives reviewers the reasoning behind the calculated dates |
| Approval and update rules | Written approval, baseline number and date, rules for actual dates, forecast, and rebaseline | Authorized approver | Freezes the baseline and defines how it will be maintained |
C. Information and Document Takeoff
- Source records: the approved WBS and dictionary, the approved sequence-logic chart, the estimate, the executed agreement, subcontractor and supplier proposals, and the Book 25 permit-and-inspection plan, sufficient to build every section of the document schedule above without inventing missing information.
- Comparison records: planned durations compared against contract requirements, estimate assumptions, and subcontractor proposals in Step 28, used to confirm the schedule is realistic rather than merely calculated.
- Approval record: written confirmation of the person or role authorized to approve the baseline schedule, obtained before calculation begins.
- Revision control: a baseline numbering and archive convention sufficient to distinguish the current approved baseline from every superseded draft and from later forecast updates.
D. Acceptance Standards
| Check | Standard |
|---|---|
| Activities and logic | Every activity traces to an approved WBS package; logic matches the approved sequence-logic chart without unrecorded changes |
| Durations | Every duration has a recorded source; effort hours, crew-days, and calendar duration are distinguished |
| Fixed dates | Every fixed date has confirmed contractual, regulatory, or lender authority; no arbitrary constraints |
| Milestones | Every required milestone entered with a measurable completion condition |
| Critical path and float | Critical path calculated and reviewed; total and free float identified without being assigned exclusively to one trade |
| Resource demand | Trade stacking, impossible crew loads, and shared-equipment conflicts identified and resolved |
| Risk review | Highest schedule risks identified with documented mitigation |
| Approval | Written approval obtained from the authorized party; baseline number and date assigned before distribution; original baseline preserved without overwriting |
E. Preparation — Confirm Purpose, Calendars, and Fixed Dates
- Confirm the schedule purpose, required level of detail, reporting cycle, calendar, and contractual milestones. Record these before entering activities.
- Import or enter the approved WBS activities and sequence relationships. Do not alter the technical order approved in Project 04.
- Create working calendars for standard workdays, holidays, shutdowns, seasonal restrictions, and authorized overtime. Base every calendar on company policy and the executed agreement.
- Identify weather-sensitive activities and define reasonable weather allowances or calendars. Record the basis for each allowance.
- Estimate each activity duration from quantity, production rate, crew size, subcontractor commitment, access, and complexity. Record the source of every estimate.
- Distinguish effort hours, crew-days, and calendar duration. Do not present labor hours as though they were calendar duration.
- Include mobilization, setup, layout, protection, cleanup, testing, inspection, and correction time. Add this time to the relevant activities rather than omitting it.
- Include submittal preparation, design review, owner review, resubmission, fabrication, shipping, and delivery durations. Coordinate these durations with the Project 07 procurement plan once it exists.
- Include permit review, utility coordination, special inspection, testing, curing, drying, and commissioning durations. Confirm each duration against the Book 25 permit-and-inspection plan.
- Identify fixed external dates and confirm their authority. Record the document or authority that establishes each fixed date.
- Do not use arbitrary date constraints merely to make the schedule appear compliant. Remove any constraint whose authority cannot be confirmed.
F. Milestones and Initial Calculation
- Enter required milestones for permit issuance, mobilization, foundation, dry-in, rough inspections, permanent utilities, substantial completion, final inspection, and handoff as applicable. State the measurable condition that defines each milestone.
- Enter owner-selection and allowance-decision milestones. Coordinate these dates with the process defined in the Project 01 scope statement.
- Enter long-lead release and required-on-site milestones. Use preliminary procurement information where the Project 07 plan is not yet complete.
- Calculate the initial schedule using approved logic. Do not calculate the schedule before Steps 3–11 are complete.
- Identify the critical path and near-critical paths. Record which activities control the finish date.
- Identify total float and free float without treating float as belonging exclusively to one trade. Record float for every activity, not only critical-path activities.
- Inspect negative float, open ends, excessive lags, missing predecessors, and date constraints. Correct each condition found before continuing.
G. Verification, Resource Check, and Risk Review
- Check that every inspection has predecessor completion and successor-release logic. Confirm no inspection is scheduled before its predecessor work is logically complete.
- Check that every concealed-work activity is linked to quality and inspection approval. Confirm no concealment activity precedes its required approval in the logic.
- Check that material delivery precedes installation with inspection and staging time. Add staging and inspection time to the relevant activities where missing.
- Check that owner decisions precede procurement and field need dates. Confirm each decision milestone allows adequate lead time.
- Check resource demand by trade, crew, and equipment, and work area. Record demand by period for comparison against available resources.
- Identify trade stacking, impossible crew loads, and competing use of cranes, lifts, scaffolds, or access. Record each conflict found.
- Level resources without destroying required milestones or concealing delay. Adjust non-critical activities within their float before adjusting milestone dates.
- Run a schedule-risk review for long-lead items, weather, inspections, utilities, owner decisions, and hidden conditions. Record each risk in the schedule-risk register.
- Develop mitigation for the highest schedule risks. Assign an owner and a response to each significant risk.
H. Review, Approve, and Freeze the Baseline
- Compare planned duration with contract requirements, estimate assumptions, and subcontractor proposals. Record any discrepancy found.
- Review the draft with owner, field lead, key trades, procurement, design team, and inspectors or utilities where coordination is appropriate. Distribute the draft far enough in advance for informed review.
- Record commitments and unresolved schedule assumptions. Preserve a record of every comment received and how it was addressed.
- Add schedule narrative explaining calendars, milestones, critical path, major constraints, and risks. Write the narrative in plain language a non-scheduler can follow.
- Obtain authorized approval of the baseline. Confirm the approval is from the person or role identified during Step 1 coordination.
- Freeze and archive the approved baseline without overwriting it. Assign the baseline number and date directly on the schedule-approval record.
- Distribute the baseline and define the update cutoff and reporting process. State the frequency and cutoff for progress updates.
- Create rules for actual dates, progress, remaining duration, forecast, recovery, and approved rebaseline. State the exact condition under which a rebaseline may occur and who must approve it.
- Link the schedule to the procurement, inspection, cost, and communication systems. Confirm the identifiers used here will be recognized by the Project 07, Project 15, Project 16, and Project 17 systems.
Common Schedule Inspection
Inspect every baseline schedule using the same checks regardless of project size or complexity.
- Logic check: confirm every activity traces to an approved WBS package and preserves the approved sequence-logic relationships without unrecorded changes.
- Duration check: confirm every duration has a recorded source and that effort hours, crew-days, and calendar duration are distinguished.
- Fixed-date check: confirm every fixed date has confirmed authority and that no arbitrary constraint remains in the schedule.
- Critical-path and float check: confirm the critical path has been calculated and reviewed, and that float is recorded without being assigned exclusively to one trade.
- Resource check: confirm trade stacking and impossible crew loads have been identified and resolved through leveling rather than milestone erosion.
- Approval check: confirm written approval was obtained from the authorized party and that the baseline number and date are recorded before distribution.
Complete the Baseline Schedule Inspection Checklist in the Inspection Checklist section below before beginning Project 06.
Image Placeholder
Image Placeholder
Image Placeholder
Image Placeholder
Image Placeholder
Image Placeholder
Failure Points and Troubleshooting
Cleanup
This project ends with the approved baseline schedule filed and distributed, not left as an open draft.
- Confirm the schedule-approval record is signed, dated, and filed with the project documents
- Confirm the schedule-risk register shows every identified risk with a recorded mitigation or accepted status
- Move every superseded draft to the archive location and confirm it is clearly marked as superseded
- Distribute the approved baseline to every stakeholder identified in the Project 01 stakeholder list
- Provide the approved baseline schedule, resource-demand check, and risk register to Project 06 for use in building the initial two-week lookahead
Field Terms
- Baseline Schedule
- The one current, approved version of the schedule all progress and forecast reporting is measured against.
- Calendar Duration
- The number of workdays an activity spans on the project calendar, including non-labor time such as curing or drying.
- Effort Hours
- The labor time required to perform an activity, independent of how many calendar days it spans.
- Critical Path
- The longest connected chain of activities in the schedule; a delay on this path delays the project finish date.
- Total Float
- The amount an activity can be delayed without delaying the project finish date.
- Free Float
- The amount an activity can be delayed without delaying the early start of its successor.
- Forecast Date
- The current expected date for an activity, which may differ from the baseline date and must state why.
- Resource Leveling
- Adjusting non-critical activities within their float to resolve trade stacking or impossible crew loads.
- Schedule-Risk Register
- A log of identified schedule risks with probability, impact, mitigation, owner, and status.
- Rebaseline
- A documented, approved replacement of the current baseline, used only for a recorded reason and never to conceal delay.
Skill Check
- Why must every schedule activity trace to an approved WBS work package rather than being entered independently?
- What is the difference between calendar duration and effort hours, and why must a schedule distinguish them?
- What must be confirmed before a fixed external date may be entered into the schedule, and why?
- What is the difference between total float and free float, and why should float not be treated as belonging exclusively to one trade?
- What two checks confirm that inspections and concealed work are correctly linked to their predecessor and successor activities?
- Why must the original baseline be preserved rather than overwritten when the schedule is updated with actual progress?
- What is a resource-demand check, and what condition does it catch that a purely logical schedule calculation would miss?
- What must a schedule-risk register record for each identified risk?
- Under what condition may a schedule be rebaselined, and what must never be the reason for a rebaseline?
- Why does this chapter require a written schedule narrative in addition to the calculated dates themselves?
Competency Rubric
| Competency | Independent Pass Standard | Not Demonstrated | With Assistance | Independently |
|---|---|---|---|---|
| PM-025 | Estimates every activity duration from a recorded quantity, production rate, crew size, subcontractor commitment, or field history, with the source documented | |||
| PM-026 | Assigns start and finish dates by calculating the schedule from approved logic and confirmed durations, without arbitrary date constraints | |||
| PM-027 | Builds required milestone dates for permit, dry-in, rough inspections, utilities, substantial completion, and handoff with measurable completion conditions | |||
| PM-028 | Schedules inspections with correct predecessor and successor logic linking them to the work they inspect and release | |||
| PM-029 | Identifies total float and free float for schedule activities and communicates float as a project resource rather than as belonging to one trade | |||
| PM-030 | Produces an approved, version-controlled baseline schedule with a checked resource demand, documented risk review, narrative, and preserved baseline record |
Mark one column per competency. Only Demonstrated Independently awards the competency; Demonstrated with Assistance authorizes additional supervised practice but does not complete the requirement.
Inspection Checklist — Baseline Schedule Inspection Checklist
| Item | Standard | Meets Standard (Y/N) | Correction (if any) |
|---|---|---|---|
| Activities and logic | Every activity traces to an approved WBS package; sequence logic preserved without unrecorded changes | ||
| Calendars | Workdays, holidays, shutdowns, seasonal restrictions, and weather allowances defined | ||
| Durations | Every duration has a recorded source; effort hours, crew-days, and calendar duration distinguished | ||
| Fixed dates | Every fixed date has confirmed authority; no arbitrary constraints remain | ||
| Milestones | Every required milestone entered with a measurable completion condition | ||
| Critical path and float | Critical path calculated and reviewed; float identified and not assigned exclusively to one trade | ||
| Inspection and concealment logic | Every inspection and concealment activity correctly linked to predecessor and successor work | ||
| Resource demand | Trade stacking and impossible crew loads identified and resolved through leveling | ||
| Risk review | Highest schedule risks identified with documented mitigation | ||
| Approval | Written approval by authorized party; baseline number and date assigned; original baseline preserved |
Schedule-risk register status: ____________ Open risks carried forward: ____________
Baseline schedule declared approved: ______ (Pass/Fail) Date: ____________ Project manager name: ____________
Performance Check
With the baseline schedule calculated and reviewed, review it against the Acceptance Standards table and confirm every activity traces to the approved WBS and preserves approved sequence logic, every duration has a recorded source, every fixed date has confirmed authority, every required milestone is entered with a measurable condition, the critical path and float have been calculated and reviewed, inspection and concealment logic is correctly linked, resource demand has been checked and leveled without eroding milestones, the highest schedule risks have documented mitigation, and written approval has been obtained from the authorized party with a baseline number and date assigned. Complete the Baseline Schedule Inspection Checklist and correct any failed item before beginning Project 06. If an item fails, identify whether the error occurred in logic import, duration estimating, fixed-date confirmation, milestone definition, critical-path calculation, resource checking, risk review, or approval before revising.
Project Closeout
You have completed the fifth project in the construction project management sequence: building and approving a residential construction schedule. This project required you to estimate task durations (PM-025), assign start and finish dates (PM-026), build milestone dates (PM-027), schedule inspections (PM-028), identify float (PM-029), and create a baseline project schedule (PM-030).
You now have an approved, version-controlled baseline schedule, a checked resource demand, a documented schedule-risk review, and defined update and rebaseline rules. That baseline carries directly into the next project: converting the master schedule into an executable two-week lookahead that confirms labor, material, and inspection readiness for the immediate work ahead.
File your approved baseline schedule, resource-demand check, and risk register where Project 06 can incorporate them into the initial two-week lookahead. Every later schedule update, lookahead, and status report in this book is measured against this exact baseline.