Foundations of Construction Planning and Scheduling

Introduction

Construction projects transform an agreed need into a physical facility such as a building, road, bridge, industrial plant, or utility system. Although the visible product is concrete, steel, earthwork, finishes, and services, project success depends equally on the invisible systems used to decide what must be done, when it must be done, who will do it, and what resources are required. Construction planning and scheduling provide those systems.

Planning establishes the project strategy and the means of achieving the required scope. Scheduling converts that strategy into a time-based representation of activities, relationships, resources, and milestones. Planning answers, “What should be done and how will it be achieved?” Scheduling answers, “When will each activity occur, in what sequence, and for how long?” The two processes are interdependent: a schedule without a sound plan is precise but unreliable, while a plan without a schedule cannot be effectively coordinated or controlled.

Construction planning is not limited to producing a bar chart at the beginning of a project. It is a continuing management process involving definition of objectives, development of methods, allocation of resources, coordination of participants, assessment of risk, monitoring of progress, and adjustment to changing conditions. Scheduling is similarly dynamic. A baseline schedule may be approved at the start of construction, but updates are needed as design information, site conditions, productivity, procurement, and stakeholder decisions evolve.

Learning Objectives

After studying this chapter, you should be able to:

1. Explain the principal phases of a construction project life cycle.
2. Distinguish strategic, tactical, and operational planning.
3. Define fundamental scheduling terminology and explain activity relationships.
4. Describe the roles of major construction project stakeholders.
5. Compare planning horizons and select an appropriate level of detail.
6. Explain how scope, time, cost, quality, safety, and sustainability interact.
7. Identify common constraints and recognize the limitations of construction schedules.
8. Apply planning principles to an illustrative construction project.

1. The Construction Project Life Cycle

A project life cycle is the sequence of stages through which a project progresses from an initial need to completion and use. Terminology differs among organizations and contract systems, but a useful construction life cycle contains the following stages.

1.1 Initiation and feasibility

The project begins with a need, opportunity, statutory requirement, or business case. At this stage the owner identifies the desired outcome, users, preliminary scope, budget range, site, and strategic objectives. Feasibility studies may address:

• technical feasibility and site suitability;
• economic and financial viability;
• environmental and social effects;
• legal, planning, and permitting requirements;
• availability of materials, labor, and utilities; and
• major risks and alternative solutions.

The output is not a fully developed design. It is a justified decision about whether and how the project should proceed. Poor decisions at this stage can create expensive commitments later because changes become more difficult as design and construction progress.

1.2 Definition and preliminary planning

The owner and project team convert the project need into measurable requirements. The project brief may define capacity, performance, spatial requirements, quality standards, completion targets, sustainability objectives, and funding limits. A preliminary work breakdown structure (WBS), procurement strategy, risk register, stakeholder register, and high-level schedule can be developed.

The WBS divides the total scope into progressively smaller deliverables and work packages. It is a scope-oriented structure, not merely a list of trades. For example, a building WBS may include substructure, superstructure, envelope, internal finishes, mechanical services, electrical services, external works, testing, and handover.

1.3 Design and procurement

During design, the project requirements are translated into drawings, specifications, calculations, models, and construction information. Design development should be coordinated with cost, constructability, safety, environmental performance, and procurement considerations.

Procurement determines how design and construction responsibilities will be organized and how resources will be obtained. Common arrangements include traditional design–bid–build, design–build, construction management, and forms of public–private partnership. Procurement affects the timing of decisions, risk allocation, contractor involvement, and opportunities for overlap between design and construction.

1.4 Construction and control

Construction converts information and resources into the physical facility. The construction team coordinates labor, plant, materials, subcontractors, temporary works, inspections, permits, logistics, and site safety. The schedule is used to sequence work, communicate commitments, forecast completion, and identify emerging delays.

