Governance, Ethics and Managerial Communication

Introduction

A network diagram and critical path method (CPM) schedule are not merely technical planning artefacts. They are governance instruments. They allocate accountability, expose dependencies, establish a basis for commitments, support contractual decisions, and provide evidence for assurance and audit. A technically correct schedule can still be organizationally dangerous if its logic is manipulated, its assumptions are hidden, its progress is overstated, or its approval rights are unclear.

Schedule governance concerns who may create, change, approve, report, audit, and rely upon schedule information. Schedule ethics concerns whether that information is represented honestly, completely, and in a manner that does not unfairly mislead decision-makers. Managerial communication converts schedule data into decisions: whether to accelerate, resequence work, approve change, accept risk, or revise a commitment.

For project managers, the central principle is simple: the schedule must be a controlled representation of the project’s current best-known plan, not a political document designed to create unjustified confidence.

Learning Objectives

By the end of this chapter, the reader should be able to:

1. Design governance arrangements for schedule ownership, approval, change control, auditability, and reporting.
2. Explain how CPM outputs should be interpreted and communicated to different stakeholders.
3. Identify optimism bias, manipulated logic, hidden contingency, misleading progress, and other ethical risks.
4. Align network schedules with contracts, assurance processes, organizational authority, and records requirements.
5. Apply practical controls to preserve the integrity and usefulness of schedule information.
6. Critically evaluate a schedule-based managerial decision in a complex project setting.

1. The Schedule as a Governance Artefact

Governance is the system by which an organization directs, controls, and assures work. A schedule supports governance because it makes intended sequence, timing, responsibility, and constraint visible. In a CPM network, activities are connected by logical relationships. The network permits calculation of earliest and latest dates, total float, and the path or paths that currently control the planned completion date.

For an activity, the basic forward-pass relationships are:

where ES is early start, EF is early finish, and D is activity duration. Under a finish-to-start convention, the early start of an activity is constrained by the early finish of its predecessors. For the backward pass:

where LS is late start and LF is late finish. Total float is:

These relationships assume a defined calendar, a consistent duration unit, valid network logic, and no unrepresented constraints. Float is not automatically spare time that can be consumed without consequence. It may be shared, owned by another party, required as contractual protection, or already exposed to uncertainty.

Governance determines which version of the network is authoritative, which assumptions are accepted, and who may authorize a change. Without these controls, the numerical outputs of CPM acquire a false appearance of objectivity.

1.1 Schedule ownership and accountability

Schedule ownership is broader than data entry. A schedule owner is accountable for the integrity of the integrated plan, including its assumptions, logic, calendars, coding, status date, interfaces, and reporting. Individual work-package managers remain accountable for the realism and timely updating of their portions.

A useful allocation distinguishes four roles:

The scheduler should not be made the sole owner of dates that depend on commercial, design, procurement, or operational decisions. Conversely, a project manager should not change logic informally without preserving the technical rationale and approval trail.

1.2 Approval rights and decision rights

Approval rights should be explicit. A schedule governance plan commonly defines:

• who approves the initial baseline;
• who may change activity dates, relationships, calendars, and constraints;
• what constitutes a baseline change;
• which changes require sponsor, client, or contract administrator approval;
• who accepts recovery plans and revised forecasts;
• how disagreements between functional managers are escalated.

A responsibility assignment matrix can be extended to schedule control using the categories Responsible, Accountable, Consulted, and Informed. The important distinction is that consultation does not equal approval. A stakeholder may review a forecast without having authority to authorize a new contractual completion date.

1.3 Baselines, forecasts, and actuals

A baseline is an approved reference plan. A current schedule is a forecast that incorporates actual progress, approved changes, and updated expectations. Actual dates are evidence of what occurred; forecast dates are estimates of what may occur. Confusing these categories is a common source of misleading reporting.

A robust schedule normally preserves:

1. the original approved baseline;
2. approved rebaselines, each with rationale and authorization;
3. the current working forecast;
4. actual start and finish records;
5. status-date snapshots;
6. change requests and supporting evidence.

A rebaseline should not erase the original plan. If the baseline is repeatedly moved to make performance appear acceptable, governance has been replaced by retrospective presentation.

