MCS certification is not optional for UK solar installers who want their customers to access the Smart Export Guarantee, 0% VAT, or government support. Every installation produces a trail of documentation that needs to be generated correctly, stored securely, and retrievable for years. This article covers exactly what your software needs to do, and where the current options fall short.
Connect with us about solar installer software · · Replies within 24 hours
The Microgeneration Certification Scheme is the quality mark that unlocks the UK renewables market. Without MCS certification, your customers cannot register for the Smart Export Guarantee (SEG) to earn from surplus solar generation. They cannot benefit from 0% VAT on domestic installations. And any future government incentive scheme will almost certainly require MCS as a prerequisite.
In 2025, there were 267,032 MCS-certified solar PV installations in the UK, smashing the previous record set in 2011 by 31%. Over 4,000 contractors are now MCS-certified for solar PV alone. With that volume of installations, the documentation burden is significant, and it scales linearly with every job you complete.
Each solar PV installation requires:
On top of per-installation documentation, MCS makes every certified installer keep a Quality Management System, or QMS. This is a set of processes demonstrating how you control the quality of installations. Records must be backed up electronically, stored off-site or in the cloud, and accessible to everyone involved in delivering installations.
The requirements above translate into specific software capabilities. Most installers currently cobble these together from multiple tools. Here is what a proper system handles in one place.
Your software must give the customer a performance estimate. It shows the expected output each year in kWh. It must use the system as designed, the roof itself, and the location. This is not a generic figure. MCS expects the estimate to reflect the actual design you are proposing. The software should pull from design data (panel wattage, orientation, tilt, shading losses) and produce a formatted document the customer can review before signing.
Commissioning is where most documentation gaps appear. The installer on site must record three things. The generation meter, its serial number and its reading, before and after. The electrical test results. What they saw on inspection. This data needs to reach the office quickly so the MCS certificate can be issued within the 10-day deadline.
A good system gives the installer a form on a telephone, to fill in on site. Some fields are required, so nothing can be sent until every needed figure is there. Photographs go straight onto the installation record. They do not wait in a telephone gallery for somebody to move them.
The MCS certificate must be issued within 10 days of commissioning. Your software should follow that deadline, and warn the office as it nears. Best of all, it should build the certificate data ready to send to the MCS Installation Database. Late submissions risk non-conformance.
The handover pack is not a single document. It holds several documents together. The MCS certificate. A signed declaration from the installer. The warranties from the panel and inverter makers. A maintenance schedule. The system specification. The commissioning data. Your contact details. Assembling this manually in Word for every installation is slow and error-prone.
Software should assemble the handover pack automatically from data already in the system. The design specification, the commissioning record, the certificate, and the warranty details are all generated during the project workflow. The handover pack should be a compiled output, not a manual assembly job.
MCS expects photo documentation of each installation. This includes before-and-after meter readings, the installed panel array, inverter placement, electrical connections, and labelling. A photograph must join the right installation record. It must not sit in a shared folder. Six months later an auditor asks, and nobody can find it.
Beyond individual installation records, MCS requires a functioning Quality Management System. You need written methods for how you run an installation. You need proof that your staff are competent, and that includes your Nominated Technical Person. You need records of every complaint. You need a way to find a fault and put it right.
Your software should keep these records as a normal result of daily operations, not as a separate paperwork exercise you do before an audit. If every installation follows a defined workflow in the system, and every exception is logged, your QMS records are already being generated.
MCS compliance is only half the picture. A solar installation business also needs to manage the operational workflow that surrounds each job.
Leads arrive from multiple sources: your website, social media, lead generation platforms, word of mouth, and manufacturer referral programmes. Each lead needs to be captured, qualified, and moved to a site survey. The software should track lead source so you can measure which channels deliver actual signed contracts, not just enquiries.
The survey records what the design needs. The roof size, which way it faces and its pitch. Anything that casts a shadow. The state of the structure. The electrical work already there, and what the consumer unit can take. That data must reach the design with nobody typing it again. The design may happen in your own system, or in a tool you connect, such as OpenSolar or EasyPV.
The system design produces a bill of materials and a performance estimate. Those feed the quote. It must list the hardware costs one by one, with the labour and the scaffolding. It must show the VAT, which is 0% for home energy-saving materials until at least March 2027. It may offer finance terms. It must give the customer a clear way to accept.
Once the customer signs, the project enters the installation pipeline. This means scheduling a crew, ordering equipment, submitting a DNO notification (required for grid-connected systems), and confirming the installation date with the customer. The software should show the office a clear view of upcoming installations, crew availability, and equipment procurement status.
The installation triggers the commissioning workflow described above. After commissioning, the handover pack is assembled, the MCS certificate is submitted, warranty registrations are completed with manufacturers, and the customer gets their documents. The SEG registration process can also be initiated at this point.
Solar PV systems carry manufacturer warranties of 10 to 25 years on panels and 5 to 12 years on inverters. Your system needs a warranty register that tracks what was installed, when, and what warranty terms apply. Scheduled maintenance reminders and a mechanism for logging faults or customer queries complete the aftercare workflow.
The UK market for solar installer software is fragmented. Here is an assessment of the gaps.
Payaca (£299 to £1,199/month) is the most complete dedicated platform for UK clean tech installers. It handles CRM, MCS-compliant proposals, scheduling, invoicing, and integrates with design tools. The limitation is cost. The Core plan costs £299 a month. A small installer doing 10 jobs a month therefore pays £30 a job for software, before any other tool. The Growth plan at £1,199/month is positioned for larger operations but represents a significant ongoing commitment.
OpenSolar (free core platform) is excellent for solar design, performance simulation, and proposal generation. But it is a design tool, not a project management system. It does not handle scheduling, commissioning workflows, handover pack assembly, or warranty management. You still need something else to run the business.
Pylon (£4 to £10/project) offers affordable solar design and proposals on a pay-per-project basis. The CRM add-on starts at $49/user/month. It is cost-effective for design work but does not cover the full installation workflow or MCS compliance documentation.
Generic field service tools (Jobber, SimPRO, Commusoft) handle scheduling, invoicing, and customer communication well. They know nothing about MCS compliance, solar design, performance estimates, or handover pack requirements. You can use them for the operational side but still need separate tools for everything renewable-specific.
The result: most UK solar installers run two to four separate tools, plus spreadsheets for the gaps. Data gets entered multiple times. Documents get assembled manually. And compliance depends on the diligence of individual staff members rather than being enforced by the system.
Connect with us about solar installer software · · Replies within 24 hours
Count what the article has just described. A solar installer doing 20 jobs makes more than 120 compliance documents a month. Every one of them repeats facts that already exist somewhere else.
A document is a copy. The performance estimate copies the survey. The certificate copies the design. The handover pack copies both. Each copy can go out of step with the others, and a person must keep them in line. That is what an MCS audit is really testing.
On engage.re the survey, the design, the commissioning data, the certificate and the photographs are one set of data, each with a permanent identifier. A document becomes a view of that data at a moment, and not a new copy. Every action goes to a signed log, so what the certificate says can be proved to be what the installer recorded.
Every installer we build for shares that foundation, so a change to MCS is made once for all of them. We explain that in bespoke software for a whole sector.
A bespoke system built specifically for your solar installation business eliminates the fragmentation. Every step from lead to aftercare lives in one system. What the surveyor records reaches everything after it. The design, the quote, the project plan, the commissioning record, the handover pack and the warranty register.
MCS compliance becomes a byproduct of doing the work, not a separate administrative task. Your installer fills in the commissioning form on their telephone. The system then checks that every required field is there. It marks any photograph that is missing. It works out whether the 10-day MCS deadline is at risk. It starts to build the handover pack.
You own the system outright. Your compliance records, customer data, and installation history are not locked inside a third-party platform. They live on infrastructure you control, backed up and protected, accessible for the full 25-year warranty period if needed.
A core system of your own covers leads, quotes, the project, the MCS documents, commissioning, handover packs and warranties. It usually costs £8,000 to £18,000 as a single build. That is less than three years of Payaca's Core plan, and you own it permanently.