Control involves comparing actual performance with the approved plan. Important control information includes actual starts and finishes, remaining durations, quantities installed, productivity, costs committed and incurred, quality records, safety observations, design changes, and procurement status. Control is effective only when information is timely and sufficiently reliable.

1.5 Commissioning, handover, and closeout

Completion is more than finishing physical work. Systems must be tested, commissioned, inspected, documented, and accepted. Handover may require operation and maintenance manuals, as-built drawings, training, warranties, certificates, statutory approvals, and resolution of defects.

Closeout includes final accounts, release of temporary facilities, demobilization, lessons learned, claims resolution, and archiving of project records. A project is operationally successful only when the completed facility can be safely and effectively used.

1.6 Operation, maintenance, and end of life

The construction team influences the facility’s performance throughout its service life. Design choices affect energy consumption, maintenance access, durability, adaptability, and eventual demolition or reuse. Contemporary planning therefore considers the whole life cycle rather than only the construction phase.

2. Levels of Planning

Planning occurs at several organizational levels. Confusion between these levels often produces either excessive detail too early or insufficient direction for current work.

2.1 Strategic planning

Strategic planning establishes the project’s overall direction. It addresses questions such as:

• What business or social need is being addressed?
• What outcomes define success?
• What procurement and contracting strategy is appropriate?
• What is the funding, completion, and risk context?
• What sustainability and stakeholder commitments must be met?

Strategic planning is normally undertaken by the owner, sponsor, senior advisers, and key project leaders. Its horizon may extend from project conception through operation.

2.2 Tactical or project planning

Tactical planning translates strategy into an executable project approach. It determines construction methods, work packaging, site logistics, temporary works, procurement sequencing, labor assumptions, information requirements, quality procedures, and risk responses.

For example, a tactical plan may decide whether excavation will use a staged retaining system, whether prefabricated services modules will be used, and whether long-lead equipment must be ordered before detailed design is complete.

2.3 Operational planning

Operational planning focuses on near-term execution. It includes weekly and daily work plans, crew assignments, permits, deliveries, inspections, access arrangements, and safety controls. Operational planning should be derived from the master schedule but should also reflect actual site conditions.

A useful principle is that planning detail should increase as the work approaches. Long-range activities may be represented as summary packages, while near-term activities should be sufficiently detailed to guide crews and coordination.

2.4 Planning as a feedback system

Planning is iterative rather than strictly linear. Information from construction can reveal design coordination problems, unrealistic productivity assumptions, or procurement risks. That information should flow back into tactical and strategic decisions. Replanning is not necessarily evidence of failure; failure occurs when changing conditions are ignored or concealed.

3. Scheduling Terminology and Models

3.1 Activity, task, and work package

An activity is a defined item of work that consumes time and usually resources. Examples include “install level-two formwork” or “test fire alarm system.” A work package is a manageable portion of the WBS assigned to a responsible person or organization. A work package may contain several schedule activities.

Activities should be sufficiently specific to allow responsibility, duration, progress, and completion to be assessed. Activities that are too broad conceal problems; activities that are excessively small create administrative effort without improving control.

3.2 Duration and effort

Duration is the elapsed calendar time required to complete an activity. Effort is the quantity of labor or other productive work required. They are not identical. Ten worker-days of effort could be completed by one worker in ten working days or by two workers in five working days, subject to productivity and work-front limitations.

Duration estimates should consider quantities, production rates, crew composition, working hours, site conditions, weather, access, learning effects, rework, and nonproductive time. A basic production relationship is:

where T is activity duration, Q is the quantity of work, and R is the production rate in quantity per unit time. This relationship assumes that the production rate is appropriate for the stated crew, conditions, and working calendar. It does not automatically account for interruptions, resource limits, curing, inspections, or dependencies.

For example, if a crew places 120 m³ of concrete at a sustained rate of 30 m³ per working day, the productive placement duration is:

The schedule may require more than four calendar days if reinforcement inspection, formwork release, concrete curing, restricted working hours, or weather affects the operation.

3.3 Milestones

