Project Execution, Monitoring and Integrated Control

Introduction

Project execution is the stage in which approved plans are converted into physical facilities, services, and documented deliverables. In construction, this includes mobilizing resources, coordinating trades, procuring materials, installing work, inspecting quality, managing safety, communicating information, and handing over completed outputs. Execution is not a mechanical implementation of the baseline. Conditions change, information develops, interfaces emerge, and decisions must be made under time and cost pressure.

Monitoring and integrated control provide the management system through which actual performance is compared with approved expectations and appropriate action is taken. Monitoring produces reliable information; control interprets that information and authorizes responses. Effective control therefore depends on three linked capabilities: a credible baseline, timely and accurate performance data, and disciplined decision-making.

A construction project manager must control the interaction among scope, schedule, cost, quality, resources, procurement, safety, risk, stakeholders, and contractual obligations. Improving one dimension may damage another. For example, accelerating a delayed activity may increase cost, reduce safety margins, or create quality defects. Integrated control seeks decisions that protect the project’s overall objectives rather than optimizing one isolated indicator.

Learning Objectives

On completing this chapter, the learner should be able to:

1. Explain the relationship between project execution, monitoring, and integrated control.
2. Establish effective information flows and manage interfaces among project participants.
3. Select and interpret construction key performance indicators (KPIs).
4. Apply earned value management (EVM) to assess cost and schedule performance.
5. Forecast final cost, completion time, and likely project outcomes.
6. Evaluate change requests and distinguish corrective, preventive, and contingency actions.
7. Explain how baselines, governance, records, and ethical conduct support project control.
8. Use digital systems and professional judgement without treating software outputs as substitutes for analysis.

1. The Execution–Monitoring–Control System

Execution produces work and evidence. Monitoring collects and organizes evidence about progress, resources, quality, safety, risk, and changes. Control compares evidence with the approved plan and initiates action. The process is continuous rather than a sequence performed only at monthly review meetings.

A useful control cycle is:

Plan → execute → measure → analyze variance → decide → act → update forecasts and plans.

The baseline is the approved reference against which performance is assessed. It normally includes:

• the scope baseline, consisting of the project scope statement, work breakdown structure, and accepted work-package descriptions;
• the schedule baseline, including activities, logic, durations, milestones, and dates;
• the cost baseline, including time-phased authorized budgets; and
• associated baselines or control requirements for quality, safety, resources, risk, and information.

A baseline is not an unchangeable prediction. It is a controlled commitment. Once approved, revisions require authorization, documentation, and traceability. If managers overwrite the baseline whenever performance deteriorates, variance disappears administratively while the underlying problem remains.

Execution responsibilities

During execution, the project team directs work packages, coordinates subcontractors, releases information, manages procurement, verifies completed work, resolves constraints, and records decisions. The project manager does not personally perform every task; the role is to establish conditions in which responsible parties can perform, report, and coordinate effectively.

Important execution controls include:

• work-package authorization and release;
• method statements, inspection and test plans, and permits;
• short-interval planning and look-ahead schedules;
• material and equipment tracking;
• design clarification and submittal management;
• daily records, photographs, survey data, and progress quantities;
• safety observations, incident reporting, and corrective actions; and
• payment and change documentation.

Execution information should be generated at its source. A subcontractor should report installed quantities and constraints close to the time of work, while the site engineer verifies evidence rather than merely copying reported percentages.

2. Information, Communication, and Interface Management

Construction projects are temporary multi-organizational systems. The owner, designer, main contractor, specialist subcontractors, suppliers, authorities, utilities, insurers, and end users possess different responsibilities and information. Many failures arise not from lack of technical skill but from gaps between organizational or technical interfaces.

An interface is a point at which two parties, systems, disciplines, contracts, or work packages must exchange information or deliver a compatible result. Examples include:

• structural openings coordinated with mechanical and electrical services;
• a utility relocation coordinated with excavation and traffic management;
• design responsibility transferred from consultant to specialist fabricator;
• a temporary works design coordinated with permanent works; and
• commissioning information transferred from installers to the facility operator.

Interface management method

A practical interface-management process is:

1. Identify interfaces. Use the work breakdown structure, drawings, method statements, contract boundaries, and site logistics plan.
2. Assign ownership. Each interface should have a responsible individual or organization, even where several parties contribute.
3. Define the required exchange. Specify the information, physical condition, date, acceptance criteria, and receiving party.
4. Record dependencies. Link interface milestones to the schedule and risk register.
5. Verify closure. An interface is closed only when the receiving party confirms that the requirement has been met.
6. Escalate unresolved constraints. Issues that threaten critical work should move rapidly through the governance structure.

