Utility-scale solar construction

From open site to finished solar plant.

We mobilise onto the site, organise the work fronts and deliver the scope to design — through to handover documentation.

01
Utility-scale projects, not rooftop installations
02
Working inside the investor’s or main contractor’s structure
03
Scope and interfaces agreed before mobilisation

How we run a project

Four stages that keep delivery in order

The same path on every project, whatever its size, so the client knows what to expect at each stage.

  1. 01

    Mobilisation

    Taking over the work front, setting up site facilities and haul roads, agreeing site access rules and the scope split with the other contractors.

  2. 02

    Execution

    Work delivered to the construction design and the programme, with continuous front coordination and progress reporting.

  3. 03

    Quality control

    Inspections at the stages that close out an element, checklists tied to the scope, and observations recorded and closed.

  4. 04

    Handover

    Punch list closed out, complete as-built documentation, and formal handover of the scope.

Projects

We present projects only on confirmed data

Project cards are filled in once we have data from the client and clearance to publish it. No rounded capacities, no borrowed photography.

See how we present projects

Safety and quality

Quality comes from organisation, not from a final inspection

Scope broken into stages, inspections written into the programme, and one observation register. All of that is set up before work starts, not after.

See our approach to safety and quality
  • Scope planning

    The scope split into stages and work fronts, with control points agreed before mobilisation.

  • Inspections and checklists

    Checklists tied to the type of work, completed at the closing stage rather than from memory at the end.

  • Observation workflow

    Inspection findings and punch-list items kept in one register, each with an owner and a date.

  • Documentation

    Documentation produced alongside the work, so handover is not a reconstruction of site history.

Built for utility scale

What actually matters on a large project

On a large-footprint plant the technology is rarely the problem. Coordination of work fronts, documentation and schedule predictability are.

Coordination
Agreed interfaces with the other contractors and a clear scope split where the works meet.
Documentation
As-built documents produced in parallel with the work, ready at handover.
Programme
Progress reported against the programme, with risks flagged early.
Reporting
An agreed report format and frequency, so the client never has to chase the status of the works.

Before mobilisation

What is worth having ready before the first plant arrives

The things whose absence most often pushes a start date back by weeks. Not all of them are ours — which is exactly why we raise them early rather than on site.

  1. Construction design

    The version we will actually build to, with an unambiguous revision number. Two versions in circulation means rework.

  2. Setting out

    Row axes and control points marked on the ground. Without them piling has nothing to start from.

  3. Site access

    A haul road that can take heavy transport, and an agreed entrance. The surprise is usually not the road but its bearing capacity.

  4. Scope split

    Who owns fencing, who owns roads, who owns drainage. An interface without an owner is the most common cause of standing time.

  5. Delivery schedule

    Dates for structures and modules. Work fronts are planned around deliveries, not the other way round.

  6. Facilities and utilities

    Space for site facilities, storage and waste collection. Agreed once, at the start.

If one of these is not in place yet, that is not an obstacle to talking — it is the reason to start.

Contact

Describe the project — we will answer specifically

Location, intended scope and schedule window are enough for us to assess a possible role in delivery.