A milestone is a significant event with zero or negligible duration, such as “permit approved,” “structure topped out,” “building watertight,” or “practical completion.” Milestones communicate decisions and achievements but do not themselves represent productive work.

3.4 Logic relationships

Activities are connected by logical relationships. The most common relationship is finish-to-start (FS): the predecessor must finish before the successor starts. Other relationships are:

• Start-to-start (SS): the successor cannot start until the predecessor starts.
• Finish-to-finish (FF): the successor cannot finish until the predecessor finishes.
• Start-to-finish (SF): the successor cannot finish until the predecessor starts; this is uncommon and should be used carefully.

Relationships should represent real dependencies, not merely preferred sequences. Excessive or artificial links can make a schedule appear logically constrained and can obscure the actual cause of delay.

3.5 Leads and lags

A lag is a planned waiting period between linked activities. For example, concrete placement may be followed by a curing period before stripping or loading. A lead permits overlap between activities, such as beginning a successor before all predecessor work is complete, provided the overlap is technically and contractually acceptable.

Lags should be documented because unexplained lags are difficult to monitor. Where possible, the underlying activity should be modeled explicitly—for example, “curing” or “approval review”—rather than hidden as an unexplained delay.

3.6 Calendars and working time

A schedule calendar defines working days, shifts, holidays, planned shutdowns, and restrictions. A duration of five working days is not necessarily seven calendar days. Night work, multiple shifts, weather calendars, and access restrictions should be represented consistently with the project’s assumptions.

3.7 Baseline, update, and forecast

The baseline schedule is the formally approved plan against which performance is compared. A schedule update records actual progress and revises remaining durations or logic where justified. The forecast is the current prediction of future completion based on actual information.

The baseline should not be casually overwritten. Retaining approved baselines supports transparency, delay analysis, learning, and accountability.

3.8 Critical path and float

The critical path is the sequence of logically connected activities that determines the earliest possible completion date under the modeled conditions. Activities on a critical path generally have zero total float, although definitions and software conventions must be checked.

Total float is the amount of time an activity can be delayed without delaying the calculated project completion date, assuming other relationships and constraints remain unchanged. Float is a property of the network calculation, not a free resource that can always be consumed independently by every participant. When one activity uses float, the available float for related activities may reduce.

Criticality can change as actual progress, logic, durations, and constraints change. Therefore, the critical path is not a permanent label attached at project commencement.

3.9 Schedule representations

Common representations include:

• Bar charts or Gantt charts: accessible and effective for communicating timing and progress.
• Network diagrams: emphasize logical relationships and are useful for critical-path analysis.
• Line-of-balance schedules: useful for repetitive or location-based work such as roads, pipelines, and multistory buildings.
• Time–location diagrams: show movement of crews or activities through physical locations.
• Resource-loaded schedules: connect activities to labor, equipment, and material requirements.
• Four-dimensional building information models: link three-dimensional components with time information.

No representation is universally superior. The appropriate model depends on project type, complexity, repetition, information quality, and the decisions the schedule must support.

4. Stakeholders and Responsibilities

A stakeholder is a person, organization, or group that can affect, be affected by, or perceive itself to be affected by the project. Stakeholder management is a planning function because decisions and information flows affect time, cost, quality, safety, and acceptance.

Responsibilities must be supported by authority. Assigning a person responsibility for a date without giving access to information, resources, or decisions creates an accountability problem rather than effective control.

5. Planning Horizons and the Last Planner Concept

Planning horizons describe how far ahead the team plans and how much detail is appropriate. A practical hierarchy is:

1. Master or baseline schedule: the overall project, major interfaces, milestones, and contractual dates.
2. Phase or look-ahead plan: a detailed view of an approaching phase, often covering several weeks or months.
3. Weekly work plan: specific commitments for the next production period.
4. Daily coordination: crew-level sequencing, permits, access, deliveries, inspections, and safety controls.