A responsibility assignment matrix, such as a RACI matrix, may identify who is responsible, accountable, consulted, and informed. It clarifies authority but does not replace technical coordination or contractual interpretation.

Information quality

Information used for control should be accurate, timely, complete, traceable, and relevant. A sophisticated dashboard based on unreliable quantities is less useful than a simple verified report. Common information controls include document numbering, revision status, approval workflows, transmittal records, access permissions, audit trails, and defined reporting cut-off dates.

The reporting cycle should distinguish:

• data date: the point up to which actual performance has been recorded;
• forecast date: the date by which a future outcome is estimated;
• reporting period: the interval covered by the report; and
• baseline version: the approved reference against which results are compared.

Mixing these dates creates false variance and weakens accountability.

3. Monitoring Performance Through KPIs

A KPI is a defined measure used to assess progress toward a strategic or operational objective. A useful KPI has a clear numerator and denominator where appropriate, an owner, a data source, a frequency, a target, and an agreed interpretation. KPIs should stimulate decisions, not merely decorate reports.

Typical construction KPIs include:

A KPI should be tested against five questions: What decision will it support? Who owns the response? Is the data reliable? What is the threshold for action? Could the measure encourage undesirable behavior?

Leading and lagging indicators

Lagging indicators describe events that have already occurred, such as cost incurred, defects found, or injuries recorded. Leading indicators provide evidence about conditions that may influence future outcomes, such as overdue design reviews, unresolved constraints, toolbox-talk participation, or the percentage of planned inspections completed.

Both are necessary. A project can show acceptable current cost while accumulating procurement delays and design ambiguities that will create future cost. Conversely, a high number of reported near misses may indicate a strong reporting culture rather than deteriorating safety, so interpretation requires context.

Traffic-light reporting

Traffic-light systems commonly classify status as green, amber, or red. They are useful for rapid escalation but should be supported by definitions. For example, amber might mean a forecast breach is credible and management action is required; red might mean an approved threshold has already been breached or a major objective is threatened. Thresholds should not be altered to make a report appear healthier.

4. Earned Value Management

Earned value management integrates scope, schedule, and cost through a time-phased budget. It answers three different questions at a selected data date:

• How much work was planned to be complete?
• How much work is actually complete, valued at the approved budget rate?
• What has actually been spent?

The principal terms are:

PV and EV are monetary values used as a common measurement scale; EV is not the amount paid to the contractor. The method requires a defined scope, an approved time-phased budget, objective progress rules, and costs aligned to the same data date.

Core equations

Here, SV is schedule variance and CV is cost variance, both expressed in budget currency. Positive SV means more budgeted work has been completed than planned at the data date; positive CV means the budgeted value of completed work exceeds actual cost. In EVM, schedule variance is expressed in value terms and eventually tends toward zero at completion, so it should not be interpreted as calendar days.

SPI is the schedule performance index and CPI is the cost performance index. Values near 1.00 indicate alignment with the baseline; a value below 1.00 indicates unfavorable performance and a value above 1.00 indicates favorable performance, subject to data quality and scope stability. These ratios are dimensionless because their numerators and denominators use the same budget-value units.

For a simple forecast, if the remaining work is expected to be performed at the original budget rate:

If current cost efficiency is expected to continue for the remaining work:

If both cost and schedule performance are expected to influence the remaining cost, a commonly used forecasting form is:

These are forecasting assumptions, not universal laws. The project team must select the form that matches the cause of variance. For example, a one-time approved design error may not justify projecting past cost inefficiency into all future work.

ETC is the remaining forecast cost and VAC is the forecast variance at completion. A negative VAC indicates that EAC exceeds BAC.

Worked EVM example

At the end of month 6, a building-services work package has BAC = $1,200,000. The control account reports PV = $600,000, EV = $540,000, and AC = $630,000.

The package has completed less budgeted work than planned and has spent more than the budgeted value of the work completed. If current cost efficiency is expected to continue:

The forecast suggests a final overrun of approximately $200,000. Management should not immediately treat this number as a fact. It should investigate causes, validate accruals and progress measurement, assess remaining risks, and determine whether corrective action can change the forecast.

