△
Sequencing Cue
Task-specific guidance for ordinary activity ordering and logic issues.
Project 04
Sequence Residential Construction Activities
Create a logic-driven residential construction sequence showing predecessor, successor, handoff, inspection, cure, procurement, access, and weather relationships before calendar dates are assigned, using the approved work breakdown structure as the complete activity source.
Field Cue System
These cues appear at the point of work. They identify sequencing, logic, inspection, and schedule-integrity issues before they become unsafe overlaps, rework, or missed inspections.
✋
Critical Logic Cue
An unsafe overlap, concealment before inspection, or broken dependency is possible.
⛑
Field Coordination Cue
Practical trade, access, and crew coordination affecting sequence logic.
▤
Authority Alert
Permit, code, or inspection sequencing requirements vary. Verify before assuming.
▧
Procurement Logic Cue
Long-lead, fabrication, and delivery logic that must be modeled before dates are assigned.
▱
Documentation Cue
Recordkeeping, version-control, and traceability guidance for the logic chart.
Job Overview
This project qualifies you to build the sequencing logic that governs a residential construction project before any calendar date is assigned. The finished work product is one approved, version-controlled construction sequence logic chart that orders every activity in the approved work breakdown structure by physical construction logic, permit and inspection requirements, procurement and long-lead relationships, safety and quality-hold conditions, access and trade-stacking constraints, and cure or drying durations.
You will convert the approved WBS into measurable schedule activities, order preconstruction through closeout work by its true technical dependencies, identify concealment and inspection relationships that must remain visible, identify long-lead and owner-decision logic, identify parallel work opportunities and unsafe overlaps, assign predecessor-successor relationships, and test the resulting logic against a delayed inspection, a late material, and an owner-selection delay before it is approved.
This project uses the WBS from Project 03 as its only activity source. It produces the sequencing logic that Project 05 converts into a dated baseline schedule, that Project 06 converts into an executable two-week lookahead, and that Project 07 uses to calculate procurement release dates. A schedule built without this sequencing discipline is not a working schedule — it is a set of dates without logic behind them.
Skills You Will Demonstrate
- PM-019 — Identify predecessor tasks.
- PM-020 — Identify dependent tasks.
- PM-021 — Order site work.
- PM-022 — Order structural work.
- PM-023 — Order mechanical and finish work.
- PM-024 — Create a sequencing logic chart.
Where This Skill Fits
The scope baseline from Project 01, the job file from Project 02, and the work breakdown structure from Project 03 are the controlling inputs to this project. This project does not create new deliverables and does not revise the WBS; it orders the deliverables the WBS already defines.
The sequence logic produced here becomes the backbone of the Project 05 baseline schedule. Every duration, resource assignment, and milestone date in Project 05 is applied on top of the logic established here. The two-week lookahead in Project 06 draws its readiness checks directly from the predecessor conditions defined in this project, and the procurement plan in Project 07 calculates backward release dates from the installation logic established here.
Scope and Intended Use
This project covers:
- converting every lowest-level WBS work package into one or more measurable schedule activities with defined start and finish conditions
- ordering preconstruction, mobilization, sitework, and foundation work according to approved plans and required inspections
- ordering structural, dry-in, and envelope work according to cure, bracing, and weather-tight requirements
- ordering MEP rough-in, insulation, and pre-drywall work according to inspection and concealment requirements
- ordering finish, exterior, and closeout work according to protection, access, and owner-decision requirements
- identifying long-lead, submittal, fabrication, and delivery logic for procurement-dependent activities
- identifying parallel work opportunities, unsafe overlaps, and trade-stacking or access conflicts
- assigning predecessor-successor relationships and testing the sequence against foreseeable delay
This project does not authorize the learner to:
- assign calendar dates, durations, or resource loading; those are established in Project 05 on top of the logic produced here
- remove a required inspection, cure period, safety control, or approved design step to shorten the apparent sequence
- invent a technical dependency that is not supported by the approved drawings, specifications, code, manufacturer instructions, or field condition
- reorder or merge WBS work packages; the sequence must use the WBS exactly as approved in Project 03
Any technical logic that cannot be supported by an approved document, code requirement, manufacturer instruction, or verified field condition must be flagged as an assumption and confirmed before the sequence is approved.
Reference Conventions
Establish these references before sequencing begins, and do not change them mid-document without a recorded revision.
| Term | Definition |
|---|---|
| Predecessor | An activity that must reach its defined finish condition, in whole or in part, before a dependent activity may begin |
| Successor | An activity that depends on a predecessor reaching its defined finish condition before it may begin |
| Finish-to-start relationship | The successor may not begin until the predecessor's defined finish condition is met |
| Start-to-start relationship | The successor may not begin until the predecessor has begun, without requiring the predecessor's finish |
| Finish-to-finish relationship | The successor may not finish until the predecessor finishes |
| Lag | A required waiting period between a predecessor's finish condition and a successor's start, representing a real technical condition such as cure or drying time |
| Weather-tight milestone | The defined point at which the building envelope is sufficiently enclosed to permit interior work to begin, stated by exact conditions rather than by date |
Sequence Logic Baseline Record
Before distributing the approved logic chart, record the baseline identification directly on the sequence-approval record:
Project name: ______ WBS baseline reference: ______ Logic baseline number: ______ Revision: ______
Date approved: ____________ Approved by (name and role): ____________ Project manager: ____________
Prerequisites
- An approved and frozen WBS baseline from Project 03, including the WBS dictionary
- Access to the approved drawings, specifications, permit and inspection plan, and long-lead item list
- Manufacturer instructions for any product whose cure, dry, or acclimation time affects sequence logic
- An activity-conversion worksheet, predecessor-successor relationship log, and sequence-test record ready for use
- Identification of the field supervision, key trades, and other parties required to walk and test the draft logic
Common Field Fundamentals
Every sequence logic chart in this book, from this chapter's residential sequence to the Chapter 20 capstone project, follows the same discipline: convert, order, relate, test, approve. Sequence logic always precedes calendar dates, and it is never adjusted merely to make a schedule appear shorter.
Activity conversionEvery WBS work package becomes one or more measurable activities with defined start and finish conditions
Physical logicSitework through closeout ordered by cure, bracing, drying, and structural requirements
Regulatory logicPermit, inspection, and concealment relationships that keep work exposed until approved
Procurement logicSubmittal, fabrication, shipping, and delivery relationships for long-lead and owner-selected items
Access and safety logicParallel work identified; unsafe overlaps and trade stacking avoided
Relationship assignmentFinish-to-start, start-to-start, and finish-to-finish relationships with justified lags only
Logic testingThe draft sequence tested against a delayed inspection, a late material, and an owner-selection delay
Baseline approvalWritten approval, baseline number, date, and version control before Project 05 begins
Concealment, Inspection, and the Weather-Tight Milestone
Work that will be concealed by a later trade — framing before drywall, rough plumbing before wall closure, waterproofing before backfill — must remain in the logic chart as visible until the governing inspection or internal quality check is recorded as passed. Do not model a concealment activity as complete merely because the trade reports the work finished; completion for sequencing purposes means the hold point has been satisfied.
PM-019 – PM-024
Sequencing / Planning Qualification
Residential Construction Sequence Logic Chart
A. Finished-Project Specification
Deliverable: one approved residential construction sequence logic chart, converting every lowest-level WBS work package into a measurable activity with a defined start and finish condition, ordered by physical, regulatory, procurement, safety, quality, access, cure, and trade-handoff requirements, with assigned predecessor-successor relationships, tested against foreseeable delay, and approved and versioned before the Project 05 baseline schedule is built.
B. Logic Chart Document Schedule
| Section | Content | Source | Purpose |
|---|---|---|---|
| Activity list | Every WBS work package converted into one or more measurable activities with start/finish conditions | Approved WBS and dictionary | Establishes the complete and only set of activities to be sequenced |
| Preconstruction logic | Permits, design approvals, selections, submittals, contracts, insurance, utility coordination | Agreement, permit plan, procurement list | Orders mandatory conditions that must precede mobilization |
| Sitework and foundation logic | Clearing, excavation, utilities, drainage, footing, foundation, waterproofing, backfill, slab | Drawings, specifications, permit plan | Orders work by cure, inspection, and structural requirements |
| Structural and dry-in logic | Floor, wall, roof, bracing, sheathing, roofing, windows, doors, WRB, siding | Drawings, specifications, manufacturer instructions | Orders structural and envelope work through the weather-tight milestone |
| MEP and preclosure logic | Plumbing, electrical, HVAC, gas, fire, low-voltage rough-in; insulation, air sealing, pre-drywall inspection | Drawings, specifications, permit plan | Orders concealment-sensitive work through required inspections |
| Finish and exterior logic | Drywall, cabinets, trim, flooring, paint, fixtures, exterior flatwork, landscaping, utility completion | Drawings, specifications, owner selections | Orders finish work by protection, access, and weather dependency |
| Procurement logic | Design, submittal, fabrication, shipping, delivery, installation logic for long-lead items | Long-lead item list, procurement register | Models material availability as a real dependency |
| Access and parallel-work logic | Access conflicts, shared equipment, trade-exclusion zones, safe parallel work paths | Site logistics plan, trade scopes | Prevents unsafe overlap and unmanaged trade stacking |
| Relationship assignment | Finish-to-start, start-to-start, finish-to-finish relationships, and justified lags | Field input, manufacturer cure/dry data | Defines exactly how activities constrain one another |
| Logic test record | Results of testing the sequence against delayed inspection, late material, and owner-selection delay | Draft logic chart, field review | Confirms the logic preserves safe alternate work paths |
C. Information and Document Takeoff
- Source records: the approved WBS and dictionary, approved drawings and specifications, permit and inspection plan, and long-lead item list, sufficient to convert and order every activity without inventing a missing dependency.
- Comparison records: the site logistics plan and trade scope information, used in Steps 25–27 to identify access conflicts and safe parallel-work paths.
- Manufacturer records: cure, dry, and acclimation instructions for any product whose installation sequence is not otherwise defined by code or approved drawings.
- Revision control: a baseline numbering and archive convention sufficient to distinguish the current approved logic chart from every superseded draft.
D. Acceptance Standards
| Check | Standard |
|---|---|
| Activity conversion | Every lowest-level WBS work package appears as at least one activity with a defined, observable start and finish condition |
| Physical logic | Sitework through closeout ordered according to approved drawings, cure, and structural requirements; no invented dependency |
| Regulatory logic | Concealment-sensitive activities remain open until the governing inspection or quality hold point is satisfied |
| Procurement logic | Long-lead and owner-selected items modeled with full submittal-to-delivery logic as predecessors to installation |
| Access and safety logic | Parallel-work activities confirmed free of unsafe overlap, access conflict, or unmanaged trade stacking |
| Relationship assignment | Every dependency stated as finish-to-start, start-to-start, or finish-to-finish, with lags justified by a real technical condition |
| Testing | Sequence tested against one delayed inspection, one late material, and one owner-selection delay, with results recorded |
| Approval | Written approval obtained; baseline number and date assigned before distribution and before Project 05 begins |
E. Preparation — Convert the WBS and Identify Preconstruction Logic
- Use the approved WBS as the complete activity source. Do not add, remove, merge, or reorder WBS work packages while converting activities.
- Convert each lowest-level work package into one or more measurable schedule activities. Split a package into multiple activities only where the split reflects a genuine logic break, not merely convenience.
- Define the start condition and finish condition for each activity. State each condition as an observable result, not an elapsed duration.
- Identify mandatory preconstruction activities, including permits, design approvals, selections, submittals, contracts, insurance, and utility coordination. Record each as a predecessor to mobilization.
- Identify mobilization, site access, temporary utilities, fencing, protection, sanitation, and layout prerequisites. Record each as a predecessor to the first physical work activity.
- Order clearing, erosion control, excavation, utilities, drainage, grading, and foundation work according to approved plans and inspections. Record the governing inspection for each concealment-sensitive step.
- Order footing, foundation, waterproofing, drainage, backfill, slab, and structural activities according to cure and inspection requirements. Record the cure duration as a lag, not as part of the activity's own duration description.
- Order floor, wall, roof, stair, bracing, sheathing, and structural-connector work. Record bracing and connector requirements as finish conditions on the predecessor activity.
- Identify crane, lift, delivery, and temporary-bracing dependencies. Record each as a predecessor condition on the affected structural activity.
F. Structural, Envelope, and MEP Logic
- Order roofing, flashing, windows, doors, WRB, siding, and dry-in activities. Sequence each according to the manufacturer's required installation order.
- Define the project weather-tight milestone and the exact conditions required to achieve it. State the milestone as a list of completed envelope conditions, not as a date.
- Order plumbing, electrical, HVAC, gas, fire, low-voltage, and specialty rough-in work. Record each trade's rough-in as a successor to the weather-tight milestone where interior protection requires it.
- Identify framing, drilling, blocking, equipment, and access dependencies among MEP trades. Record cross-trade dependencies explicitly rather than assuming informal coordination.
- Identify rough-in inspections and work that must remain visible. Record each inspection as a hold point before the successor concealment activity may begin.
- Order insulation, air sealing, energy testing, fire blocking, and pre-drywall inspections. Record the pre-drywall inspection as the final hold point before drywall may begin.
- Order drywall, curing, sanding, primer, cabinets, trim, flooring, paint, fixtures, devices, and finish hardware. Record drywall cure and primer dry time as lags supported by manufacturer instructions.
- Identify finish-protection and humidity or temperature dependencies. Record any environmental condition required before a finish activity may begin.
- Order exterior flatwork, decks, fences, hardscape, landscaping, utility completion, and final grading based on access and weather. Record access conflicts with interior finish work explicitly.
- Identify permanent power, water, gas, HVAC, security, and utility-release milestones. Record each utility release as a predecessor to the activities that depend on it.
G. Procurement, Access, and Relationship Logic
- Identify owner-selection and material-release deadlines required before fabrication or installation. Record each deadline as a predecessor to the affected procurement activity.
- Identify design, submittal, fabrication, shipping, delivery, and installation logic for long-lead items. Record the complete chain as predecessors to installation, not as a single combined activity.
- Identify required samples, mockups, first-work inspections, and quality hold points. Record each as a predecessor to full-scale installation of the same assembly.
- Identify permit, special, manufacturer, utility, lender, and owner inspection relationships. Record the responsible party and required lead time for each.
- Identify curing, drying, acclimation, testing, startup, commissioning, and training durations as logic conditions. Record each as a lag supported by a specific document or manufacturer instruction.
- Identify access conflicts, shared equipment, limited laydown, occupied-area phasing, and trade-exclusion zones. Record each conflict and the activities it affects.
- Identify activities that cannot overlap safely or without quality loss. Record the reason for each exclusion.
- Identify activities that can proceed in parallel by area, phase, floor, or system. Confirm the parallel activities do not share the access, equipment, or crew conflicts identified in Step 25.
- Assign finish-to-start, start-to-start, finish-to-finish, or approved lag relationships. Assign the relationship type that matches the actual technical condition, not the type that is easiest to enter.
- Use lags only when they represent a real technical condition and not to hide an unmodeled activity. Support every lag with a cited document, code requirement, or manufacturer instruction.
H. Build, Test, and Approve the Logic Chart
- Identify potential rework loops caused by premature closure or incomplete handoff. Record each loop and the hold point that should prevent it.
- Create a visual logic chart from mobilization through owner handoff. Follow the document schedule in Section B.
- Walk the logic with field supervision and key trades. Record every comment received and how it was addressed.
- Test the sequence against one delayed inspection, one late material, and one owner-selection delay. Record the effect of each test scenario on the logic in the sequence-test record.
- Revise the logic to preserve safe alternate work paths where possible. Do not accept a sequence with no alternate path around a single point of failure without documenting the risk.
- Approve and version the sequence logic before building the baseline schedule. Record the approval on the sequence-approval record before Project 05 begins.
Common Sequence Logic Inspection
Inspect every sequence logic chart using the same checks regardless of project size or complexity.
- Activity-conversion check: confirm every lowest-level WBS work package appears as at least one activity with a defined start and finish condition.
- Physical logic check: confirm sitework through closeout activities are ordered according to approved drawings, cure, and structural requirements without an invented dependency.
- Concealment check: confirm every activity that will be concealed remains open in the logic until its governing inspection or hold point is satisfied.
- Procurement check: confirm long-lead and owner-selected items are modeled with complete submittal-to-delivery logic as predecessors to installation.
- Access and safety check: confirm parallel-work activities are free of unsafe overlap, access conflict, or unmanaged trade stacking.
- Testing check: confirm the sequence has been tested against a delayed inspection, a late material, and an owner-selection delay, with results recorded.
Complete the Sequence Logic Inspection Checklist in the Inspection Checklist section below before beginning Project 05.
Image Placeholder
Image Placeholder
Image Placeholder
Image Placeholder
Image Placeholder
Image Placeholder
Failure Points and Troubleshooting
Cleanup
This project ends with the approved sequence logic chart filed and distributed, not left as an open draft.
- Confirm the sequence-approval record is signed, dated, and filed with the project documents
- Confirm the sequence-test record shows all three required delay scenarios tested and their effects documented
- Move every superseded draft to the archive location and confirm it is clearly marked as superseded
- Distribute the approved baseline to field supervision, key trades, and other parties identified during the walk-through review
- Provide the approved logic chart and relationship log to Project 05 for use in building the baseline schedule
Field Terms
- Sequence Logic Baseline
- The one current, approved version of the sequence logic chart the Project 05 schedule is built from.
- Predecessor
- An activity that must reach its defined finish condition before a dependent activity may begin.
- Successor
- An activity that depends on a predecessor's defined finish condition before it may begin.
- Finish-to-Start Relationship
- A dependency in which the successor may not begin until the predecessor's finish condition is met.
- Lag
- A required waiting period between activities representing a real technical condition such as cure or drying time.
- Weather-Tight Milestone
- The defined point at which the envelope is sufficiently enclosed to permit interior work, stated by condition rather than date.
- Hold Point
- A required inspection or quality check that must be satisfied before a concealment-sensitive activity's successor may begin.
- Long-Lead Item
- A custom, engineered, imported, or limited-availability item whose submittal-to-delivery chain must be modeled as a full predecessor sequence.
- Trade Stacking
- Unsafe or unproductive congestion created when multiple trades share the same work area, access, or equipment at the same time.
- Alternate Work Path
- A safe, executable sequence of work that can proceed if a planned activity is delayed by inspection, material, or owner decision.
Skill Check
- Why must the sequence logic chart use the approved WBS as its only activity source, without reordering or merging work packages?
- What is the difference between a finish-to-start relationship and a start-to-start relationship, and why does the distinction matter for scheduling?
- Why must a concealment-sensitive activity remain open in the logic chart until its governing inspection or hold point is satisfied?
- What four stages must a long-lead item's procurement logic include before it is treated as ready for installation?
- Why is a lag only acceptable when it represents a real technical condition, and what happens when a lag is used to hide an unmodeled activity?
- What three delay scenarios must the draft sequence be tested against before it is approved?
- Why must the weather-tight milestone be defined by conditions rather than by a date at this stage of planning?
- What are three possible causes of an unsafe trade-stacking condition, and how does the learner confirm which one occurred?
- Why must sequence logic precede the assignment of calendar dates and durations in Project 05?
- Why does this chapter require field supervision and key trades to walk the draft logic before it is approved?
Competency Rubric
| Competency | Independent Pass Standard | Not Demonstrated | With Assistance | Independently |
|---|---|---|---|---|
| PM-019 | Identifies predecessor activities for each WBS work package with a documented physical, regulatory, procurement, or safety reason | |||
| PM-020 | Identifies dependent (successor) activities and assigns the correct relationship type for each predecessor | |||
| PM-021 | Orders sitework and foundation activities according to approved plans, cure requirements, and required inspections | |||
| PM-022 | Orders structural, dry-in, and envelope activities through the defined weather-tight milestone | |||
| PM-023 | Orders MEP rough-in and finish activities through required concealment inspections and finish-protection dependencies | |||
| PM-024 | Produces an approved, version-controlled sequence logic chart tested against delayed inspection, late material, and owner-selection delay |
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 — Sequence Logic Inspection Checklist
| Item | Standard | Meets Standard (Y/N) | Correction (if any) |
|---|---|---|---|
| Activity conversion | Every lowest-level WBS work package appears as at least one activity with a defined start/finish condition | ||
| Preconstruction logic | Permits, approvals, selections, submittals, contracts, insurance, and utility coordination sequenced before mobilization | ||
| Physical logic | Sitework through closeout ordered by approved plans, cure, and structural requirements | ||
| Concealment / inspection logic | Every concealment-sensitive activity linked to its governing hold point | ||
| Procurement logic | Long-lead and owner-selected items modeled with full submittal-to-delivery chains | ||
| Access and safety logic | Parallel-work activities confirmed free of unsafe overlap or trade stacking | ||
| Relationship assignment | Every dependency typed correctly; every lag supported by a cited document | ||
| Testing | Sequence tested against delayed inspection, late material, and owner-selection delay | ||
| Review | Draft walked with field supervision and key trades; comments recorded and addressed | ||
| Approval | Written approval by authorized party; baseline number and date assigned before distribution |
Sequence-test record status: ____________ Open risks carried forward: ____________
Sequence logic baseline declared approved: ______ (Pass/Fail) Date: ____________ Project manager name: ____________
Performance Check
With the sequence logic chart drafted and reviewed, review it against the Acceptance Standards table and confirm every WBS work package has been converted into at least one activity with a defined start and finish condition, sitework through closeout activities are ordered by physical, regulatory, procurement, safety, quality, access, cure, and trade-handoff requirements, every concealment-sensitive activity remains open until its governing hold point is satisfied, every long-lead item is modeled with a complete submittal-to-delivery chain, parallel-work activities are confirmed free of unsafe overlap, every relationship and lag is correctly typed and supported, the sequence has been tested against delayed inspection, late material, and owner-selection delay, and written approval has been obtained with a baseline number and date assigned. Complete the Sequence Logic Inspection Checklist and correct any failed item before beginning Project 05. If an item fails, identify whether the error occurred in activity conversion, physical logic, regulatory logic, procurement logic, access and safety logic, relationship assignment, or testing before revising.
Project Closeout
You have completed the fourth project in the construction project management sequence: sequencing the activities of a residential construction project. This project required you to identify predecessor tasks (PM-019), identify dependent tasks (PM-020), order site work (PM-021), order structural work (PM-022), order mechanical and finish work (PM-023), and create a sequencing logic chart (PM-024).
You now have an approved, version-controlled sequence logic chart, a predecessor-successor relationship log, and a documented sequence-test record. That logic carries directly into the next project: building the resource-informed, dated baseline schedule that applies durations, resources, and milestones on top of the sequence established here.
File your approved sequence logic chart and relationship log where Project 05 can incorporate them into the baseline schedule. Every later schedule, lookahead, and procurement date in this book is built on top of this exact sequencing logic.