Make shared delivery easier to manage

Water and infrastructure delivery often depends on several organisations, functions and systems working together. The work may be shared, but the information needed to manage it is often not.

Different teams can hold their own versions of programme, commercial, operational or assurance information, structured in different ways and updated at different times. Information is then passed between organisations through spreadsheets, emails, manual uploads and locally managed reporting processes.

That creates effort on both sides. Teams spend time checking, reformatting and reconciling information before they can use it, while differences in definitions, timing or ownership can make it difficult to establish a consistent view of what is happening.

The problem becomes more visible as delivery grows. More projects, partners, regions and reporting requirements mean more interfaces to manage, and manual processes that once seemed manageable can become a significant source of delay, duplication and uncertainty.

Better integrated working is not about forcing every organisation onto the same system. It is about making the information and processes between them work well enough that people can coordinate delivery without constantly managing the gaps.

Teams working across organisational boundaries should be able to rely on the information they receive without first having to rebuild, reformat or reconcile it.

The systems used by different organisations do not need to be identical, but the information moving between them should be consistent, well defined and available when it is needed.

Shared reporting should work from agreed data and definitions rather than parallel versions maintained by different teams. Handoffs between organisations should be supported by repeatable processes, with clear ownership of what is produced, checked and passed on.

Where information needs to move between systems, that movement should be automated where practical rather than dependent on manual uploads and spreadsheet workarounds.

As delivery grows, adding new projects, partners or reporting requirements should not create the same increase in coordination effort. The result is a more reliable shared view of delivery, with less time spent managing interfaces and more attention on the work those interfaces are there to support.

The exact solution depends on where the boundaries sit and how information currently moves between organisations.

We start by understanding what each party needs to provide, receive, review or act on, which systems hold that information, and where manual handoffs or inconsistent structures are creating unnecessary effort.

That can mean defining shared data structures and reporting requirements, connecting existing systems, or creating a governed layer that brings information together without requiring every organisation to work in the same platform.

Where information is exchanged repeatedly, we can automate the movement, transformation and validation of data between systems. Where the challenge is a shared process rather than a data transfer, we can improve the workflow around submissions, reviews, approvals and assurance. Reporting can then work from the same underlying information, while applications or workflow tools can be introduced where established systems do not support the shared process well enough.

The aim is not to centralise everything. It is to make the interfaces between organisations reliable enough that shared delivery does not depend on people continually reconciling systems, spreadsheets and local processes.

Integrated working often sits alongside wider project, transformation and operational activity.