2. Audit Trails and Configuration Control

An audit trail allows an independent reviewer to reconstruct what changed, when, by whom, why, and under which authority. At minimum, schedule change records should identify the affected activity or relationship, old value, new value, reason, initiator, reviewer, approver, effective date, and supporting evidence.

Configuration control extends beyond saving multiple files. It requires controlled naming, access permissions, version history, approved calendars, coding structures, and retention rules. A practical schedule record should make it possible to answer questions such as:

• What information was known at the reporting date?
• Which forecast was presented to the client?
• When did the critical path change?
• Was a date moved because work progressed, because logic changed, or because a constraint was imposed?
• Was the change approved before it was used in external reporting?

The status date is particularly important. Progress reported after the status date may be valid operational information but should not be silently inserted into a historical report. Time-phased data should be frozen at reporting cut-off, with late information clearly identified.

Schedule quality controls

Quality assurance should combine automated tests with professional review. Typical tests include:

• activities without predecessors or successors, except legitimate start and finish milestones;
• excessive use of mandatory constraints;
• negative float and unexplained imposed dates;
• out-of-sequence progress;
• very long activities that conceal uncertainty;
• excessive lags or leads;
• open-ended work packages;
• calendars inconsistent with contracts or resource availability;
• logic that bypasses approval, testing, or commissioning steps;
• changes to the critical path without an identifiable cause.

Automated checks identify anomalies; they do not determine whether an anomaly is legitimate. A commissioning activity may appropriately have a contractual date constraint, while an unexplained date constraint may be a method of hiding schedule weakness.

3. Ethical Risks in Schedule Development and Reporting

Ethical schedule practice requires honesty, competence, transparency, and respect for affected stakeholders. The ethical issue is not only whether a statement is technically false. A report can be misleading through omission, selective presentation, inappropriate precision, or the use of a technically defensible but practically deceptive model.

3.1 Optimism bias

Optimism bias is the tendency to underestimate durations, costs, or risks and overestimate the probability of favourable outcomes. It may arise from enthusiasm, pressure to win work, unfamiliarity with comparable projects, or the belief that known problems will not recur.

Controls include reference-class forecasting, independent challenge, explicit risk allowances, three-point estimating, and comparison with actual performance on similar work. Three-point estimates often use optimistic, most-likely, and pessimistic values. The estimates should not be treated as objective probabilities unless the organization has a defensible basis for assigning those probabilities.

A schedule should distinguish between:

• known work duration, representing planned productive effort;
• explicit risk-response activities, representing identified mitigation or recovery work;
• contingency, representing provision for uncertainty; and
• management reserve, which may be governed outside the performance baseline.

The location and ownership of contingency must be visible. A hidden buffer inserted into selected activities can distort float, conceal risk, and make performance comparisons unreliable.

3.2 Manipulated logic

Logic is manipulated when relationships or constraints are selected primarily to produce a desired forecast rather than to represent the actual work process. Examples include removing a predecessor to make an activity appear ready, using an arbitrary finish-to-finish link to avoid a delay, adding excessive lag instead of modelling real work, or splitting activities solely to move the apparent critical path.

Not every unusual relationship is unethical. A finish-to-finish relationship may accurately represent testing that can overlap with installation. The ethical test is whether the relationship reflects a defendable operational, technical, commercial, or safety dependency and whether its rationale is documented.

3.3 Hidden contingency

Contingency is not inherently improper. The problem arises when it is hidden from the people responsible for risk decisions or presented as normal productivity. Hidden contingency can lead managers to believe that the plan is more efficient than it really is, while later consuming the buffer without an appropriate risk discussion.

A transparent schedule records the nature, location, owner, trigger, and governance treatment of contingency. If management reserve is outside the baseline, reports should explain that fact rather than implying that the baseline contains all available protection.

3.4 Misleading progress

Progress can be overstated through premature start or finish claims, credit for procurement before delivery, excessive use of subjective percentage complete, or reporting physical progress without recognizing defective or rejected work. A milestone should be supported by objective evidence appropriate to its definition of done.

For measurable work, weighted milestones, quantity installed and accepted, or earned-value rules may be more reliable than an unsupported percentage estimate. If earned value is used, schedule performance measures must be interpreted carefully. For example:

where SPI is the schedule performance index, EV is earned value, and PV is planned value, both measured at the same status date and in the same value units. An SPI below 1 indicates less earned value than planned under the selected measurement rules; it does not, by itself, prove that the completion date will be late or identify the cause. It can be distorted by front-loaded budgets, changes in scope, or weak earning rules.

3.5 Conflicts of interest and retaliation

A scheduler may be pressured by a contractor, functional manager, or sponsor to suppress negative information. A sound governance system provides escalation routes and protects professional challenge. Schedule personnel should disclose conflicts of interest, avoid accepting unauthorized changes, and maintain evidence for material judgments. Ethical governance is weakened when reporting bad news is punished more severely than creating it.

4. Communicating Critical-Path Information

Critical-path communication is not simply the transmission of a list of activities. It is an explanation of what currently controls completion, why it controls completion, what uncertainty surrounds it, and what decision is required.

The critical path is the longest path through the network under the selected logic, calendars, constraints, and status assumptions. It may change as actual progress, resource availability, logic, scope, and risk evolve. A path with zero total float in one calculation is not necessarily the only path that threatens completion. Near-critical paths deserve attention because small delays can make them critical.

A useful management report should include:

• the current forecast completion date and baseline date;
• the controlling path or paths;
• activities with low or negative float;
• changes since the previous report;
• causes of variance, not merely symptoms;
• uncertainty, assumptions, and confidence limits where available;
• mitigation options and their consequences;
• decisions required, responsible decision-makers, and due dates.

Different audiences require different levels of detail. A sponsor usually needs the forecast, exposure, choices, and decision implications. A work-package manager needs logic, dates, interfaces, resources, and evidence requirements. A client or contract administrator may need contractual milestones, notices, approved changes, and contemporaneous records. The underlying facts must remain consistent even when the presentation is adapted.

A communication discipline

A practical message structure is:

Fact: What has happened?

Interpretation: What does the schedule analysis indicate?

Uncertainty: What assumptions or risks could change the conclusion?

Action: What options exist, and what decision is required?

For example: “The design approval is four working days later than the baseline. Because procurement release depends on that approval, the current forecast completion is two days later, with three days of float remaining. The forecast assumes expedited review and no further design comments. The sponsor must decide by Friday whether to authorize parallel procurement at additional cost.” This is more useful than saying simply that the project is “95 percent on track.”

5. Aligning Schedules with Contracts and Assurance

A project schedule may serve several purposes simultaneously: internal coordination, client reporting, payment administration, delay analysis, resource planning, and dispute resolution. These purposes are related but not identical. Contractual schedules may contain specified milestones, notice obligations, access dates, sectional completions, calendars, and rules for extensions of time. The project team must understand which schedule statements create contractual commitments and which are internal forecasts.

Contractual alignment

Before issuing a schedule, the project manager should identify:

• contractual completion and sectional dates;
• required schedule format, coding, calendars, and update frequency;
• notice requirements for delay, disruption, change, and access problems;
• responsibility for employer, contractor, designer, supplier, and authority activities;
• rules for acceptance, rejection, and recovery schedules;
• records needed to substantiate entitlement or responsibility.

A schedule should not be used to create a contractual obligation that was never approved, nor should contractual obligations be omitted because they are inconvenient to model. Where contract interpretation is uncertain, the matter should be referred to appropriate commercial and legal authority.

Assurance and independent challenge

Assurance is the structured examination of whether governance, controls, assumptions, and outcomes are reliable. An independent schedule review may examine network integrity, estimate quality, risk integration, progress evidence, contractual alignment, and the plausibility of the forecast. Independence means that the reviewer is sufficiently separate from the person whose performance is being assessed; it does not mean the reviewer lacks technical expertise.

Assurance should be proportionate. A high-risk infrastructure project may require a schedule risk analysis, forensic review, or independent estimate validation. A small internal project may require only peer review and documented approval. In all cases, the organization should preserve the distinction between assurance findings and management decisions.

Schedule risk analysis

