---
id: KB-CS-029
url: https://app.codecontract.io/help/manufacturing/renewables-and-energy-efficiency-projects
idioma: en
categoria: sector-industria
subcategoria: renovables
audiencia: usuario
nivel: intermedio
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-CS-017, KB-CS-006]
citadoPor: [KB-CN-002, KB-CS-037]
---

# Renewables and energy efficiency

_Subsidised projects, many subcontractors, and a claim submitted months later._

**Responde a:** grant justification documentation · solar installation documentation · subcontractors on renewable projects · installation certificate and commissioning

A renewables project combines two things already hard on their own: construction with subcontractors, and a grant claim submitted when the work finished months ago and nobody remembers the detail.

## The three layers

| Layer | Module | When it is needed |
| --- | --- | --- |
| Subcontractors and their documentation | Trackline | During the works |
| Contract and client sign-offs | Consigne | At start and handover |
| Evidence of execution | SmartCheck | During, not at claim time |

> [!IMPORTANT]
> A grant claim is prepared during the works or not at all. Photos, delivery notes and certificates gathered afterwards have two problems: half are missing, and what exists has no reliable date. Certifying as it happens costs minutes; reconstructing later costs weeks and sometimes cannot be done.

## Frameworks cited

Electrical and installation regulations, commissioning and registration requirements before the competent authority, the conditions of each grant call, and — where there are works — contractor safety coordination. Justification requirements are set by each call; read it at the start, not at the end.

> [!WARNING]
> Grant calls tend to require documentation in very specific formats, on deadlines that are not extended. Losing a grant over a piece of paper is the most expensive way to learn this.

> [!NOTE]
> If you run many similar projects, the claim is nearly identical each time. Built as a process, it fills itself in as the work progresses.

**Can I give the client access during the works?**

Yes, read-only and scoped to their project.

**What about the evidence the call requires?**

Certify it as it happens, not at the end.

**Does it work across several sites?**

One case per project, with its subcontractors inside.

## Ejemplos

**An installer loses part of a grant for lack of execution evidence.**

- Certifies photos and delivery notes during the works
- Builds the claim as a process from the start

→ The next project reaches claim time with everything gathered and dated, with nothing reconstructed.

**An installation's documentation scatters after commissioning.**

- Gathers it into the installation's file

→ Whoever maintains it finds what went in.

**Calendar inspections get forgotten.**

- Warns about each due date in advance

→ The calendar keeps itself.

**The client asks you to evidence a period's output.**

- Checks the records for that date

→ You answer from the archive.

**A component is replaced and the documentation stays the same.**

- Updates the file with every change

→ The paper describes what is installed.

**A grant asks you to evidence the installation years later.**

- Keeps the complete file with its date

→ The claim comes from the archive.