Work Is Progressing. Is the Project Still on Plan?

-

Connect the master schedule and field actuals to schedule, cost and completion forecasts.

By Edward Kim | BuildNextSphere

Two engineers observe completed structural work and unfinished areas on the same construction site. AI-generated concept illustration.
Figure 1. Progress Today. Completion Tomorrow?
Source: AI-generated concept illustration; layout and editorial direction by Edward Kim | BuildNextSphere.
Note: Illustrative contrast between completed and remaining work, not a project forecast.

Progress is not the whole project position

Work can be visibly advancing while the project’s completion outlook deteriorates. Installed quantities describe completed work; expenditure describes money spent; certified payment describes an amount accepted through a payment process. None, by itself, explains whether the remaining work can finish within the current time and cost expectations. Project controls must connect the position today to the work still ahead.

PCI therefore asks a broader question than whether an AI tool can move activities on a schedule. What was the agreed basis? What actually happened? What has changed in the remaining work, and what decision is now required? A concise summary is useful only when the supporting dates, quantities, assumptions and records remain accessible.

A planner compares drawings and records beside a window overlooking construction. AI-generated concept illustration.
Figure 2. Look Beyond the Visible Work
Source: AI-generated concept illustration; layout and editorial direction by Edward Kim | BuildNextSphere.
Note: Documents are symbolic; no financial amount, earned value or payment certification is represented.

Two useful systems, a missing connection

In Edward’s UAE project experience, P6 supported planning and reviews of schedules, resources, quantities, progress and costs. A separate work-management system supported daily programmes and field updates. Both were useful, but their usefulness did not mean the records were already integrated. Progress reporting and P6 updating still required separate work.

That distinction matters when explaining BNS PIS. The historical system should not be credited with functions performed separately in P6. The development opportunity is to connect field actuals to the relevant schedule activities and control records, while retaining their source and review status. Reusing an update is valuable; quietly treating an unconfirmed update as an approved actual is not.

Two planners work with a shared drawing and separate records in a site office. AI-generated concept illustration.
Figure 3. Two Useful Systems, One Gap
Source: AI-generated concept illustration; layout and editorial direction by Edward Kim | BuildNextSphere.
Note: Conceptual historical separation; no P6 or legacy-system screenshot and no completed integration.

Compare the report with its underlying record

A separate overseas infrastructure experience reinforced this concern. Edward encountered a gap between submitted progress information and the underlying project position. Later support did not recover the project as intended. His subsequent reviews paid closer attention to comparing progress reports with the original P6 records. The lesson here is evidence reconciliation; the timing of management support is examined separately in MRI.

A mismatch should lead to a traceable question, not an immediate accusation. The reporting date, activity scope, progress rule or version may differ; the information may also be incomplete or incorrect. Record the discrepancy, retain the original evidence and identify who can resolve it. A forecast built on unexplained differences can look precise without being dependable.

Two engineers compare large drawings at a construction site. AI-generated concept illustration.
Figure 4. Check Behind the Summary
Source: AI-generated concept illustration; layout and editorial direction by Edward Kim | BuildNextSphere.
Note: A review illustration, not evidence of misconduct or an actual project report.

Connect actuals to the remaining work

The initial PIS direction is to bring in P6 schedule data and link it to field actuals captured through WEI. That requires more than transferring a percentage. Activity identifiers, actual dates, remaining work, constraints and the applicable data date need a consistent treatment. The approved baseline should remain distinguishable from the current update and from an alternative under review.

A longer-term direction includes PIS’s own overall scheduling capability. That is not an existing feature or a commitment that the initial connection will write changes directly into P6. Calculation location, exchange frequency and write permissions remain design matters. A forecast should explain its assumptions about remaining duration, resources and cost, including where those assumptions are still uncertain.

A project team reviews a plan and supporting folders around a table. AI-generated concept illustration.
Figure 5. Protect the Basis. Update the Outlook.
Source: AI-generated concept illustration; layout and editorial direction by Edward Kim | BuildNextSphere.
Note: The team-review scene illustrates keeping the baseline distinct from current updates; individual folders do not identify specific versions. No calculated schedule or software interface is shown.

Use one forecast-review record

Use one forecast-review record with six parts: baseline and data date; actuals and sources; current schedule; variance and remaining work; completion and cost assumptions; and the required decision. Check whether the compared values cover the same work and period. Where earned-value analysis is used, retain its defined measurement basis rather than substituting cash spent or certified payment amounts.

The review should end with a specific unresolved choice: confirm a field actual, revise a remaining-duration assumption, evaluate a resource option or seek authority for a change. A report that lists variances but leaves the next decision invisible has not completed the management connection. The proposed record supports that conversation; it is not a finished PIS dashboard.

Two reviewers discuss a physical building model. AI-generated concept illustration.
Figure 6. What Is the Forecast Built On?
Source: AI-generated concept illustration; layout and editorial direction by Edward Kim | BuildNextSphere.
Note: A proposed forecast-review concept; no numerical completion or cost forecast is supplied.

Calculate, review, then approve the response