Deterministic CPM produces a single forecast based on selected durations and logic. Real projects contain uncertainty. A schedule risk analysis may model duration ranges, correlations, risk events, and alternative logic to estimate a distribution of possible completion dates. Such analysis does not eliminate judgment. Results depend on model quality, input calibration, correlation assumptions, and treatment of unknowns.

A probability such as “there is an 80% chance of completing by date X” is meaningful only if the model, assumptions, and confidence interpretation are documented. It should not be presented as a guarantee. Risk analysis should inform contingency and decision-making rather than provide a mathematical disguise for unsupported optimism.

6. Technology, Data, and Artificial Intelligence

Modern scheduling platforms provide automated critical-path calculations, baseline comparison, anomaly detection, dashboards, and integration with cost, procurement, and field systems. These capabilities can improve transparency, but automation also creates governance risks. A system may calculate an accurate result from inaccurate logic; a dashboard may display an attractive indicator while hiding changes in definitions; and access permissions may allow unauthorized alteration.

Artificial intelligence can assist with pattern recognition, narrative generation, risk identification, and comparison with historical projects. However, AI-generated schedule recommendations require human validation. A model may reproduce historical bias, infer relationships that are not operationally valid, or obscure the source of a conclusion. Organizations should maintain data provenance, access controls, version history, explainability appropriate to the decision, and clear accountability for the final report.

The governing principle is that automation may support professional judgment but cannot transfer accountability away from authorized decision-makers.

7. Applied Case: The Riverside Hospital Extension

The following is an illustrative case.

Background

A public hospital extension consists of design, enabling works, structural construction, building services, commissioning, regulatory inspection, and handover. The approved baseline completion date is 30 September. The contractor submits monthly updates, while the hospital authority maintains responsibility for clinical equipment specifications and access to operating areas.

Problem

At month eight, the dashboard reports 92 percent overall progress and shows completion on 30 September. However, the integrated schedule contains several warning signs:

• equipment procurement is shown as 100 percent complete because purchase orders were issued, although delivery and acceptance remain outstanding;
• regulatory inspection has been removed as a predecessor to handover;
• a six-week lag has been inserted between installation and commissioning without explanation;
• the original baseline has been overwritten;
• design approval dates were moved to actual dates without a change record;
• the current critical path runs through commissioning, while a near-critical path through fire-safety approval has only two days of float.

The contractor argues that the dashboard reflects “commercially realistic progress.” The hospital authority is concerned that opening commitments are being presented to executives as secure.

Analysis

The schedule team first freezes the current data and retrieves the last approved baseline from records. It then validates progress evidence. Purchase orders are confirmed, but equipment delivery, installation, testing, and acceptance are not complete. The progress rule is therefore revised so that procurement credit is separated from physical and accepted progress.

The removed inspection predecessor is reinstated because regulatory approval is a genuine handover dependency. The lag is replaced with explicit commissioning and test activities, allowing responsibilities and evidence to be assigned. Design changes are recorded with their causes and approval status. The forecast is recalculated using the approved calendar and current actuals.

The revised report identifies 12 October as the most likely completion date under current assumptions. It also presents an acceleration option costing additional specialist resources and a risk that fire-safety approval could extend the date further. The hospital board is asked to decide whether to authorize acceleration, revise the opening commitment, or accept the exposure with a documented contingency plan.

Outcome

The board rejects the unsupported 30 September commitment and approves targeted acceleration of commissioning. The schedule baseline remains preserved, while an approved recovery forecast is issued as a separate controlled version. Monthly reports now distinguish ordered, delivered, installed, tested, and accepted equipment. An independent assurance review confirms the revised logic and progress rules.

Learning points

1. A high percentage-complete figure can be misleading when the earning rule does not represent accepted work.
2. Removing a real predecessor changes the meaning of the network rather than solving the underlying delay.
3. Preserving the original baseline is essential for accountability and learning.
4. Critical-path communication must include near-critical paths, assumptions, options, and decisions.
5. Ethical reporting may require communicating a worse forecast before improvement is possible.

8. Best-Practice Framework

A mature schedule governance system can be organized as a repeating control cycle:

