Schedule Governance, Communication, and Integrated Project Application

Introduction

A construction schedule is not merely a bar chart showing intended dates. It is a controlled management system that connects scope, design information, procurement, resources, contracts, cost, risk, quality, safety, and stakeholder decisions. A schedule becomes professionally useful when people can rely on its logic, status, assumptions, and revision history. Schedule governance provides that reliability.

Governance answers five practical questions: Who may create or change schedule information? Which schedule is authoritative? How are changes assessed and approved? How is performance communicated? What evidence demonstrates that the schedule remains credible? These questions become increasingly important as projects involve multiple contractors, design revisions, public authorities, digital systems, and contractual completion obligations.

This chapter develops an integrated approach to schedule specifications, assurance reviews, version and change control, reporting, ethical data practices, contractual responsibilities, collaborative decision-making, and project application. The emphasis is on the construction planner's professional judgment: a technically attractive schedule is not sufficient if it is unauthorized, unsupported, misleading, or disconnected from site reality.

Learning Objectives

On completing this chapter, students should be able to:

1. Explain the purpose and components of schedule governance.
2. Prepare schedule specifications that define structure, logic, calendars, coding, status dates, and update rules.
3. Conduct assurance reviews of schedule quality and interpret common schedule indicators.
4. Apply version control and a disciplined schedule change-control process.
5. Design reporting protocols for different project audiences.
6. Explain ethical, contractual, and legal responsibilities associated with schedule data.
7. Facilitate collaborative schedule decisions among owners, designers, contractors, and suppliers.
8. Develop an integrated project schedule and control plan for a construction project.
9. Evaluate the limitations of scheduling software, artificial intelligence, and automated forecasting.

1. Schedule Governance as a Management System

Schedule governance is the framework of authority, processes, standards, records, and controls used to ensure that schedule information is developed and used consistently. It is distinct from scheduling administration. Administration may involve entering dates or issuing reports; governance determines whether those activities are authorized, transparent, and fit for purpose.

A sound governance system has six connected dimensions:

Governance should be proportionate to project risk. A small fit-out may require a simple baseline, two-week look-ahead, and change log. A major hospital, railway, or process plant generally requires a hierarchical schedule, interface register, formal baseline approval, progress measurement rules, schedule risk analysis, forensic-quality records, and integrated reporting.

Governance roles

The project owner normally establishes contractual requirements and approves significant changes. The project manager coordinates the control system and resolves competing priorities. The scheduler develops and maintains the schedule, but should not unilaterally redefine scope, progress, or contractual dates. The construction manager validates site logic and constructability. Discipline leads and trade contractors provide activity information and progress evidence. The commercial manager evaluates time-related cost and entitlement. The design manager controls information release dates. The document controller protects records and revision status.

A responsibility assignment matrix should distinguish between preparing, reviewing, approving, and being informed. The familiar RACI terms—Responsible, Accountable, Consulted, and Informed—are useful, provided they are applied to actual decisions rather than used as a decorative table.

2. The Schedule Specification

A schedule specification is the project-specific rulebook for creating, updating, reviewing, and reporting the schedule. It should be issued early, preferably with the planning requirements in procurement documents, and refined during mobilization. It should not be so detailed that it prevents professional judgment, nor so vague that every participant uses a different interpretation.

2.1 Minimum specification content

A robust specification normally defines:

• schedule purpose, contractual status, and required levels of detail;
• work breakdown structure (WBS), organizational breakdown structure, and cost or location coding;
• activity naming conventions and maximum or minimum activity durations;
• calendars, working hours, holidays, weather allowances, and shift arrangements;
• logical relationship types and permitted use of leads and lags;
• constraints and treatment of imposed dates;
• milestones, interfaces, procurement activities, testing, commissioning, and handover;
• baseline submission, review, acceptance, and update dates;
• progress measurement rules for engineering, procurement, construction, and commissioning;
• rules for actual dates, remaining duration, forecast dates, and out-of-sequence work;
• data date, reporting cut-off, narrative, and distribution requirements;
• change control, audit trail, file naming, security, and retention;
• software version, file exchange format, and interoperability requirements.