The look-ahead process should identify constraints before work is promised. Typical constraints include missing drawings, unresolved design decisions, unavailable materials, incomplete preceding work, permits, access, plant, labor, and inspections. Removing constraints is often more valuable than simply adding detail to a schedule.

Lean construction approaches, including the Last Planner System, emphasize reliable workflow and commitments made by the people responsible for performing the work. The approach distinguishes what should be done from what can be done and what will be done. This encourages collaborative planning, constraint removal, learning from missed commitments, and reduction of variability.

6. Project Constraints and Interdependencies

A constraint is a condition that limits the available choices or performance of the project. Common constraints include:

• Scope: required functions, quantities, interfaces, and exclusions.
• Time: contractual dates, seasonal windows, funding deadlines, and user occupancy dates.
• Cost: approved budget, cash flow, escalation, and borrowing limits.
• Resources: labor, equipment, materials, information, and specialist capacity.
• Site: space, access, ground conditions, neighboring properties, utilities, and logistics.
• Regulation: planning approvals, building codes, environmental permits, labor rules, and safety law.
• Technology: design maturity, software interoperability, fabrication capability, and data quality.
• Stakeholders: decision speed, community tolerance, operational requirements, and political commitments.

Constraints may be hard, such as a statutory requirement, or soft, such as a preferred working sequence. Identifying which constraints are genuinely fixed helps the team evaluate alternatives rather than treating every preference as immovable.

Resource constraints can create a difference between a theoretically achievable schedule and a feasible schedule. A network may show two activities occurring simultaneously, but if both require the only available crane or specialist crew, the plan must be modified through resequencing, resource allocation, or additional capacity.

7. The Relationship Among Scope, Time, Cost, Quality, Safety, and Sustainability

Construction management is often introduced through the “iron triangle” of scope, time, and cost. This is useful but incomplete. Quality, safety, and sustainability are not optional additions; they are essential performance dimensions.

7.1 Scope, time, and cost

Scope defines what is to be delivered. Time defines when it is to be delivered. Cost defines the financial resources available. A change to one commonly affects the others. Adding a floor increases quantities, design effort, procurement, construction duration, and cost. Accelerating completion may require additional shifts, overtime, prefabrication, or parallel work, each of which can increase cost and introduce safety or quality risks.

The relationship is not a simple mechanical rule. Productivity improvements, design simplification, standardization, and early procurement may reduce time without proportionally increasing cost. Effective planning seeks such alternatives rather than assuming that every improvement requires more money.

7.2 Quality

Quality means satisfying stated requirements and being fit for intended use. Schedule pressure can encourage premature work, inadequate inspection, incomplete documentation, or substitution without proper review. These actions may appear to protect time while creating rework, defects, disputes, and life-cycle cost.

Quality should be planned through specifications, inspection and test plans, hold points, mock-ups, method statements, competent supervision, and clear acceptance criteria. Quality activities must be included in the schedule rather than treated as invisible administrative tasks.

7.3 Safety

Safety planning identifies hazards, assesses risk, selects controls, and coordinates safe work methods. A compressed schedule can increase exposure to simultaneous operations, fatigue, congestion, lifting conflicts, and rushed decisions. Conversely, good planning can improve safety by providing access, sequencing high-risk work appropriately, separating people and plant, and allowing sufficient time for controls.

Safety is both an ethical and legal responsibility. Production targets must never justify bypassing statutory duties, permits, competency requirements, or critical controls.

7.4 Sustainability

Sustainability includes environmental, social, and economic considerations across the facility life cycle. Planning decisions influence embodied carbon, waste, transport, energy use, water use, biodiversity, worker welfare, community disruption, adaptability, and maintainability.

Examples of schedule-related sustainability decisions include ordering materials in consolidated deliveries, using prefabrication to reduce waste, selecting lower-carbon materials, protecting existing vegetation, planning for material reuse, and avoiding unnecessary rework. A shorter construction duration is not automatically more sustainable if it requires excessive transport, waste, energy, or unsafe working patterns.

