MCS solar job paperwork
Every document an MCS solar job creates, and when to do each one
One domestic solar PV job produces records for five readers: the customer, the network operator, building control, MCS and your own file. Here is the full list, the order it falls in and a way of working that closes the file before you leave site.
- Fourteen records listed with who receives each
- The two deadlines that catch small firms out
- A same day routine you can start this week

The documents, in the order a job produces them
A typical domestic roof job in England or Wales. Your own file keeps a copy of every row.

| Document | When | Who it goes to |
|---|---|---|
| Survey record: roof measurements, photos, shading notes, consumer unit | First visit or remote survey | Your file |
| Performance estimate in the MCS 032 format, with self consumption figures | Before contract | Customer |
| Module layout drawing, datasheets and the sunpath diagram if the roof is shaded | Before contract | Customer |
| MCS Customer Commitment | Before contract | Customer |
| Quotation, contract and cancellation rights | At sale | Customer |
| G99 application, where the system is over 16 A per phase | Before install | DNO |
| Roof structure check and mounting calculation | Before install | Your file |
| Risk assessment and method statement | Before install | Your file and the site team |
| Electrical Installation Certificate to BS 7671 | Commissioning | Customer |
| PV array test report and system verification certificate | Commissioning | Customer |
| G98 notification, for systems up to 16 A per phase | Within 28 days of commissioning | DNO |
| Building Regulations notification | After commissioning | Building control, through your competent person scheme |
| MCS certificate | Within 30 calendar days of commissioning | Customer, raised on the MCS database |
| Handover checklist, user instructions, warranties, written workmanship cover and financial protection product | Handover | Customer |
Why one solar job makes so much paper

An MCS solar job answers to several sets of rules at once. MIS 3002 covers how the system is installed and tested. MCS 032 covers what the customer is told before they sign. The Installer Operating Requirements cover how your company keeps records and looks after the customer. BS 7671 and the Building Regulations cover the electrical work, and the distribution network operator (DNO) has forms of its own. Each wants its own evidence, and most of them want the same facts: the address, the kit, the array size and the dates.
That repetition is the real problem. The documents themselves are short. What eats the evening is typing the same module model, inverter serial number and MPAN into six places, then hunting for a photo that is on somebody else's phone. Remove the repetition and the pile shrinks to something you can finish before the scaffold comes down.
A note on names. MCS relaunched its installer scheme with new document titles, and certification bodies are moving existing companies across in phases. If your templates still quote MCS 001 and a consumer code, you are on the older rules until you are moved. The list above uses the current titles.
Deadlines and retention worth pinning to the wall

- MCS certificate
- Raised within 30 calendar days of commissioning
- G98 notification
- Sent to the DNO within 28 days of commissioning
- G99 application
- Agreed by the DNO before the system is connected
- Pre-sale information
- In the customer's hands before the contract is agreed
- Installation records
- Stored securely for at least six years
Where the evenings actually go

Ask a two van solar firm where the hours go and the answer is rarely the roof. It is rebuilding the quote figures inside the handover pack, chasing a serial number nobody wrote down, and filling in the DNO form from memory at the kitchen table.
Three habits cause most of it. First, the survey is written on paper and retyped later. Second, the design changes on install day (a panel dropped to clear a vent, an inverter swapped because of stock) and nobody updates the estimate the customer was given, so the certificate and the quote disagree. Third, commissioning readings go on the back of a delivery note and are typed up on Sunday.
None of that is a competence problem. It is a data entry problem, and it has a plain fix: record each fact once, at the moment you learn it, somewhere every later document can draw on.
A routine that finishes the file the same day
This works with a shared folder and decent templates. Job software makes it quicker, but the order is what matters.

Capture the job once
At survey, record the address, MPAN, roof dimensions, pitch, orientation, shading and consumer unit details in one place. Every later document should draw on that record, never on memory.
Lock the design before the quote
Produce the layout, performance estimate and datasheets together and send them as one bundle with the Customer Commitment. If the design changes later, reissue the estimate that day, keep both versions and note in one line what changed and why.
Send DNO forms from the design
A G99 application goes in as soon as the customer signs, because nothing can be connected until the DNO agrees. For G98 jobs, prepare the notification now and leave only the commissioning date blank.
Photograph to a list
Give the roof team a fixed shot list: roof before work, fixings, rails, cable routes, isolators, labels, inverter data plate and meter. Photos named by job go straight into the file.
Commission into the template
Enter test results into the array test report and the electrical certificate on site, on a phone or tablet. Scan serial numbers instead of copying them by hand.
Hand over before you leave
Walk the customer through the handover checklist and send the pack while you are still there. Then raise the MCS certificate and send the G98 notification with the details in front of you.
Close files on a Friday
Once a week, open every job commissioned in the last month and tick off the certificate, DNO notice, building control notice and pack.
Things installers ask us
What paperwork is needed for an MCS solar installation?
Before the sale: a performance estimate in the MCS 032 format, a layout drawing, datasheets and the Customer Commitment. For the install: a roof structure check, risk assessment and any G99 application. At the end: the Electrical Installation Certificate, PV array test report, DNO notification, Building Regulations notification, the MCS certificate and a handover pack.
How long do I have to register an MCS certificate after commissioning?
The Installer Operating Requirements say the certificate is raised within 30 calendar days of commissioning the installation. The clock starts at commissioning, not at handover or final payment, so a job that waits for a snagging visit can run out of time. Raise it on the day where you can.
How long do I need to keep MCS job records?
The current scheme rules ask for installation records to be kept for a minimum of six years, stored securely and backed up. That covers the whole file: quotes, design records, test results and what was handed to the customer.
What goes in an MCS solar handover pack?
At least: the MCS certificate, the Electrical Installation Certificate, the array test report and verification certificate, user and shutdown instructions, datasheets and warranties, confirmation of the DNO notification, your written workmanship cover and the financial protection product. MCS publishes a handover checklist for each technology.
Who sends the G98 notification, the installer or the customer?
The installer. MIS 3002 puts the duty to notify the DNO on the MCS certified company, and MCS guidance says it is done within 28 days of commissioning. Find the right DNO from the postcode or the MPAN, and check whether it wants its own online form.
Do I need special software to do MCS paperwork?
No. Nothing in the scheme requires paid software, and a small firm can meet it with templates and a tidy folder for each job. Software earns its place when you are retyping the same details into several documents or losing track of which jobs still need a certificate.
See one job record fill every document
Helionix builds the estimate, DNO forms, schematic and handover pack from details you enter once. Book a demo, send a question through the form or open the chat and ask about your own workflow.