2.2 Work breakdown and schedule architecture

The WBS decomposes the project into manageable deliverables and work packages. It should reflect how the project will be controlled, not merely how a tender document is organized. A useful architecture may contain project, building or system, area, discipline, work package, and activity levels. Excessive decomposition creates maintenance burden and false precision; insufficient decomposition hides interfaces and prevents meaningful progress measurement.

The schedule should distinguish at least four kinds of information:

1. Work activities: tasks consuming time and resources.
2. Milestones: zero-duration events representing decisions, completions, or approvals.
3. Logic: relationships explaining why one event affects another.
4. Calendars and constraints: rules that define when work can occur.

A relationship is meaningful only when it represents a real dependency. Finish-to-start is common, but start-to-start, finish-to-finish, and start-to-finish relationships may be appropriate. Lags should represent identifiable conditions, such as curing or statutory review, and should not be used to conceal missing activities.

2.3 Calendars and assumptions

Calendars are a frequent source of hidden error. A schedule should identify the working calendar for each activity, including normal hours, weekends, public holidays, planned shutdowns, seasonal restrictions, and resource-specific working patterns. Weather allowances should be based on an explicit method and evidence, not inserted arbitrarily into many activities.

Assumptions should be recorded in an assumptions register. Examples include anticipated design release dates, production rates, approval durations, access arrangements, and utility availability. Each assumption should have an owner, confidence assessment, required decision date, and consequence if it proves false.

3. Baselines, Status, and the Meaning of Progress

The approved baseline is the reference against which performance and change are assessed. It is not a prediction that conditions will remain unchanged. A baseline should be frozen at a defined approval point and retained unchanged. Approved changes should be incorporated through a documented baseline revision or change-controlled current plan, depending on the contract and governance rules.

A statused schedule includes actual and forecast information as of a data date. The data date is the boundary between historical information and forward-looking forecast. Mixing observations from different cut-off dates produces misleading results.

Progress measurement

Progress must be measurable, repeatable, and resistant to manipulation. Suitable methods depend on the activity:

• units installed for repetitive work;
• quantity-weighted steps for complex work;
• milestone or weighted milestone rules for design and procurement;
• physical measurement verified by records;
• earned-value methods when cost and resource data are sufficiently reliable.

The simplest percentage-complete statement is not always the best. For example, reporting that a wall is 80% complete because 80% of the elapsed time has passed confuses time with physical accomplishment. A weighted rule might allocate 20% to setting out, 50% to installation, 20% to inspection, and 10% to documentation. The weights must represent effort or value and be agreed before performance is measured.

For an activity with planned value PV, earned value EV, and actual cost AC, common performance indicators are:

Here, SV is schedule variance and CV is cost variance, both expressed in the same value units as PV, EV, and AC. SPI and CPI are dimensionless indices. An SPI below 1 indicates less earned value than planned at the status date, but it does not by itself prove that the contractual completion date will be missed. Earned-value measures are meaningful only when the baseline, progress rules, and cost data are credible. They should supplement, not replace, critical-path and milestone analysis.

4. Schedule Assurance and Quality Review

Schedule assurance is a structured examination of whether a schedule is logically sound, complete, current, traceable, and useful for decision-making. Assurance is different from editing. Editing corrects presentation or data-entry errors; assurance evaluates whether the model represents the project adequately.

4.1 Review dimensions

A practical review covers the following dimensions:

Structural quality. Is the WBS complete? Are activities coded consistently? Are milestones and interfaces visible? Are calendars appropriate?

Logic quality. Are activities connected by credible relationships? Are open-ended activities justified? Are excessive constraints, negative float, lags, or leads masking the real logic? Is out-of-sequence work identified?

