Governance is often associated with meetings, reporting and approval processes. When applied poorly, it can become an additional administrative burden that slows delivery without improving outcomes.
Good governance has a different purpose.
It creates clarity around objectives, responsibilities, decisions, risks and evidence. It helps project teams identify problems earlier and resolve them at the appropriate level. It also gives clients confidence that progress is being measured against meaningful delivery outcomes rather than activity alone.
For retrofit and construction programmes, better governance should make delivery more efficient, not more complicated.
Governance begins with clear outcomes
A programme should begin with a shared understanding of what successful delivery means.
Completion cannot be measured only by the number of properties installed or the amount of funding spent. Wider outcomes may include:
- Compliant and technically suitable installations
- Improved building performance
- Effective ventilation
- Controlled moisture risk
- Positive resident experience
- Complete project records
- Reduced defects and remedial work
- Safe and coordinated delivery
When these outcomes are not defined clearly, different organisations may work towards different interpretations of success.
The client may focus on programme volume. The designer may focus on producing information. The installer may focus on completing measures. The Retrofit Coordinator may focus on compliance and lodgement.
Governance should connect these activities into one coordinated delivery objective.
Responsibilities must be understood
Retrofit programmes often involve several organisations and professional roles. The existence of defined roles does not automatically mean the boundaries between them are understood.
Problems commonly arise where responsibility for a decision is assumed rather than agreed.
Examples may include:
- Who confirms that the survey information is sufficient?
- Who decides whether a standard detail is suitable for a particular property?
- Who manages design changes discovered during installation?
- Who confirms that ventilation requirements have been completed?
- Who accepts incomplete or alternative evidence?
- Who communicates technical changes to the site team?
A clear responsibility structure reduces gaps, duplication and delayed decisions.
This can be achieved through a concise responsibility matrix rather than a lengthy management procedure.
Information must reach the people who need it
A programme may contain extensive documentation and still suffer from poor information management.
The important question is not how much information exists. It is whether the current, approved and relevant information is available to the person making the decision or completing the work.
Site teams should not have to search through several systems to identify the correct construction detail. Designers should receive feedback when site conditions differ from the assessment. Programme managers should understand which technical issues could affect delivery dates.
Effective governance establishes:
- Where approved information is held
- How revisions are identified
- How changes are communicated
- How superseded information is removed from use
- How site queries are raised and answered
- How final records are retained
These controls can remain simple, provided they are consistently followed.
Decisions should be made at the correct level
Not every issue needs senior approval. Equally, some decisions should not be made informally on site.
Governance should define which matters can be resolved by the delivery team and which require technical, commercial or client review.
A minor adjustment to a non critical fixing arrangement may be managed through an agreed site process. A change that affects moisture behaviour, fire performance, ventilation or the compatibility of measures requires appropriate technical review.
This distinction supports faster decision making while protecting important technical outcomes.
Risks should lead to action
Risk registers are useful only when they influence delivery.
A meaningful risk process identifies the issue, its potential consequence, the required control, the responsible person and the date by which action is needed.
For example, a programme containing several solid wall property types may identify uncertainty about wall construction as a technical risk. The control may include targeted opening up surveys, property archetype reviews and approval of suitable details before installation.
The risk has then informed the work rather than remaining as a statement in a report.
Resident experience is part of programme governance
Retrofit takes place in people’s homes. Access, communication, sequencing, temporary disruption and handover all affect the success of the programme.
Resident issues should not be separated from technical and programme management.
A missed appointment may affect the sequence of work. Poor explanation of ventilation controls may affect future building performance. An unresolved complaint may reveal a recurring technical defect.
Governance should create a route for resident feedback to reach the people capable of acting on it.
Use performance information intelligently
Programme reporting should show more than completed property numbers.
Useful measures may include:
- First time quality performance
- Open technical queries
- Defect type and frequency
- Time taken to resolve design issues
- Evidence accepted at the first review
- Resident access failure rates
- Remedial work by property type or measure
- Progress against design and installation readiness
These indicators help the team understand the health of the programme, not only its output.
The AISK perspective
AISK supports governance that is proportionate, practical and connected to delivery.
The aim is not to add more layers of checking. It is to make responsibilities visible, decisions timely and information reliable.
Better governance improves programme delivery because it reduces uncertainty. It helps teams identify what matters, understand who is responsible and act before a manageable issue becomes a repeated programme failure.