EVM limitations

EVM can conceal important issues when work packages are too large, progress rules are subjective, or budgets are loaded into early activities. Percent-complete estimates may also reward reporting rather than actual completion. EVM does not directly measure quality, safety, customer satisfaction, cash flow, or technical performance. It should therefore be combined with physical progress, schedule-network analysis, quality records, risk analysis, and professional judgement.

5. Schedule and Cost Forecasting

Monitoring describes current status; forecasting estimates future status. A forecast should state its assumptions, confidence, data date, risks, and sensitivity to changed conditions.

Schedule forecasting

A schedule forecast uses updated activity durations, logic, actual starts and finishes, remaining durations, resource constraints, calendars, and approved changes. Critical path analysis identifies the longest path through the network under the schedule model. However, the critical path can change when actual progress, logic, or constraints change. A noncritical activity may also possess low total float and become critical quickly.

Schedule control should examine:

• activities completed later or earlier than planned;
• remaining duration and productivity assumptions;
• logic changes and missing dependencies;
• near-critical paths and total float;
• procurement and approval constraints;
• access, workface, and resource availability; and
• effects of proposed acceleration on cost, safety, and quality.

A recovery plan should identify specific actions, owners, resources, dates, and decision thresholds. “Work harder” is not a recovery strategy.

Cost forecasting

A cost forecast should include actual costs, accrued costs, committed costs, approved changes, probable changes, remaining procurement, labor productivity, escalation, risk exposure, and indirect costs. The accounting system and project-control system must define whether figures are cash-based, invoice-based, accrual-based, or commitment-based. Comparing an accrual-adjusted forecast with invoice-only actual cost creates misleading variance.

Forecast confidence can be improved through bottom-up ETC analysis. Each responsible manager estimates the remaining cost of assigned work, including known constraints and realistic productivity. This is more resource-intensive than applying a single index but may be more credible when performance conditions are changing.

6. Change Control and Baseline Governance

A change is a modification to an approved requirement, design, method, sequence, contract condition, or baseline. Not every site instruction is a formally approved change, and not every change request should be accepted. A disciplined process protects both project objectives and contractual rights.

A change-control procedure commonly includes:

1. submission of a clearly described change request;
2. classification of its origin, such as client, design development, unforeseen condition, regulatory requirement, or contractor proposal;
3. assessment of scope, schedule, cost, quality, safety, risk, procurement, sustainability, and interfaces;
4. identification of alternatives, including rejection or deferral;
5. review by authorized technical and commercial personnel;
6. decision by the appropriate authority;
7. update of affected documents and baselines; and
8. communication, implementation, and verification.

A change log should record the request identifier, description, originator, date, status, estimate, decision authority, decision, implementation date, and links to supporting evidence.

Change evaluation

The project team should distinguish:

• scope change: alters what is to be delivered;
• design development: provides information needed to define already-approved scope;
• correction: fixes nonconforming work or an error;
• constructive change: an instruction or action that effectively changes work even if the formal process was not followed; and
• trend or potential change: an emerging issue requiring early visibility before final authorization.

A change analysis should consider direct cost, indirect cost, time impact, disruption, acceleration, rework, risk transfer, maintainability, and legal or contractual entitlement. Double counting must be avoided: a risk allowance, contingency, and change estimate should not all be added for the same event without explanation.

Baseline changes should be approved only by authorized governance. The original baseline should remain accessible so that performance history is not erased. A revised baseline supports forward management; it should not be used to conceal past underperformance.

7. Corrective, Preventive, and Contingency Action

A corrective action addresses an observed unfavorable deviation or nonconformance. Examples include resequencing work after a delay, replacing defective material, or assigning additional design resources to clear a critical approval backlog.

A preventive action addresses a potential problem before it occurs. Examples include early procurement of a long-lead item, additional design checking for a recurring error, or a trial installation before mass production.

A contingency action is a planned response activated if a specified risk occurs. For example, a project may identify an alternative supplier if the primary supplier exceeds a defined delivery threshold.

Effective actions have an owner, due date, required resources, acceptance criteria, and verification method. Closing an action means confirming effectiveness, not merely entering a completion date in software. Root-cause analysis is necessary when symptoms recur. Techniques such as the five whys, cause-and-effect diagrams, and barrier analysis can support investigation, but they should be applied with evidence rather than used as a ritual.

8. Integrated Control Across Project Domains

