A construction company recovers 10%+ of revenue lost to project gaps

A construction company recovered at least 10% of its annualised revenue projection after the project made hidden leakage visible.

The leakage did not come from one dramatic failure. It accumulated through duplicated work, delayed projects, continuing equipment and labour costs, missed changes and charges that were difficult to trace back to the event that created them.

We delivered a structured project knowledge and control system that connects correspondence, local requirements, people, project events, timelines, costs and source documents. After implementation, the recovered revenue was at least equivalent to 10% of the company's annualised revenue projection. The claim needs the approved denominator, measurement period and attribution before publication, but the business outcome is clear: better structure helped the company capture more of the revenue it was already planning to deliver.

Client background

Our client is a large construction company delivering public bridge contracts, housing developments and other multi-site projects. The work carries different local requirements, contract rules, milestones, teams, weather exposure and commercial decisions.

The company did not need a generic dashboard. It needed a way to see where expected revenue was being lost in the ordinary movement of project work and to give the responsible people enough evidence to act.

Business challenge

Revenue leakage appeared in the gaps between systems and teams:

• a new project repeated research completed on a similar job;
• a local requirement was discovered late;
• a weather delay moved work while rental and labour costs continued;
• a change or disruption was not connected to its extra charge;
• project email contained the decision, but the timeline and cost view did not;
• and knowledge remained with the person who had worked on the earlier project.

Each gap may look small. Together they reduce the amount of planned work the company can capture. Leadership could see that expected revenue and actual capture were diverging, but needed a connected operational record to understand why.

Implementation

We made project communication and control part of one structure. Email can be linked to the project, site, contract, work package, owner and next action. Requirements, decisions and documents remain attached to their source and date. A new project can retrieve relevant earlier work without treating it as current approval.

Retrieval-augmented generation, or RAG, searches relevant source documents before answering a project question. City A, Project X can therefore provide a source-backed starting point for City A, Project Y. That reduces duplicated research while preserving the context that makes the earlier work safe to verify.

The project timeline connects milestones, dependencies, weather and disruption events to equipment rental, labour exposure, changes and extra charges. Project leaders can see what happened, what was affected and which commercial record followed.

The company-wide structure also supports people and knowledge transfer. HR and delivery teams can find the experience connected to a prior project or work package, reducing the chance that a useful solution has to be rediscovered from scratch.

Why it was difficult

The 10%+ outcome is an attribution problem as well as a systems problem. Revenue recovery can be affected by many commercial and operational decisions. The system must expose the events and actions that contributed to the result without claiming that every recovered amount came from one feature.

The construction context makes this harder. Local requirements differ, weather is variable and contract treatment depends on the project. The system had to connect the facts while leaving current professional and contractual judgement with the responsible people.

Value delivered

• Revenue leakage was reduced by at least the equivalent of 10% of annualised revenue projection after implementation, subject to confirmation of the measurement basis.
• Duplicated research and knowledge gaps became easier to identify and control.
• Weather and disruption events could be connected to timeline, rental, labour and charge records.
• Project email, decisions and source documents remained available in the relevant context.
• RAG made relevant prior project knowledge easier to retrieve.
• Company-wide knowledge transfer reduced dependence on individual memory.
• Commercial teams gained a clearer basis for reviewing missed charges, changes and delay exposure.

The important result is not a claim that software creates revenue by itself. It is that structure made operational leakage visible enough for the company to recover more of the revenue already in its plan.

What this means for your business

If your forecast is healthy but the business keeps failing to capture the work inside it, look for the gaps between operations, evidence and commercial control. Revenue leakage often hides in repeated work, late decisions, missed changes and costs that have no connected cause.

The same pattern applies to property, insurance, professional services and lending. Connect the event, owner, evidence and charge so management can see where expected value is escaping and act before the period closes.

Related: Project controls · Knowledge systems · Construction companies