Utility-scale PV · construction
Utility-scale solar construction with power-grade execution.
Scope described through interfaces, control written into the programme, documentation ready at handover.
- Project interfaces
- Inspection and test plan
- Handover documentation
Scope
Capabilities built around project interfaces
Each stage is described not only by a list of works but by its interfaces — with the main contractor, the equipment suppliers and the commissioning team. Those are what drive the programme.
Execution principles
Four principles that run the project
Not slogans but conditions we have to satisfy in order to hand over a scope with no open points.
-
Plan
Scope broken into stages with hold points and documentation requirements. The plan exists before mobilisation, not partway through the works.
-
Interfaces
Scope boundaries with the other contractors described and confirmed. An interface without an owner is the most common source of delay.
-
Control
Inspections and tests carried out to plan, with results recorded. An element closes once its check is confirmed.
-
Handover
Punch list closed, documentation compiled, scope handed over formally.
Projects
A technical portfolio, without decoration
A project card is a visual and a data table. We publish only values confirmed by project documentation and cleared for release.
See the project record formatQuality control
Control as part of running the project
Project controls, the inspection and test plan and interface management are one structure, not three separate documents.
-
Project controls
Scope, programme and reporting kept consistent, with a single source of progress information.
-
Inspection and test plan
Inspections mapped to stages of scope, with hold points before elements are covered.
-
Interface management
A register of interfaces with the other contractors, each with an owner on both sides.
-
Scope close-out
The punch list as part of the observation register, closed by confirmation rather than by declaration.
Documentation
Documentation ready at the moment of handover
We treat documentation as an output of the works rather than an administrative task performed afterwards. Handover then confirms the actual state instead of reconstructing site history.
| Control records | Inspection and test results linked to stages of scope and to the dates they were performed. |
|---|---|
| Observation register | One register covering inspections and the punch list, each item with an owner. |
| As-built documentation | A complete set of as-built documents maintained in parallel with the works. |
| Handover records | Scope handed over formally, with the status of open points stated unambiguously. |
What is handed over
What the client receives along with the scope
Handover is not only the completed works. It is the set of records the asset will later be operated and maintained from.
| As-built documentation | The actual state with deviations agreed with the designer marked up — not a copy of the construction design. |
|---|---|
| Control records | Inspection and test results tied to stages of scope, with date and inspector. Item by item, not in aggregate. |
| Observation register | The full punch-list history: item raised, how it was cleared, close-out confirmed by whoever raised it. |
| Route records | Cable runs and penetrations recorded so they can be found again without excavating the site. |
| Module register | Installed, rejected and damaged units listed — the evidence base for any warranty claim. |
| Handover records | Formal transfer of the scope with the status of open points stated unambiguously on the day of signing. |
The extent of this documentation is agreed before mobilisation. Adding requirements at handover always costs more than settling them at the start.
Contact
Describe the scope and the interfaces
Scope, expected interfaces and the schedule window are enough for us to assess a possible role in delivery.