Schedule realism. Are durations consistent with quantities, productivity, resources, access, and work methods? Are procurement and approvals given realistic durations?

Completeness. Are design, approvals, utilities, temporary works, inspections, testing, commissioning, training, handover, and closeout included? Are external interfaces represented?

Status integrity. Are actual dates supported by records? Is progress measured consistently? Are remaining durations based on current productivity rather than optimistic assumptions?

Change integrity. Can the reviewer identify what changed, why it changed, who approved it, and what effect it had on milestones and resources?

4.2 Quantitative indicators and their limits

Let N be the number of activities in a schedule. If N_open activities have neither predecessor nor successor, an open-end percentage can be calculated as:

This is a diagnostic indicator, not a universal pass/fail rule. Project start and finish milestones may legitimately have open ends, and some summary activities should not be logically linked. A high value suggests incomplete logic, but a low value does not guarantee a good schedule.

Similarly, the critical path is the longest logical path to a selected completion milestone under the model's calendars and constraints. It may change after every update. A path with zero total float is not automatically the only path requiring management: near-critical paths, constrained interfaces, procurement risks, and resource bottlenecks may also threaten completion.

A review should combine automated tests with professional inquiry. Automated checks can identify missing logic, invalid dates, excessive lags, and inconsistent calendars. They cannot determine whether a planned sequence is constructible or whether a reported actual date is truthful.

5. Version Control and Change Control

Version control prevents teams from working from different schedule realities. Every issued file should have a unique identifier, revision, status, data date, author, checker, approver, issue purpose, and storage location. A controlled naming convention might include project code, schedule type, data date, revision, and status. Superseded versions should be retained but clearly marked as superseded.

A schedule change is any alteration that affects activities, logic, dates, calendars, resources, coding, milestones, or interpretation of the approved plan. Not every correction has the same significance. A typographical correction may be handled through controlled editing; a design change affecting a completion milestone requires formal assessment.

Change-control workflow

1. Identify: record the proposed change, source, date, and affected scope.
2. Classify: distinguish correction, progress update, risk response, client change, contractor means-and-methods change, or external event.
3. Assess: model time, cost, resources, safety, quality, procurement, and interface effects.
4. Consult: obtain input from affected disciplines and contractual parties.
5. Decide: approve, reject, defer, or request further information under delegated authority.
6. Implement: update the controlled schedule and related registers.
7. Communicate: issue the approved revision with a narrative explaining differences.
8. Verify: confirm that field teams and downstream systems reflect the decision.

A time-impact analysis may be appropriate for a significant delay event. It should use a contemporaneous or appropriately controlled schedule, identify the event and its insertion point, test the affected logic, and distinguish cause from effect. It should not be used mechanically to manufacture entitlement. Contract wording, notice requirements, concurrency provisions, float ownership, and mitigation duties must be considered by the responsible commercial and legal teams.

6. Communication and Reporting Protocols

Different audiences require different information. Senior owners need milestone confidence, major risks, decisions, and trend information. Site supervisors need near-term constraints, work fronts, access, inspections, and deliveries. Designers need information release and review dates. Commercial teams need change events, delay records, and entitlement-relevant evidence. A single enormous report usually serves none of them well.

A reporting protocol should define:

• audience and purpose;
• reporting frequency and data date;
• responsible preparer and approver;
• required tables, charts, narratives, and exceptions;
• distribution list and controlled repository;
• escalation thresholds;
• response and decision deadlines.

A monthly executive report may contain a milestone dashboard, critical and near-critical paths, trend analysis, approved and pending changes, top risks, decisions required, and a concise narrative. A weekly control report may include two-week or six-week look-ahead activities, constraints, procurement status, design deliverables, inspections, and recovery actions. Daily records should capture actual site events, labour, equipment, weather, deliveries, instructions, access restrictions, and disruptions.