1. Define: establish purpose, authority, calendars, coding, assumptions, and reporting rules.
2. Develop: create a network with defensible logic, estimates, milestones, and ownership.
3. Approve: baseline the plan through the appropriate governance authority.
4. Status: collect evidence at a defined status date and distinguish actuals from forecasts.
5. Analyse: examine critical and near-critical paths, variance, risk, float, and change.
6. Decide: authorize corrective action, change, escalation, or revised commitment.
7. Record: preserve versions, approvals, evidence, and rationale.
8. Learn: compare forecasts with outcomes and improve estimating, logic, and controls.

The framework is effective only when leaders reward accurate information. If project teams are praised for optimistic forecasts and criticized for transparent warnings, formal procedures will not produce ethical schedules.

Challenges and Limitations

Schedule governance cannot remove uncertainty or guarantee truthful forecasts. Complex projects may have emergent work, incomplete design, political constraints, and dependencies outside the project manager’s control. CPM itself simplifies reality by representing work through activities and relationships. Multiple critical paths, resource constraints, calendars, and probabilistic outcomes can make the phrase “the critical path” misleading if used without qualification.

Governance controls also impose cost. Excessive approval layers may delay legitimate updates, while excessive documentation may cause teams to treat records as bureaucracy rather than decision evidence. The appropriate response is proportionality: retain enough control to protect integrity, but allow timely operational management.

Finally, transparency must respect confidentiality, privacy, security, and commercial sensitivity. Ethical communication does not mean publishing every detail to every audience. It means providing each authorized audience with information that is accurate, material, comprehensible, and sufficient for its decision.

Chapter Summary

Schedule governance establishes ownership, authority, approval rights, configuration control, audit trails, and reporting discipline. CPM calculations are useful only when the network, calendars, constraints, progress data, and assumptions are credible. Baselines, forecasts, actuals, and rebaselines must be distinguished and preserved.

Ethical schedule management addresses optimism bias, manipulated logic, hidden contingency, overstated progress, conflicts of interest, and pressure to suppress bad news. Critical-path communication should explain the controlling path, near-critical exposure, causes, uncertainty, options, and decisions. Contractual schedules require alignment with milestones, notices, responsibilities, and evidence requirements. Assurance and technology can strengthen controls, but neither automation nor artificial intelligence removes professional accountability.

The mature project manager treats the schedule as both an analytical model and a governance record. Its value lies not in producing reassuring dates, but in enabling informed, timely, and defensible decisions.

Key Terms

Schedule governance: The system of authority, controls, and accountability used to direct and assure schedule management.

Schedule owner: The person accountable for the integrity and use of an integrated schedule.

Baseline: An approved reference plan used for comparison and control.

Forecast: The current estimate of future dates and outcomes.

Status date: The cut-off date to which actual progress and schedule information apply.

Audit trail: Evidence showing what changed, when, by whom, why, and with what approval.

Configuration control: Management of versions, access, calendars, coding, and approved schedule content.

Critical path: The longest controlling path through a network under specified assumptions.

Near-critical path: A path with sufficiently little float that it may soon control completion.

Total float: The calculated allowable delay before an activity affects the relevant planned completion date.

Optimism bias: Systematic tendency to underestimate difficulty or overestimate favourable outcomes.

Hidden contingency: Unidentified or undisclosed time provision embedded in the schedule.

Progress evidence: Objective information supporting reported actual performance.

Rebaseline: An approved replacement or revision of the reference plan.

Schedule risk analysis: Analysis that models uncertainty to estimate possible completion outcomes.

Assurance: Independent or structured examination of governance, controls, assumptions, and results.

Recovery schedule: A controlled plan intended to reduce or recover forecast delay.

Management reserve: Governed provision held for uncertain work outside or separate from the performance baseline.

Review Questions

Short Answer Questions

1. Why should the original baseline be preserved when a project is rebaselined?
2. Distinguish between a schedule owner and a project scheduler.
3. What is the ethical problem with removing a genuine predecessor from a network?
4. Why should near-critical paths be reported?
5. What information should an audit trail contain?

Long Answer Questions

1. Explain how schedule governance supports organizational accountability and contractual performance.
2. Discuss the ethical risks associated with optimism bias, hidden contingency, and misleading progress reporting.
3. Compare the informational needs of a sponsor, work-package manager, and client contract administrator.
4. Explain how assurance and configuration control can improve confidence in CPM outputs.
5. Evaluate the benefits and limitations of using artificial intelligence in schedule analysis and reporting.