7.5 A systems perspective

The dimensions of performance should be treated as an interconnected system. A useful decision question is: “What is the effect of this change on the whole project and its life cycle?” For example, selecting a cheaper material may reduce initial cost but increase installation time, defects, maintenance, or environmental impact. The best decision is often the one that optimizes value rather than one isolated metric.

8. Developing a Reliable Basic Schedule

A disciplined scheduling process commonly follows these steps:

1. Confirm the project brief, assumptions, exclusions, and acceptance criteria.
2. Develop or verify the WBS.
3. Define activities and assign responsible parties.
4. Estimate quantities, resources, calendars, and durations.
5. Establish logical relationships and required milestones.
6. Add procurement, design, approvals, inspections, testing, and handover activities.
7. Check constructability, access, temporary works, and resource conflicts.
8. Analyze critical activities, float, constraints, and risks.
9. Review the schedule collaboratively with those who will perform the work.
10. Approve a baseline and define update procedures.
11. Record actual progress and forecast remaining work consistently.
12. Communicate decisions and revise the plan through controlled change management.

The schedule should be traceable to scope and supported by explicit assumptions. A visually attractive schedule can still be unreliable if it omits design release, procurement, approvals, commissioning, or realistic production conditions.

9. Illustrative Case: A Community Health Centre

Background

This illustrative case concerns a two-storey community health centre with consultation rooms, a pharmacy, laboratories, mechanical services, parking, and landscaping. The owner requires operational opening before the winter season. The site is constrained by a busy public road and an existing clinic that must remain open.

Problem

An initial contractor schedule showed completion in 12 months. During review, the project team identified that the schedule omitted planning approval conditions, long-lead medical equipment, utility shutdown coordination, commissioning, and user training. It also showed the same mobile crane serving structural steel and mechanical plant installation at overlapping times.

Analysis

The project team developed a WBS and a responsibility matrix. They identified the following principal constraints:

• restricted delivery hours because of the adjacent clinic;
• a six-week lead time for the main air-handling units;
• a required utility shutdown approved only during a specified weekend;
• winter weather risk for external works; and
• a need to separate public and construction traffic.

The team then prepared a six-month look-ahead plan, a procurement register, and a constraint log. The air-handling units were released for manufacture after confirming critical interfaces. Utility shutdown planning was linked to testing and temporary services. External drainage and service routes were resequenced to protect the winter work window.

Approach and solution

The revised schedule included design release, shop drawing review, procurement, delivery, installation, inspection, testing, commissioning, and training. The crane conflict was resolved by changing the lifting sequence and using a smaller mobile crane for selected operations. Weekly planning meetings required supervisors to identify constraints and make commitments only for work that was ready.

The owner accepted a modest increase in early procurement expenditure because it reduced the risk of late equipment delivery. A quality hold point was inserted before ceiling closure so that concealed services could be inspected and documented. Safety planning included segregated pedestrian routes and a permit system for the utility shutdown.

Outcome

The revised plan preserved the required opening date under the stated assumptions. More importantly, it provided a credible forecast and exposed risks early. The project team avoided treating the original 12-month duration as a fact; it tested whether the activities, resources, information, and approvals could realistically support that date.

Learning points

1. A schedule is only as reliable as its scope definition and assumptions.
2. Procurement and approvals are schedule activities, not background administration.
3. Constraint removal improves workflow reliability.
4. A small early cost may protect a major completion milestone.
5. Quality and safety controls must be integrated into the sequence.
6. The critical path can change when resources or interfaces change.

10. Challenges, Governance, and Contemporary Practice

10.1 Common limitations

Schedules are models of reality, not reality itself. They depend on uncertain estimates, incomplete information, assumptions about productivity, and representations of complex relationships. Excessive detail can create false confidence, while insufficient detail prevents meaningful control. Software can calculate dates quickly but cannot determine whether the logic is technically sensible.