The narrative is essential. A date movement without explanation is not management information. A strong narrative states what changed, why it changed, the effect on contractual or internal milestones, the action owner, and the date by which action is required.

Communication as a control loop

Effective communication is a feedback loop: observe actual conditions, compare them with the plan, interpret variance, decide an intervention, implement it, and observe the result. Meetings should therefore end with explicit decisions, owners, due dates, and unresolved assumptions. A meeting that merely circulates information without assigning decisions has limited control value.

7. Ethical Data Practices and Contractual Responsibility

Schedule information can influence payment, extension-of-time claims, liquidated damages, public confidence, and safety decisions. Ethical practice therefore requires accuracy, traceability, impartiality, and respect for confidentiality.

A planner should not:

• record progress that has not been verified;
• backdate actual dates to improve performance indicators;
• manipulate logic to hide delay;
• delete unfavourable historical versions;
• present a forecast as a contractual commitment without authority;
• suppress uncertainty or risks to satisfy a reporting target;
• use another party's confidential information without authorization;
• allow software output or AI-generated text to substitute for professional verification.

Contractual responsibilities vary by jurisdiction and contract form. Nevertheless, common obligations include timely notices, maintaining required records, complying with approved programmes, providing updates, demonstrating delay causation, cooperating with instructions, and mitigating avoidable delay. The schedule is evidence within a broader record; it is not automatically conclusive evidence of entitlement.

Data protection also matters. Personnel data, security information, commercial rates, and proprietary designs should be accessed only for legitimate purposes. Retention periods, permissions, audit logs, and backups should follow contract, organizational, and applicable legal requirements.

8. Collaborative Decision-Making and Integration

Construction schedules are socio-technical systems. Software can calculate dates, but people determine assumptions, sequence, responsibility, and acceptable risk. Collaboration is especially important at interfaces where one party's completion is another party's start condition.

Useful collaborative practices include:

• planning workshops with trade supervisors and design leads;
• pull planning, in which teams identify prerequisites backward from a target milestone;
• constraint-log reviews that assign owners and release dates;
• interface registers linking deliverables between organizations;
• joint review of near-critical paths and recovery options;
• transparent alternatives analysis before committing to acceleration.

Collaboration does not mean that every decision is made by consensus. The accountable manager must make timely decisions within delegated authority, while documenting dissenting technical views where they are material.

Recovery planning should evaluate alternatives such as resequencing, additional crews, overtime, prefabrication, design release acceleration, alternative procurement, or scope partitioning. Each alternative should be tested for cost, safety, quality, logistics, labour availability, community impact, and risk transfer. Acceleration that increases unsafe work or creates rework is not genuine recovery.

9. Technology, Digital Integration, and Artificial Intelligence

Modern projects may integrate scheduling software with building information modelling, enterprise resource planning, field reporting, document management, geographic information systems, and cost systems. Integration can reduce duplicate entry and reveal inconsistencies, but it also creates data-governance risks. Each system should have a defined source of truth for activity identity, quantities, costs, documents, and approvals.

Four-dimensional BIM links model elements to time. It can support constructability reviews, work-zone planning, logistics simulation, and communication with non-specialists. Its value depends on model completeness, object coding, installation logic, and regular synchronization. A visually impressive sequence can still be operationally false if it omits temporary works, access, inspections, or commissioning.

AI tools can classify records, identify unusual progress patterns, summarize meeting minutes, forecast likely delays, or suggest relationships. Their output should be treated as decision support. A responsible workflow identifies the source data, tests for bias and missing information, protects confidential data, records human review, and preserves an audit trail. Forecast confidence should not be represented as certainty. AI cannot independently establish contractual causation or replace site verification and professional accountability.

10. Integrated Project Schedule and Control Plan

An integrated project schedule and control plan brings governance into one operational document. It should be prepared before detailed execution and updated when project conditions or contractual requirements change.

A practical control plan contains:

1. Project basis: scope, contract milestones, assumptions, exclusions, and interfaces.
2. Schedule architecture: WBS, coding, activity rules, calendars, logic conventions, and milestones.
3. Responsibilities: preparation, review, approval, progress evidence, and escalation roles.
4. Baseline process: submission, review comments, acceptance, freezing, and revision rules.
5. Progress system: measurement rules, evidence requirements, data date, and status cycle.
6. Assurance: automated checks, peer review, constructability review, and management assurance gates.
7. Change control: classification, impact analysis, authority levels, and records.
8. Reporting: audience-specific reports, frequencies, narratives, dashboards, and meeting cycle.
9. Risk and opportunity: schedule risk register, response owners, contingency, and triggers.
10. Records and technology: file control, permissions, integration rules, backups, and retention.
11. Closeout: testing, commissioning, training, as-builts, defects, handover, and lessons learned.

Worked application: Riverside Community Health Centre

The following is an illustrative case, not a report of an actual project.

Background. A two-storey health centre has a contractual completion milestone on 30 September. The work includes structural frame, envelope, mechanical and electrical services, medical-gas installation, finishes, testing, commissioning, authority approval, and handover. The owner, design consultant, main contractor, and several specialist contractors use different reporting practices.

Problem. At the end of May, the dashboard reports 78% overall progress. However, the medical-gas design is incomplete, the electrical utility connection has no confirmed date, and commissioning activities are represented by one summary bar. The contractor's update shows a completion date of 30 September, while the commissioning subcontractor forecasts 18 October. The parties disagree about whether the schedule is delayed.

Analysis. The project team first freezes the May data date and preserves the issued baseline and update. The scheduler performs an assurance review. It identifies missing design-release activities, an open-ended utility interface, excessive use of summary activities, inconsistent calendars, and progress credited to finishes before inspection. The reported 78% is therefore not a reliable indicator of readiness for handover.

The team decomposes commissioning into equipment completion, pre-functional checks, integrated systems testing, medical-gas certification, authority inspection, training, defects correction, and handover documentation. Each activity receives an owner, predecessor, successor, calendar, evidence rule, and forecast duration. The utility connection is added as an external interface milestone with a responsible owner and decision date.

Approach. The control plan establishes a weekly interface meeting, a Wednesday data date, a two-week look-ahead for site teams, and a monthly executive report. Progress on commissioning is measured by verified milestones rather than elapsed time. Design changes are entered in a change register and assessed for time and cost. The owner approves a revised sequence that completes unaffected areas while the utility issue is resolved. A recovery option involving additional commissioning personnel is evaluated, but only after confirming that equipment, documentation, and safe access will be available.

Outcome. The updated logic forecasts 12 October completion rather than 30 September. This result is initially unwelcome but credible. The owner issues a timely contractual notice and authorizes a documented recovery plan. After the utility date is confirmed and commissioning is resequenced, the forecast improves to 4 October. The project team retains both the original baseline and approved update, records the assumptions behind the recovery, and reports residual risk rather than declaring an unsupported return to the original date.

Learning points. First, aggregate percentage complete can conceal a critical readiness problem. Second, commissioning and handover must be planned from the beginning. Third, schedule assurance can reveal governance weaknesses before they become disputes. Fourth, transparent recognition of delay enables better decisions than optimistic reporting. Finally, a recovery plan is credible only when its resources, prerequisites, safety conditions, and evidence are controlled.

11. Challenges and Limitations

Schedule governance cannot eliminate uncertainty. Weather, productivity variation, design development, labour availability, market disruption, and unforeseen conditions remain. A schedule is a model of a project, not the project itself.

Several limitations require particular caution:

• A logically correct schedule may still use unrealistic durations.
• Critical-path results depend on calendars, constraints, and the selected completion milestone.
• Float is a model result and may be affected by changes in logic or progress data.
• Earned value can give a misleading picture when quantities, weights, or baseline budgets are weak.
• Detailed schedules can create an illusion of control and consume excessive maintenance effort.
• Digital integration may propagate one incorrect source record across many systems.
• Contractual analysis cannot be reduced to software calculations; contemporaneous evidence and contract interpretation remain essential.
• Forecasts become less reliable as they extend farther into an uncertain future.

The professional response is not to abandon the schedule but to make uncertainty visible through assumptions, risk registers, scenario analysis, confidence ranges, and decision thresholds.

Best-Practice Checklist

Before issuing a controlled schedule update, confirm that:

• the data date and reporting period are explicit;
• actual dates and progress have supporting evidence;
• the baseline and prior approved update are preserved;
• logic, calendars, constraints, and open ends have been reviewed;
• near-critical paths and key interfaces are identified;
• changes are classified and approved at the correct authority level;
• the narrative explains material movement and required decisions;
• contractual notices and records are not being replaced by informal communication;
• confidential data are appropriately protected;
• field teams, designers, suppliers, and management are working from the same issued version.

Chapter Summary

Schedule governance converts a schedule from a date list into a controlled project information system. A schedule specification establishes common rules for structure, calendars, logic, progress, status, reporting, and change. The approved baseline provides a stable reference, while status updates distinguish verified historical facts from forecasts.

Schedule assurance examines structural quality, logic, realism, completeness, status integrity, and change traceability. Automated indicators such as open-end percentages, schedule variance, and schedule performance index can support review, but none replaces professional judgment. Version control ensures that participants use the correct information, and change control links proposed alterations to documented impact, authority, implementation, and communication.

Effective reporting is audience-specific and uses narratives, decisions, owners, and deadlines rather than unexplained data. Ethical practice requires truthful progress, preserved records, protection of confidential information, and clear separation between forecast, baseline, and contractual commitment. Collaborative planning improves interfaces and recovery decisions, while digital tools, BIM, and AI are valuable only when their data, assumptions, and outputs are governed.

An integrated schedule and control plan combines these principles into a repeatable project system. Its ultimate purpose is not to produce attractive charts; it is to support timely, evidence-based, safe, and accountable construction decisions.

Key Terms

Schedule governance: The authority, standards, processes, and controls used to manage schedule information.

Schedule specification: Project rules defining how the schedule is developed, updated, reviewed, and reported.

Work breakdown structure (WBS): Hierarchical decomposition of project scope into manageable elements.

Baseline: An approved reference plan retained for performance and change comparison.

Data date: The boundary date separating recorded actual information from forecast information.

Status update: A controlled schedule revision containing actual progress and current forecasts.

Schedule assurance: Structured examination of schedule quality, completeness, realism, and traceability.

Critical path: The longest logical path to a selected completion milestone under the schedule model.

Near-critical path: A path with limited float that may become critical after modest change.

Float: Time flexibility calculated by the schedule model before an activity or milestone affects a required date.

Progress measurement: Agreed method for determining physical or weighted accomplishment.

Schedule variance: Difference between earned value and planned value at a status date.

Version control: Management of schedule identities, revisions, approvals, storage, and superseded files.

Change control: Formal process for assessing, approving, implementing, and recording changes.

Interface: Dependency or exchange of information, access, work, or acceptance between parties or systems.

Look-ahead schedule: Short-horizon schedule used to coordinate near-term work and constraints.

Assumptions register: Controlled list of uncertain premises, owners, decision dates, and consequences.

Time-impact analysis: Structured assessment of how a delay or change affects schedule logic and dates.

Schedule narrative: Written explanation of progress, variance, changes, risks, and required decisions.

Integrated control plan: Document combining schedule rules, responsibilities, assurance, reporting, change, risk, and records.

Review Questions

Short Answer Questions