Integrated control requires understanding interactions among domains. A delayed façade package may affect enclosure, internal finishes, temporary heating, commissioning, energy performance, and handover. A design change may affect procurement, access, waste, safety, and contractual entitlement.

A practical integrated review considers the following chain:

Issue or change → affected scope → activities and interfaces → resources and procurement → cost and cash flow → quality and safety → risk exposure → stakeholder and contractual effects → decision and updated forecast.

The project controls team should reconcile information from different systems. For example, installed quantities in the site measurement system should be consistent with progress claims, the schedule update, the cost report, and the earned-value calculation. Differences may be legitimate because each system has a different purpose, but unexplained differences require investigation.

Governance forums should be proportionate. A daily coordination meeting may resolve workface constraints; a weekly progress meeting may review near-term performance; a monthly management review may approve forecasts and escalated changes; and a formal change board may authorize baseline revisions. Decision rights should be defined in advance.

9. Digital Tools, BIM, and Artificial Intelligence

Common digital tools include integrated cost and schedule systems, field-reporting applications, document-management platforms, building information modelling (BIM), geographic information systems, drone or photographic progress capture, and automated dashboards. These tools can improve traceability and reduce transcription, but they do not guarantee correct control.

BIM can support visual coordination, quantity extraction, sequencing, and asset information transfer. Its value depends on model purpose, information requirements, authorship, version control, and validation. A visually attractive model may still contain inaccurate quantities or unresolved responsibility boundaries.

Artificial intelligence can assist with document classification, anomaly detection, progress-image comparison, forecasting, and retrieval of relevant project records. Professional controls remain essential because AI outputs may reflect incomplete data, biased training information, incorrect interpretation, or confidentiality risks. AI-generated recommendations should be explainable enough for responsible personnel to review, and sensitive project data should be handled under approved information-security arrangements.

Technology should therefore be governed by the questions: What decision is being supported? What evidence is used? Who validates the output? What happens when the system is wrong? Who retains accountability?

10. Ethics, Contract, and Regulatory Responsibility

Project control information has commercial and safety consequences. Ethical practice requires truthful reporting, transparent assumptions, protection of confidential information, avoidance of conflicts of interest, and prompt escalation of threats to safety or compliance. Manipulating progress percentages, delaying recognition of cost, suppressing defects, or changing thresholds to avoid escalation undermines the project and may create legal liability.

The project team must comply with applicable building regulations, occupational health and safety requirements, environmental permits, labor rules, procurement conditions, and contract notice provisions. The exact legal requirements vary by jurisdiction and contract form; this chapter does not replace professional legal advice.

Records are particularly important in disputes. Contemporaneous records should show what occurred, when it occurred, who was informed, what evidence supports the assertion, and what action was taken. Records should be factual and distinguish observation from opinion. A good record supports learning and fair allocation of responsibility; it is not a weapon for manufacturing entitlement.

11. Illustrative Case: Delayed Hospital Expansion

Background

A contractor is constructing a three-storey hospital expansion under a design-and-build arrangement. At the end of month 8, the mechanical-services package has a BAC of $2.4 million. Its reported values are PV = $1.20 million, EV = $1.08 million, and AC = $1.26 million. The package includes medical-gas systems, air handling, plumbing, and controls.

Problem

The package is behind plan and over cost. Several equipment submittals are late, ceiling-space coordination is incomplete, and installed ductwork has required rework. The mechanical package is not currently on the longest overall schedule path, but it has only five days of total float and interfaces with commissioning.

Analysis

The performance indices are:

If the current cost efficiency continues, the simple EAC is:

This indicates a potential $0.4 million overrun. However, the team identifies that $80,000 of the cost variance results from a one-time design coordination error already corrected. The remaining concern is low productivity caused by congested workfaces and late equipment information. Applying the index mechanically would overstate the likely final cost if the one-time event is genuinely nonrecurring.

Approach and solution

The project manager establishes an integrated recovery plan:

• the design manager must close priority coordination issues within five working days;
• procurement must issue a submittal and fabrication dashboard for long-lead equipment;
• the mechanical contractor must submit a revised workface plan and measured productivity assumptions;
• a controlled trial installation is used to verify the revised ductwork detail;
• the scheduler links equipment delivery, ceiling closure, testing, and commissioning milestones;
• the commercial manager separates approved change, probable change, and contractor-caused rework;
• weekly earned-value analysis is combined with physical quantities and quality inspections; and
• the risk register records the possibility that commissioning will be delayed if interfaces remain open.

