Why Getting One Operating Answer Still Takes Three People

A leader asks why a job’s forecast changed. Accounting can show posted costs. The PM knows which changes are still being reviewed. The superintendent knows what happened in the field this week.

All three may have useful information. The question is what it takes to bring that information together, and whether the company has to repeat the same exercise next week.

Separate the number from the explanation

Start by writing down the exact question. “How is the job doing?” leaves plenty of room for different interpretations. “What changed in the remaining labor forecast since the last review, and what evidence explains the change?” gives the team something specific to investigate.

List the records needed for that answer. Then list the context needed to interpret them: timing, pending approvals, cost treatment, scope changes, and site conditions.

A useful answer needs both. A record can be accurate within its own system while still being incomplete for the decision someone is trying to make.

Follow the work required to assemble the answer

Document who is asked, what they look up, what they reconcile, and what they explain from memory. Note how current the information needs to be and which disagreements require human review.

That sequence becomes a practical brief for improvement. It might point to a missing system connection, an inconsistent identifier, a delayed update, or company knowledge that lives with one person.

Avoid starting with a dashboard layout. First agree what the answer means and which information can support it.

Connect one question well

Choose a recurring question with a clear decision attached. Agree the source records, the people who can validate the interpretation, and what happens when information is missing or contradictory.

For a hypothetical change-status question, the first useful result might connect the relevant request, supporting documents, current owner, and last recorded action. A reviewer should still be able to see where a status comes from and which details need confirmation.

The implementation should preserve uncertainty instead of quietly turning incomplete information into a confident-looking answer.

Build knowledge that stays useful

The Construction Intelligence Engine is the persistent intelligence layer we build through the Technology Partner Program. Its foundation begins during the Sprint and expands as we connect systems, workflows, documents, and operating knowledge.

The questions CIE can support depend on what has been connected and validated for your company. We develop those capabilities around real operating needs.

Bring an answer that currently takes a round of calls to a 20-minute discovery conversation. It is a useful place to begin discussing the information your team needs.

Keep exploring

Read our answer on connecting existing construction software for the practical next steps and related workflows.

The Lean Construction Institute offers a construction-industry perspective on the handoffs and waiting between teams. See its Focus on Flow guide.