1. What is the difference between schedule administration and schedule governance?
2. Why should an approved baseline be preserved rather than overwritten?
3. What information should a schedule narrative provide when a milestone moves?
4. State two ethical practices required when recording schedule progress.
5. Why are commissioning and handover activities important components of an integrated schedule?

Long Answer Questions

1. Explain the principal contents of a project schedule specification and discuss how each supports control.
2. Describe a complete schedule change-control workflow from identification through verification.
3. Compare the needs of senior management, site supervisors, designers, and commercial teams in schedule reporting.
4. Explain how schedule assurance combines automated checks with professional judgment.
5. Discuss the opportunities and limitations of BIM, digital integration, and artificial intelligence in schedule control.

Analytical / Application Questions

1. A contractor reports 85% completion, but authority approvals, testing, and utility connection are not represented in the schedule. Diagnose the governance and measurement weaknesses and propose corrective actions.
2. A design change affects a long-lead item and may delay commissioning. Develop the information, participants, analysis steps, approvals, and records required before revising the forecast.
3. Prepare an outline integrated schedule and control plan for a medium-sized building project, including WBS structure, baseline rules, progress measurement, assurance checks, reporting cycle, change authority, and ethical data controls.

Multiple Choice Questions with Answers

Question 1

Which document establishes the project-specific rules for schedule structure, calendars, updates, and reporting?

A. Schedule specification

B. Risk register

C. Procurement invoice

D. Quality punch list

Correct Answer: A. Schedule specification

Question 2

What is the primary purpose of an approved schedule baseline?

A. To replace all future forecasts

B. To provide a stable reference for performance and change comparison

C. To record only daily labour quantities

D. To eliminate the need for schedule updates

Correct Answer: B. To provide a stable reference for performance and change comparison

Question 3

If earned value is 80 and planned value is 100, what is the schedule performance index?

A. 0.80

B. 1.20

C. 20.00

D. 180

Correct Answer: A. 0.80

Question 4

Which action is most consistent with ethical schedule practice?

A. Backdating actual dates to improve performance

B. Deleting superseded schedules

C. Recording verified progress with supporting evidence

D. Hiding an unfavourable forecast from the owner

Correct Answer: C. Recording verified progress with supporting evidence

Question 5

What does the data date identify?

A. The date a contract was signed

B. The boundary between actual information and forecast information

C. The date of the final payment

D. The planned start of every activity

Correct Answer: B. The boundary between actual information and forecast information

Question 6

Which item is a typical output of schedule assurance?

A. An unsupported acceleration promise

B. A review of logic, calendars, open ends, and progress integrity

C. A replacement for the construction contract

D. An automatic entitlement to additional time

Correct Answer: B. A review of logic, calendars, open ends, and progress integrity

Question 7

Why should a schedule change be accompanied by an impact assessment?

A. To determine effects on time, cost, resources, interfaces, and risk

B. To ensure every activity has the same duration

C. To remove the need for stakeholder consultation

D. To prevent preservation of earlier versions

Correct Answer: A. To determine effects on time, cost, resources, interfaces, and risk

Question 8

Which reporting product is generally most useful to site supervisors?

A. A short-horizon look-ahead showing constraints and near-term work

B. A yearly corporate financial statement

C. A historical tender advertisement

D. A list of unrelated completed projects

Correct Answer: A. A short-horizon look-ahead showing constraints and near-term work

Question 9

What is a principal limitation of automated schedule checks?

A. They can never identify missing logic

B. They cannot determine whether every sequence is constructible or every actual date is truthful

C. They always delete the baseline

D. They eliminate the need for data dates

Correct Answer: B. They cannot determine whether every sequence is constructible or every actual date is truthful

Question 10

In the illustrative health-centre case, why was the reported overall percentage complete unreliable?

A. The project had no activities at all

B. Commissioning and interface activities were incomplete or poorly represented

C. The baseline had too many approved milestones

D. The owner refused to use any reporting protocol

Correct Answer: B. Commissioning and interface activities were incomplete or poorly represented