Other common problems include manipulating logic to create a preferred completion date, hiding risk in large summary activities, failing to update remaining durations, ignoring subcontractor information, and treating progress percentages as objective when the measurement method is undefined.

10.2 Ethical and governance responsibilities

Professionals should report forecast dates honestly, distinguish facts from assumptions, preserve schedule records, and disclose significant risks. Progress should not be overstated to protect reputation or payment. Changes should be authorized through a documented process that considers scope, time, cost, quality, safety, and sustainability.

Contractual schedules also require care. A schedule may support payment, extension-of-time assessment, disruption analysis, or dispute resolution. Records should therefore identify the source and date of information, approved changes, actual events, mitigation actions, and the basis of forecasts. Legal requirements vary by jurisdiction and contract, so project teams must follow applicable law and contract conditions.

10.3 Digital tools and artificial intelligence

Construction management software, building information modeling, mobile field reporting, drones, digital twins, and cloud-based collaboration can improve information flow and visibility. Four-dimensional models can help teams visualize sequence and spatial conflicts. Automated progress recognition and predictive analytics may identify patterns associated with delay.

However, digital tools do not eliminate the need for professional judgment. Data may be incomplete, biased, incorrectly classified, or inconsistent with site reality. Artificial intelligence should be used with human review, documented assumptions, cybersecurity controls, privacy protection, and clear accountability. A prediction is not a fact merely because it is generated by a sophisticated system.

Chapter Summary

Construction planning and scheduling are complementary management processes. Planning defines objectives, scope, methods, resources, risks, and responsibilities; scheduling represents activities, logic, durations, milestones, constraints, and forecasts over time. The project life cycle extends from initiation and feasibility through definition, design, procurement, construction, commissioning, handover, operation, and eventual end of life.

Strategic planning establishes direction, tactical planning develops the project approach, and operational planning coordinates near-term work. Scheduling terminology includes activities, work packages, durations, milestones, calendars, relationships, lags, leads, baselines, updates, forecasts, critical paths, and float. Reliable schedules are built from a clear WBS, realistic assumptions, sound logic, resource information, and collaborative review.

Stakeholders have different but interdependent responsibilities. Planning horizons should become more detailed as work approaches, with constraint removal preceding reliable commitments. Scope, time, cost, quality, safety, and sustainability form an interconnected performance system. Decisions that improve one dimension can harm another, so professional planning seeks whole-project and life-cycle value. Finally, schedules are decision-support models that require ethical reporting, controlled change, continual learning, and informed use of digital technology.

Key Terms

Activity: A defined item of work that consumes time and usually resources.

Baseline schedule: The formally approved schedule used for comparison and control.

Constraint: A condition that limits project choices or performance.

Critical path: The logical sequence that determines the calculated earliest project completion.

Duration: Elapsed working or calendar time required for an activity.

Float: Time available for delay without delaying a specified project date, subject to network conditions.

Forecast: The current prediction of future dates based on actual information.

Lag: Planned waiting time between linked activities.

Lead: Planned overlap that permits a successor to begin before full completion of its predecessor.

Milestone: A significant event with zero or negligible duration.

Planning horizon: The period into the future covered by a plan.

Procurement: The process of obtaining works, materials, equipment, and services.

Scope: The agreed work and deliverables included in a project.

Schedule update: A controlled record of actual progress and revised remaining work.

Stakeholder: A person or organization that can affect or be affected by a project.

Sustainability: Management of environmental, social, and economic effects across the life cycle.

Work package: A manageable WBS component assigned to a responsible party.

Work breakdown structure: A hierarchical decomposition of the total project scope.

Review Questions

Short Answer Questions

1. What is the difference between construction planning and construction scheduling?
2. Name four major stages in a construction project life cycle.
3. Define a milestone and give one construction example.
4. What is the purpose of a baseline schedule?
5. Why should procurement and approvals be included in a construction schedule?