The team does not simply add labor. It tests whether additional labor would worsen congestion and safety. A forecast is prepared using a bottom-up ETC, with the one-time design error excluded from future productivity assumptions but unresolved interface risk retained.

Outcome

After four weeks, priority submittals are approved, the workface plan reduces congestion, and rework falls. The package remains two days behind its revised interim milestone but protects the overall commissioning date. The final forecast is revised to $2.68 million rather than the mechanically calculated $2.80 million. The forecast is still above BAC, but the remaining variance is visible, explained, and linked to accountable actions.

Learning points

1. EVM identifies a signal; it does not explain the cause.
2. One-time events and systemic inefficiency require different forecasts.
3. Interfaces can be more important than the status of an individual activity.
4. Corrective action must be tested against safety, quality, and workface capacity.
5. A credible forecast includes assumptions and uncertainty, not only a number.

12. Challenges and Limitations

Integrated control is difficult for several recurring reasons. First, progress is often measured subjectively, especially for design, procurement, and partially complete installations. Second, reporting may be delayed until information is already obsolete. Third, contract incentives can encourage local optimization or concealment. Fourth, frequent changes may make the baseline unstable, although instability is not a justification for abandoning control. Fifth, data systems may use inconsistent coding structures, calendars, cost categories, or definitions of completion.

Other limitations include:

• EVM ratios can be distorted by front-loaded budgets or poor work-package design;
• schedule forecasts can be unreliable when logic is incomplete or constraints are hidden;
• KPIs can create perverse incentives when used as isolated targets;
• dashboards may encourage attention to measurable issues while neglecting important qualitative risks;
• forecasts are conditional estimates, not guarantees; and
• excessive reporting can consume time needed for management action.

The remedy is not more data automatically. It is better definitions, verification, appropriate aggregation, clear accountability, and management attention to causes.

Best-Practice Checklist

Before issuing a control report, the project team should confirm that:

• the data date and baseline version are stated;
• scope, schedule, and cost information refer to the same work and period;
• progress quantities have evidence and an agreed measurement rule;
• actual costs include appropriate accruals and commitments;
• major variances have causes, owners, and response dates;
• forecasts state assumptions and distinguish approved from potential changes;
• critical and near-critical interfaces are visible;
• corrective and preventive actions are verified for effectiveness;
• safety, quality, contractual, and regulatory effects have been considered; and
• decisions and baseline changes are authorized and traceable.

Chapter Summary

Project execution converts approved scope into deliverables, while monitoring gathers evidence and integrated control converts evidence into decisions. Reliable control requires a credible scope, schedule, and cost baseline; disciplined information management; clear ownership of interfaces; and reporting that is timely, accurate, and actionable.

KPIs should combine leading and lagging measures across schedule, cost, productivity, quality, safety, procurement, risk, information, and sustainability. Earned value management uses PV, EV, and AC to calculate variances and performance indices, but its results depend on objective progress measurement and should be interpreted with physical, technical, and risk information. EAC and ETC are conditional forecasts whose assumptions must be made explicit.

Change control protects baseline integrity by evaluating scope, cost, schedule, quality, safety, risk, interfaces, and contractual effects before authorization. Corrective action responds to observed deviation, preventive action reduces the likelihood of future problems, and contingency action is activated when a defined risk occurs. Digital tools, BIM, and AI can strengthen traceability and analysis, but accountability remains with competent professionals. Ethical reporting, regulatory compliance, and contemporaneous records are essential to trustworthy project governance.

Key Terms

Baseline: An approved reference used to assess and control project performance.

Budget at completion (BAC): The total approved budget for the defined scope.

Corrective action: Action taken to address an observed deviation or nonconformance.

Cost performance index (CPI): Earned value divided by actual cost.

Earned value (EV): Budgeted value of work actually completed.

Estimate at completion (EAC): Forecast total cost at project completion.

Estimate to complete (ETC): Forecast cost required to complete remaining work.

Interface: A point where parties, systems, disciplines, or work packages must exchange compatible information or results.

Integrated control: Coordinated management of project performance across interdependent domains.

Key performance indicator (KPI): A defined measure used to assess progress toward an objective.

Leading indicator: A measure of conditions that may influence future performance.

Preventive action: Action taken to reduce the likelihood of a potential problem.

Planned value (PV): Budgeted value of work scheduled by a specified data date.

