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

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 explanation for every delay: design changes, funding and physical conditions can create other problems.

**Figure 02. Planned Work, Unconfirmed Conditions**
**Source:** AI-generated concept illustration; editorial direction by Edward | BuildNextSphere.
**Note:** A hypothetical construction scenario showing unconfirmed inspection and access conditions, with the same concrete pump requested by two work areas.

02. Project Intelligence Starts with a Clear Distinction

Plan, progress and readiness

The plan describes what should happen, when and how. Progress describes completed work against that plan. Readiness asks whether the next activity has what it needs. A reinforcement completion report answers a progress question, not whether the inspection, pump allocation and access are confirmed.

A working definition

BuildNextSphere uses Project Intelligence as a working definition: interpreting plans, field facts, constraints, resources and changes together to support responsible decisions and learn from results. It is not an official standard or a validated software product. A dashboard may help; people must still understand uncertainty and take responsibility.

Its usefulness depends on whether the team recognises what remains uncertain and knows which action is needed, rather than how much information a screen displays.

**Figure 03. Connecting Plans, Progress and Readiness to Decisions**
**Source:** AI-generated concept illustration; editorial direction by Edward | BuildNextSphere.
**Note:** Illustrates BuildNextSphere’s working definition of Project Intelligence through planning, progress observation, readiness checks and human judgement. It does not represent an official standard or a validated software platform.

03. Build a Shared View of One Activity

**Figure 04. One Activity, One Shared Record**
**Source:** Framework proposed by Edward | BuildNextSphere.
**Note:** A proposed structure for an activity-level record. Keep unconfirmed information explicit and distinguish observations, proposed responses and approved instructions. Adapt the checks to the activity and retain applicable project procedures and authorised reviews.

Connect the record to the work

Identify the activity, work area and intended start. Record the current status, source and last confirmation. For each missing condition, add the affected work, required decision, action owner, approver where needed, deadline and evidence for closure. Collect what helps resolve the problem, not every available data point.

Keep uncertainty visible

An empty inspection field means “not confirmed,” not “nothing is wrong.” A pump booking needs a time period. Yesterday’s route check may not establish tomorrow’s access. Keep conflicting records visible until the responsible person resolves them.

Check conditions appropriate to the activity

Checks must suit the activity, including relevant resources, permits, utilities, access, quality, safety and handover needs. This is not a complete checklist or permission to start. Applicable project procedures and authorised reviews remain necessary.

An actionable entry

“Access unconfirmed” becomes actionable when someone owns the route check, knows its deadline and understands which delivery depends on it. Distinguish observations, proposed responses and approved instructions.

04. Turn Missing Conditions into Decisions and Support

Compare options, not just requests

For the pump conflict, compare the sequence in Areas A and B, effects on later activities and feasible alternatives. Moving a pour may disrupt another crew; another pump may be unavailable or unsuitable. These are options to investigate, not automatic solutions.

Give each action an owner

Assign an owner and confirmation time to each condition. The person reporting a status may not have authority to approve action. Urgency is not approval, and resequencing does not remove inspection or safety requirements. Escalate decisions beyond site authority through the project’s arrangements.

Connect meeting rhythms

Daily coordination can address immediate conditions; weekly reviews can anticipate recurring conflicts and resource needs. Escalation should specify the decision, timing and consequences of waiting. The person raising the issue should see the response.

**Figure 05. From Information to Verified Action**
**Source:** Framework proposed by Edward | BuildNextSphere.
**Note:** A proposed coordination process linking confirmed facts, option assessment, authorised decisions, assigned actions and result verification. Adapt responsibilities and review timing to the project. Required inspections and safety approvals remain applicable when work is resequenced.

05. Check What Changed, Then Update the Plan

Close the condition, not the message

An inspection request is not a completed inspection. A pump allocation is not proof of arrival. Verify readiness, record what happened and keep unresolved conditions visible. Update forecasts through the agreed process rather than silently rewriting the original commitment.

A lesson from field experience

On an overseas underground project, I helped develop and introduce a mobile work-management system linked to control-room coordination. Field and equipment information supported the arrangement, but people still had to interpret it and organise responses. This anonymous experience is separate from the hypothetical pour; it is not measured evidence of improvement or a historical AI system.

Learn from a defined record

For future trials, define measures and a baseline. Record staffing, scope and site changes before attributing better results to a tool.

Decision waiting time or actions reopened after completion could provide useful measures. Agree what each measure means before comparing results; a changed staffing level or work scope may explain an apparent improvement.

06. Eight Areas, One Connected Project

A map for the series

BuildNextSphere’s planned series explores eight connected areas. These are topics for investigation, not capabilities already demonstrated by a complete platform.

PI-01 & PI-02

Project Execution & Controls connects plans, progress and forecasts. Resource & Productivity Management examines whether people, equipment and materials meet activity needs.

PI-03 & PI-04

Procurement & Supply Chain Management connects deliveries to work needs. Risk, Early Warning & Recovery examines developing conditions, their impacts and possible responses.

PI-05 & PI-06

Contract & Commercial Management connects field events to contractual review under the applicable contract. Document, Communication & Knowledge connects sources, decisions, actions and reusable records.

PI-07 & PI-08

Multi-Project Governance & Executive Management addresses leadership attention and support. EPC Delivery & Project Lessons connects lifecycle handovers and lessons for future projects.

Connections without losing context

The aim is not to send every issue everywhere, but to give the right person enough context to act.

An activity may need procurement help, contractual review or management support. Preserve the context when passing it on. Later articles will examine these connections and the limits of standardised records across different project sizes, stages and operating conditions.

07. Start with One Activity at Your Next Meeting

A small, practical start

At your next meeting, choose one stalled activity. Record the facts, missing condition, affected work, decision, owner, deadline and verification method. Check that participants recognise the same situation. Paper or a spreadsheet may be enough; responsibility need not wait for new software.

The direction ahead

BuildNextSphere explores how people can interpret conditions and make decisions they can act on and verify. BNS Project Intelligence Sphere Platform may eventually help identify missing or conflicting information, but remains a development direction requiring human review and authority. Does the team know the next action—and check that it happens?

Closing message

Connect the facts. Assign the action. Verify the result.

Shared facts and verified action — **Figure 07. Connecting Plans, Progress and Readiness to Decisions**
**Source:** AI-generated concept illustration; editorial direction by Edward | BuildNextSphere.
**Note:** Illustrates BuildNextSphere’s working definition of Project Intelligence through planning, progress observation, readiness checks and human judgement. It does not represent an official standard or a validated software platform.

Read the article as a PDF

Sources

No external sources cited.

Basis of This Article

This article presents Edward Kim’s practical perspective and BuildNextSphere’s proposed Project Intelligence framework. The concrete-placement scenario is hypothetical. The anonymous underground-project account draws on Edward’s direct experience and is not an independently evaluated case study.

The definitions, records and workflows presented here are proposals for discussion—not official standards, complete operating procedures or evidence of a validated software platform. Their application requires review against the project’s conditions, applicable procedures and authorised responsibilities.

Image credits and explanatory notes are provided beneath each figure.

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.