Long Answer Questions

1. Explain strategic, tactical, and operational planning and show how they are connected.
2. Describe the principal scheduling relationships and discuss when each may be appropriate.
3. Explain the roles of the owner, designer, contractor, scheduler, and subcontractors in project planning.
4. Discuss the relationship among scope, time, cost, quality, safety, and sustainability.
5. Explain why a construction schedule is a model rather than a perfect representation of reality.

Analytical / Application Questions

1. A project schedule shows structural work and mechanical plant installation occurring at the same time, but both require one crane. Analyze the problem and propose two planning responses.
2. A contractor claims that a five-day duration for a concrete activity is sufficient because the production calculation gives five days. Identify additional conditions that should be checked before accepting the duration.
3. Using the community health centre case, explain how early procurement, constraint removal, quality hold points, and safety planning contributed to protecting the opening date.

Multiple Choice Questions with Answers

Question 1

Which statement best distinguishes planning from scheduling?

A. Planning defines how objectives will be achieved, while scheduling represents activities and timing.

B. Planning is performed only by workers, while scheduling is performed only by owners.

C. Planning concerns cost only, while scheduling concerns quality only.

D. Planning occurs after construction, while scheduling occurs before project initiation.

Correct Answer: A. Planning defines how objectives will be achieved, while scheduling represents activities and timing.

Question 2

Which project life-cycle stage normally includes testing, training, operation manuals, and acceptance documentation?

A. Feasibility

B. Concept design

C. Handover and closeout

D. Site investigation

Correct Answer: C. Handover and closeout

Question 3

A finish-to-start relationship means that:

A. Two activities must finish at exactly the same time.

B. The successor cannot start until the predecessor finishes.

C. The predecessor cannot start until the successor finishes.

D. Two activities must always start simultaneously.

Correct Answer: B. The successor cannot start until the predecessor finishes.

Question 4

A crew places 150 m³ of concrete at a sustained rate of 30 m³ per working day. Ignoring inspections and other delays, what is the productive duration?

A. 3 working days

B. 5 working days

C. 30 working days

D. 180 working days

Correct Answer: B. 5 working days

Question 5

Which planning level focuses most directly on permits, deliveries, crew assignments, and daily site coordination?

A. Strategic planning

B. Feasibility planning

C. Operational planning

D. Corporate planning

Correct Answer: C. Operational planning

Question 6

What is the principal purpose of a work breakdown structure?

A. To decompose the total project scope into manageable deliverables and work packages

B. To calculate tax obligations for subcontractors

C. To replace all project drawings

D. To identify only safety hazards

Correct Answer: A. To decompose the total project scope into manageable deliverables and work packages

Question 7

Which statement about the critical path is correct?

A. It is permanently fixed once the baseline is approved.

B. It is always the sequence with the highest cost.

C. It can change as progress, durations, logic, and constraints change.

D. It includes every activity with a nonzero duration.

Correct Answer: C. It can change as progress, durations, logic, and constraints change.

Question 8

Why should quality inspections and commissioning be included in the schedule?

A. They consume time and may affect readiness for subsequent work and handover.

B. They are unrelated to project completion.

C. They eliminate the need for design information.

D. They are performed only after the project has been abandoned.

Correct Answer: A. They consume time and may affect readiness for subsequent work and handover.

Question 9

Which is an example of a hard constraint?

A. A preferred sequence selected for convenience

B. A statutory permit requirement

C. A supervisor’s informal preference

D. A suggested color scheme

Correct Answer: B. A statutory permit requirement

Question 10

What is an appropriate principle for using artificial intelligence in scheduling?

A. Accept every prediction without review because software is objective.

B. Use predictions with human judgment, verified data, and documented assumptions.

C. Replace all stakeholder communication with automated outputs.

D. Remove all schedule records once a prediction is generated.

Correct Answer: B. Use predictions with human judgment, verified data, and documented assumptions.