Schedule performance index (SPI): Earned value divided by planned value.

Schedule variance (SV): Earned value minus planned value in budget-value units.

Actual cost (AC): Cost incurred for completed work by the data date.

Variance at completion (VAC): Budget at completion minus estimate at completion.

Change control: The governed process for evaluating, approving, documenting, and implementing changes.

Contingency action: A planned response activated when a specified risk condition occurs.

Review Questions

Short Answer Questions

1. What is the difference between monitoring and control?
2. Define planned value, earned value, and actual cost.
3. Why should interface ownership be assigned explicitly?
4. Distinguish a leading indicator from a lagging indicator.
5. What is the purpose of preserving the original project baseline?

Long Answer Questions

1. Explain how scope, schedule, and cost baselines support integrated project control.
2. Discuss the strengths and limitations of earned value management in construction projects.
3. Describe a disciplined change-control process and explain why unauthorized changes are dangerous.
4. Explain how information quality and reporting governance affect management decisions.
5. Compare corrective, preventive, and contingency actions using construction examples.

Analytical / Application Questions

1. A work package has BAC = $900,000, PV = $450,000, EV = $405,000, and AC = $480,000. Calculate SV, CV, SPI, CPI, and EAC using the assumption that current cost efficiency continues. Interpret the result.
2. A delayed procurement package is not on the current critical path but has four days of float and supplies equipment needed for commissioning. Identify the interfaces, KPIs, and corrective actions you would include in a recovery plan.
3. A contractor requests additional labor to recover schedule delay caused by congested workfaces. Evaluate the request using integrated control principles, including cost, safety, quality, productivity, and interface considerations.

Multiple Choice Questions with Answers

Question 1

Which statement best describes earned value (EV)?

A. The amount paid to the contractor by the data date

B. The budgeted value of work actually completed by the data date

C. The total approved project budget

D. The forecast cost of all remaining work

Correct Answer: B. The budgeted value of work actually completed by the data date

Question 2

If PV = $500,000 and EV = $450,000, what is the schedule variance?

A. $50,000

B. −$50,000

C. $950,000

D. −$450,000

Correct Answer: B. −$50,000

Question 3

A CPI of 0.80 generally indicates that the project is:

A. Obtaining $0.80 of budgeted value for each $1.00 of actual cost

B. Completing 80% more work than planned

C. Exactly on budget

D. Spending nothing on completed work

Correct Answer: A. Obtaining $0.80 of budgeted value for each $1.00 of actual cost

Question 4

Which is a leading safety indicator?

A. Recorded lost-time injury

B. Final accident cost

C. Percentage of planned safety inspections completed

D. Number of injuries at project completion

Correct Answer: C. Percentage of planned safety inspections completed

Question 5

What is the principal purpose of a change log?

A. To remove the original baseline

B. To record, track, and provide traceability for change requests and decisions

C. To replace the project schedule

D. To authorize every change automatically

Correct Answer: B. To record, track, and provide traceability for change requests and decisions

Question 6

A corrective action is primarily intended to:

A. Address an observed deviation or nonconformance

B. Predict the project budget without data

C. Define the original project scope

D. Eliminate the need for verification

Correct Answer: A. Address an observed deviation or nonconformance

Question 7

If BAC = $1,000,000, EV = $400,000, and AC = $500,000, what is CPI?

A. 0.40

B. 0.80

C. 1.25

D. 2.00

Correct Answer: B. 0.80

Question 8

Which practice most directly improves interface management?

A. Allowing each organization to use undocumented assumptions

B. Assigning ownership and defining required information exchanges

C. Reporting only completed activities

D. Changing milestones without approval

Correct Answer: B. Assigning ownership and defining required information exchanges

Question 9

Using EAC = BAC ÷ CPI assumes that:

A. Current cost efficiency will continue for the remaining work

B. Schedule performance has no possible effect on cost

C. The project has no approved scope

D. Actual cost is always equal to planned value

Correct Answer: A. Current cost efficiency will continue for the remaining work

Question 10

Why should AI-generated project-control recommendations be reviewed by professionals?

A. AI outputs are guaranteed to be correct

B. Review is unnecessary when a dashboard exists

C. Outputs may reflect incomplete data, errors, or inappropriate assumptions

D. Professional accountability transfers automatically to the software

Correct Answer: C. Outputs may reflect incomplete data, errors, or inappropriate assumptions