Module 1 · Unit 5 · 8 minutes
The full narrated video will be added here. The complete transcript is available below.
Clean heat projects are delivered by a chain of people and organisations, mostly not by one team working in isolation. The client defines the need. Engineers turn that need into technical requirements. Suppliers provide products. Contractors install and test the system. Quality and compliance functions verify that requirements have been met. Operators and maintainers need the right information to run the asset safely and effectively. Finally, the end user can use the product.
The important point is that the project outcome depends on the quality of connections between these roles. Every interface can create risk if information is incomplete, late or misunderstood. The goal is not more meetings, it is clear ownership, timely evidence and shared understanding.
A small communication gap can quickly become a significant project problem. A gap can cause rework, delays and additional cost. It can also lead to safety or quality risks at interfaces, as well as a loss of trust between stakeholders. Good communication is therefore not an administrative extra; it is a fundamental part of delivery control.
For example, a design change that is not passed to the installer may arrive after materials have been ordered or work has started. If evidence is not captured as the work happens, the project may be technically complete but unable to demonstrate compliance. And if different stakeholders have different ideas of what "ready" means, commissioning or handover can fail even when the physical installation looks complete.
Beyond the immediate delivery impacts, unclear requirements and poorly defined responsibilities can also affect the overall performance of the heating system once it is in operation. If project requirements are not communicated clearly, the resulting tasks may not be completed as intended, and the system may not deliver the expected functionality or performance. This is particularly important in more complex clean heat projects, such as those involving sector coupling, smart energy integration, or multi-functional systems that move beyond standard heating configurations. In these cases, well-managed interfaces are essential to ensure that all system functions operate together as intended.
The practical lesson is simple: whenever information changes, the people who depend on that information need to know what changed, what the impact is, who owns the next action and what evidence is required. By ensuring that requirements, responsibilities and interfaces are understood across the entire value chain, projects are more likely to deliver not only on time and within budget, but also with the intended long-term operational performance.
Each role has a distinct responsibility, but no role can deliver the project outcome alone. Successful clean heat projects depend on collaboration and clear communication between all participants throughout the project lifecycle.
The client and the engineer work together to define the project objectives, requirements and constraints. In many projects, the client does not yet know exactly what type of heating system is possible, or which solution best meets their needs. The engineer therefore helps translate the client's objectives into technical requirements, explains the available options and develops a solution that is technically, economically and operationally suitable. As the project progresses, the engineer also manages technical changes and coordinates the interfaces between the different project participants.
The supplier does much more than simply deliver equipment. Working closely with the engineer, the supplier helps identify suitable technologies, provides technical information, product certifications and installation guidance. As projects become more complex, for example when integrating renewable technologies, sector coupling or advanced control systems, the level of collaboration between the engineer, supplier and installation teams increases significantly. In many cases, equipment suppliers also provide their own installation specialists, who must coordinate closely with other contractors to define both the physical and digital interfaces. Without clear communication, coordinated planning and well-defined priorities, these interfaces become a major source of project risk.
The installer or contractor transforms the design into the physical installation and should raise technical issues or deviations as early as possible. Where specialist subcontractors are involved, for example for electrical works, controls, pipework, insulation or commissioning, they also need to communicate effectively with each other to ensure that their work integrates correctly with the overall system.
Quality and compliance are not the responsibility of a single individual or a separate team. Every participant is responsible for completing their own work to the required standard and for providing the appropriate evidence that it has been completed correctly. The engineer typically has an important coordinating role by reviewing how these individual contributions fit together and ensuring that the completed system meets the agreed project requirements. Depending on the project, independent inspections or third-party assessments may also be required, but quality is primarily achieved through good communication and responsibility across the entire delivery team, not by relying on a final inspection.
The operator or maintainer confirms that the completed system can be operated and maintained safely and efficiently over its lifetime.
Finally, the end user experiences the outcome of the project.
The key message is that interfaces matter just as much as individual responsibilities. A role can perform its own task correctly, but the project can still fail if information, responsibilities or changes are not communicated clearly to the next person in the value chain. The more complex the project is, the more important it becomes to manage these interfaces effectively.
This slide highlights a simple but important principle: if we want to minimise errors, we should minimise unnecessary interfaces between roles.
The first example shows a value-chain of a new 5GDHC system for an energy provider. In the original model, there are eight separate roles involved, from the client through to the end user. The revised approach reduces this to six roles by combining the client with the operator or maintainer. Also, in this example the engineer takes over the quality and compliance function.
The second example shows a value-chain of a new renewable heating system for a municipal swimming pool. Here, the number of roles is reduced from eight to three. The client, so the municipality has also the compliance function, is at the same time the operator or maintainer and as well is the end user. This can make communication, decision-making and accountability much clearer.
However, it is not always possible to minimize interfaces. Where interfaces are necessary, they need to be well managed through clear communication, defined responsibilities and appropriate evidence.
So the key message is: fewer interfaces generally mean fewer opportunities for communication errors, but the interfaces that remain must be clearly defined and actively managed.
Evidence should be designed into the project from the beginning. We should not wait until the end and then try to reconstruct what happened. Each role should know what it must provide, when it is needed and who checks it.
A strong evidence trail connects the requirement to the activity, the record of what was done, the review of that record and the final acceptance. Each role needs to understand what evidence it must provide, when it is needed and who will rely on it.
Good evidence is clear, traceable, timely, attributable and accessible. This makes assurance easier and reduces the risk of late surprises during inspection, commissioning or handover.
A practical communication flow chart can be built around five steps.
First, align on scope, roles, interfaces and acceptance criteria. Second, prepare by sharing the information needed for the next activity. Third, de-escalate in advance by addressing changes, deviations and risks early. Fourth, verify both the work and the evidence against the agreed requirement. Finally, hand over not only the asset, but also the records, outstanding actions and operational knowledge.
The rule behind all five steps is: no silent assumptions. If a change affects another role, make that dependency visible before the next activity relies on outdated information.
To summarise: Clean heat projects are delivered through a one value chain of interdependent roles. Clear communication at every interface ensures that requirements, changes and evidence move with the work, helping teams avoid errors and deliver safely, compliantly and efficiently.