Ordinary scheduling calculations can follow established logic automatically. Changing that logic, a baseline or a budget is a different action with its own authority. Future AI support could compare alternatives and identify assumptions worth challenging; people would assess feasibility and approve relevant changes. Calculation output is not an instruction simply because it is generated quickly.

PCI connects evidence to outlook. EWI uses that outlook to examine warning signals; CCI considers contractual implications without treating a schedule impact as automatic entitlement; MRI addresses support beyond site authority. Start with one forecast on your project. Can another reviewer identify the baseline, trace the actuals and understand the assumptions behind the completion date? If not, that connection deserves attention before another confident summary is issued.

Three professionals compare construction plans and records. AI-generated concept illustration.
Figure 7. Calculate. Review. Decide.
Source: AI-generated concept illustration; layout and editorial direction by Edward Kim | BuildNextSphere.
Note: Illustrates human review of alternatives; no AI recommendation, EOT award or baseline approval is implied.

Sources

No external sources cited. The experience account is based on Edward Kim’s direct project experience and subsequent clarifications.

Basis of This Article

The article distinguishes historical P6-based project controls from the separate UAE work-management system. The overseas infrastructure experience is anonymised. P6 integration and PIS scheduling are development directions; the review aid is proposed. No new performance figure or legal conclusion is claimed.

Related Reading

Explore more from BuildNextSphere:

• Why Build BNS PIS?

• When Projects Don’t Go to Plan: What Are We Missing?

• Why Do Projects Fail to Execute the Plan?

• Between the Plan and the Site: How Can AI Support Project Execution?

BuildNextSphere

BuildNextSphere connects Development, Technology & Project Intelligence through practical, experience-informed content.

Explore BuildNextSphere’s development direction and discover more insights through the channels below.

About the Author

Edward Kim is the Founder of BuildNextSphere. He draws on his experience with overseas construction projects to share practical insights from field operations, project delivery, and IT-enabled working systems. Through BuildNextSphere, he explores how people, technology, and real project conditions can help turn plans into action and support better project outcomes.

Content & IP Notice

This article and related materials are prepared by BuildNextSphere. Unless otherwise stated, the original structure, wording, diagrams and visual materials are the intellectual property of BuildNextSphere and Edward Kim. BuildNextSphere, its logo, tagline and brand assets are part of the BuildNextSphere brand identity. Unauthorised reproduction, modification, redistribution or commercial use is not permitted without prior written consent. Third-party names, technologies and references remain the property of their respective owners. General management principles are not claimed as proprietary inventions.

Comments

Post a Comment

Popular posts from this blog

Why Better Construction Technology Still Needs Better Project Execution

-
Image
  Practical lessons on people, cooperation, and making work ready. By Edward / BuildNextSphere Better technology helps teams visualize buildings, simulate construction sequences, and share information quickly. Yet construction projects can still fall behind. A clear plan does not automatically put the right drawing, material, decision, or support in the hands of the people doing the work. The useful question is what prevents a planned activity from becoming completed work. 01. What the Available Evidence Shows A 2025 CoST analysis undertaken with the World Bank reported delays in roughly 70% of infrastructure projects with available delay information. The wider dataset contained 480 projects, with substantial missing information. The finding describes the reported sample; it is not a global construction failure rate. Source: CoST (2025). Delay information was unavailable for 186 of 480 projects. Separately, the European Court of Auditors reported an 82% increase in the combined ...
Read more

When Projects Don’t Go to Plan: What Are We Missing?

-
Image
An introduction to Project Intelligence: connecting field information, decisions and action. Figure 01. The Plan Is Ready. Why Is the Work Waiting? Source: AI-generated concept illustration; layout and editorial direction by Edward | BuildNextSphere. Note: A hypothetical scene illustrating the distinction between scheduled work and confirmed work readiness. It is not a photograph of an actual project. 01. Tomorrow’s Work Is Planned. Is It Ready? A planned start Imagine a construction project where Area A’s concrete pour is scheduled for tomorrow. Reinforcement is reported complete, but the inspection is unconfirmed. Area B also needs the pump, and nobody has checked whether the delivery route will remain available. The question behind the delay The schedule expresses an intention; it does not confirm every starting condition. Ask what prevents the activity from proceeding, who can resolve it and what evidence would establish readiness. This is a hypothetical example, not an ex...
Read more

AI in Construction: What Makes a Tool Useful on Site?

-
Image
Connecting digital assistance with the people and conditions needed to move work forward. By Edward | BuildNextSphere Figure 01. The Document Is Ready. Is the Work Ready? Source: AI-generated concept illustration; layout and text by Edward | BuildNextSphere. 01. A Clear Document Does Not Mean the Work Is Ready A meeting can end with a clear summary while the work remains blocked. The drawing may be current, but equipment is allocated elsewhere, an inspection is outstanding or the preceding activity is unfinished. Getting the information onto a page and getting a team ready to act are connected tasks, but they are different. In my own work, AI has helped with meeting records, information organisation and correspondence drafts. These uses can create more room for review and response. The next question is how that assistance reaches the people coordinating actual work. This article focuses on AI and the digital working systems around it. 02. Match the Support to the Task Differen...
Read more