Fragmentation isn't an IT problem. It's a balance sheet problem.
Christian Pallaria, Founder & CEO · August 2026 · 5 min read
33.4%
of contract budget, on average, sitting in dispute on distressed projects
Every system in construction works exactly as it was designed to. The inbox delivers the emails. The RFI register logs the question. The schedule tracks the program. Each one works in isolation.
What none of them does is talk to each other, because that was never seen as a problem.
The mechanics are almost boring
Benchmarking across more than 1,300 projects found close to 800 RFIs on an average job. Each question consumes drafting, routing, research, and response time, while many never receive a formal answer.
When requests run through email without a shared log or clear accountability, questions vanish, duplicate requests appear, and answers fail to reach the crew that needs them. The cost emerges later as idle trades, resequencing, or a claim that nobody can fully substantiate.
Questions that vanish
RFIs move through inboxes without a shared due date, owner, or complete answer trail.
Decisions with no home
Scope changes and approvals remain in email until the missing record has already cost time.
Manual reconciliation
A change must be re-entered in the schedule, budget, and reporting systems.
One more silo
Another point solution adds its own login and export format to an already fragmented stack.
This is not a be more organised problem
The pattern is too consistent across too many projects to be explained by one person dropping the ball. Teams operate inside systems that record only one slice of the project, leaving people to rebuild the connections manually.
“The tools didn't fail. The gaps between them did — and those gaps are the cost centre nobody is tracking.”
Why buying another tool makes it worse
A new RFI tool or dashboard becomes another system with its own login, export, and data boundary. The useful distinction is whether software solves one task or connects the work already spread across the project.
The difference becomes visible when an approved change updates the schedule and budget together, instead of relying on someone to repeat it in three places.
What this means for how you run the business
Executives need to see exposure before it becomes a claim. WisyPlan reads across email, documents, schedules, and site data to surface unanswered work while teams keep their current tools. Explore PMO Intelligence or see how WisyPlan works.
Fragmentation feels operational until it becomes a balance sheet number. The earlier the links are visible, the more chance a team has to act before that happens.
Common questions
Yes. On distressed projects, the average sum in dispute runs to 33.4% of the contract budget, while scope change drives a substantial share of claims. The gaps between systems become a balance sheet cost when decisions and documents cannot be found in time.
Construction firms already use many disconnected tools. Another point solution adds depth in one place but creates another login, export format, and data boundary. A connecting layer must work across the systems the team already uses.
Industry benchmarking found close to 800 RFIs on an average project. Each can consume hours of drafting, routing, research, and response time, while unanswered questions can lead to idle trades, resequencing, and claims that are difficult to substantiate.
WisyPlan connects to project email, documents, schedules, and site data so related records can be treated as one thread. It surfaces unanswered items and delivery risk while teams continue using their existing systems.
Common questions
Yes. On distressed projects, the average sum in dispute runs to 33.4% of the contract budget, while scope change drives a substantial share of claims. The gaps between systems become a balance sheet cost when decisions and documents cannot be found in time.
Construction firms already use many disconnected tools. Another point solution adds depth in one place but creates another login, export format, and data boundary. A connecting layer must work across the systems the team already uses.
Industry benchmarking found close to 800 RFIs on an average project. Each can consume hours of drafting, routing, research, and response time, while unanswered questions can lead to idle trades, resequencing, and claims that are difficult to substantiate.
WisyPlan connects to project email, documents, schedules, and site data so related records can be treated as one thread. It surfaces unanswered items and delivery risk while teams continue using their existing systems.
Founder & CEO, WisyPlan