Analytical / Application Questions

1. A contractor reports that a project is on time because procurement purchase orders are complete, but delivery, installation, and testing are unfinished. Design a progress-validation and reporting approach.
2. A project has three paths with total floats of 0, 2, and 4 working days. Explain how you would communicate the exposure and what additional evidence you would seek before recommending acceleration.
3. A sponsor asks the scheduler to overwrite the baseline so that the current forecast appears compliant. Formulate an ethical and governance-based response, including escalation and documentation steps.

Multiple Choice Questions with Answers

Question 1

Which statement best distinguishes a baseline from a forecast?

A. A baseline is an approved reference plan, while a forecast is the current estimate of future outcomes.

B. A baseline contains only actual dates, while a forecast contains only planned dates.

C. A baseline is always more accurate than a forecast.

D. A forecast cannot be changed after approval.

Correct Answer: A. A baseline is an approved reference plan, while a forecast is the current estimate of future outcomes.

Question 2

For an activity with ES = 12 working days and duration D = 8 working days, what is EF under the stated CPM convention?

A. 4 working days

B. 12 working days

C. 20 working days

D. 96 working days

Correct Answer: C. 20 working days

Question 3

Which practice most directly supports an audit trail?

A. Overwriting the previous schedule after every update

B. Recording the old value, new value, reason, initiator, and approval for a material change

C. Reporting only the latest completion date

D. Allowing all users unrestricted editing access

Correct Answer: B. Recording the old value, new value, reason, initiator, and approval for a material change

Question 4

Why is removing a genuine predecessor ethically problematic?

A. It necessarily shortens every activity duration.

B. It changes the model to produce a more favourable result rather than representing the actual dependency.

C. It eliminates the need for a baseline.

D. It converts a forecast into an actual.

Correct Answer: B. It changes the model to produce a more favourable result rather than representing the actual dependency.

Question 5

An SPI value below 1 generally indicates that:

A. More earned value has been achieved than planned at the status date.

B. Less earned value has been achieved than planned at the status date under the selected rules.

C. The project must finish late regardless of all other information.

D. The cost variance is exactly zero.

Correct Answer: B. Less earned value has been achieved than planned at the status date under the selected rules.

Question 6

Which communication format is most useful for a senior decision-maker?

A. A list of every activity without interpretation

B. Only a percentage-complete figure

C. Facts, interpretation, uncertainty, options, and the decision required

D. A revised baseline with no explanation

Correct Answer: C. Facts, interpretation, uncertainty, options, and the decision required

Question 7

What is hidden contingency?

A. A formally approved risk response with a named owner

B. Time provision embedded in the schedule without transparent identification or governance

C. A documented contractual milestone

D. An actual completion date recorded after work finishes

Correct Answer: B. Time provision embedded in the schedule without transparent identification or governance

Question 8

Which evidence is most appropriate for claiming accepted equipment progress?

A. A purchase order issued to a supplier

B. A verbal statement that delivery is expected

C. Verified delivery, installation, testing, and acceptance records as required by the progress rule

D. The existence of a procurement activity in the schedule

Correct Answer: C. Verified delivery, installation, testing, and acceptance records as required by the progress rule

Question 9

Why should a schedule risk analysis probability be accompanied by model assumptions?

A. Because probabilities are guarantees only when assumptions are hidden

B. Because the result depends on inputs, correlations, logic, and treatment of uncertainty

C. Because deterministic CPM cannot calculate dates

D. Because assumptions have no influence on the forecast

Correct Answer: B. Because the result depends on inputs, correlations, logic, and treatment of uncertainty

Question 10

What is the primary governance principle concerning AI-generated schedule recommendations?

A. AI recommendations require no review if the software is commercially licensed.

B. AI may support analysis, but authorized professionals remain accountable for decisions and validation.

C. AI should replace all schedule owners.

D. AI outputs should be accepted only when they produce the shortest completion date.

Correct Answer: B. AI may support analysis, but authorized professionals remain accountable for decisions and validation.