What an MCS-certified solar installer has to produce by commissioning sign-off - MIS 3002 evidence, IEC 62446 tests, the EIC, DNO notification, MID registration within 10 working days, and a handover pack that unlocks the customer's SEG application.
Matt Franklin
Ask a solar installer where a job goes wrong and they'll talk about scaffolding delays or a DNO sitting on an application. Ask their office manager and you'll get a different answer: the fortnight after the panels go on the roof, when the certificates, registrations, and notifications all come due at once and the evidence needed to complete them is scattered across an engineer's phone, a van, and three email threads.
Commissioning is where a solar job either closes cleanly or drags. For an MCS-certified business running 15 or more installs a month, it's also the biggest compliance exposure in the operation. The customer can't claim Smart Export Guarantee payments until you've registered the install. Your MCS accreditation depends on the paperwork standing up to audit. And every day between install and sign-off is a day you probably haven't invoiced the balance.
If your office is still chasing engineers for test results and photos after every install, book a demo and we'll show you how solar installers run commissioning capture on site in Payaca.
MCS certification for solar PV means installing to MIS 3002, and MIS 3002 is specific about what the installed system has to be and what the customer has to receive. By the time you sign the job off, the file should contain:
The MCS certificate isn't just your compliance record - it's the customer's key to getting paid. Every SEG licensee requires it before they'll approve an export tariff application. A slow MID registration directly delays your customer's first export payment, and they will ring you about it.
Almost every commissioning delay traces back to something that should have been captured weeks earlier. The DNO application needs inverter and panel specifications, so a survey that doesn't pin down the exact kit means the G99 application waits on a design decision. Shading analysis and roof measurements from the survey feed the performance estimate that MIS 3002 requires you to give the customer before contract. If the surveyor recorded "south-ish roof, some shading from next door" in a notebook, someone in the office is now redoing that work from Google Maps.
The fix is structural rather than heroic. Decide once what data the survey must capture - roof dimensions and orientation, shading survey, existing consumer unit condition, supply details for the DNO application, photos of everything - and make those fields required before a survey can be marked complete. Same discipline at design: the performance estimate, string design, and specified components get locked before anything is ordered, because those exact details flow into the DNO application, the commissioning tests, and the MID entry.
The engineer on the roof is doing two jobs. One is installing a solar PV system. The other is producing the evidence that lets the office close the job, and the second one is the job that usually gets skipped when it's 4pm and raining.
The IEC 62446 test results are the core of it. String voltages and currents, insulation resistance, earth continuity - recorded per string, with the meter readings, not "all fine" scrawled at the bottom of a sheet. Add labelled photos: the array, the inverter installation, DC isolation, the generation meter, the consumer unit after works, and the DC labelling that BS 7671 and MIS 3002 both expect. If any of that leaves site only in the engineer's head, the office finds out during MID registration, and the choice becomes chase the engineer for a week or book a return visit that costs £200-£400 in unbilled time.
Field capture is the difference between the two. When the commissioning checklist lives on the engineer's phone with required fields and photo prompts, the data arrives in the office the moment the engineer signs off, and sign-off can't happen with gaps in it.
MID registration within 10 working days of commissioning is the hard deadline in the process, and it's the one worth building the workflow around. Everything the entry needs - system size, component details, test results, commissioning date - already exists by the end of install day if the capture upstream was done properly. Registration then takes minutes, the MCS certificate follows, and the customer's SEG application is unblocked inside a week of the scaffold coming down.
Miss the window and the problems compound quietly. The customer's export payments are delayed and their first call is to you. Late or corrected MID entries are exactly the pattern MCS audits look for, because they signal the data behind the registrations is weak. And the balance invoice tends to wait for the certificate, so slow registration is slow cash for no reason other than process.
MIS 3002 and the consumer codes both expect the customer to walk away with a complete pack: the MCS certificate, the EIC, DNO notification or approval evidence, a system schematic, component datasheets, warranty terms for panels, inverter, and workmanship (with the insurance-backed guarantee documentation), a shutdown and isolation procedure, and guidance on applying for SEG payments.
Assembling that from scratch per job is an afternoon of admin. Generating it from the data already captured at survey, design, and commissioning is a template and a click. The pack going out within 48 hours of commissioning, with the balance invoice attached, is what a clean close looks like - and it's the version of your business the customer describes when a neighbour asks who did their panels.
Pull up last month's jobs and check:
If two or more of those numbers make you wince, the gap isn't engineer diligence - it's that your process depends on people remembering things instead of a system requiring them.
Payaca is built for exactly this shape of problem: required custom fields on survey and commissioning checklists so evidence gets captured on site, automated G98 and G99 applications and commissioning submissions pre-filled from project data, and document templates that turn captured data into the EIC pack, MID export, and homeowner handover without re-keying. Installers running commissioning this way get certificates out in days rather than weeks and reclaim 2-4 hours of admin per job.
Book a demo and we'll walk through your commissioning process end to end.
Related reading: Solar installer solutions | Do I need MCS to install solar PV? | Mobile app for field teams
See how Payaca helps clean tech installers save time and grow their business.
Book a demo
MIS 3005 split into two documents on 1 April 2022 - one for design, one for installation. Most growing UK heat pump installers still treat them as one workflow, and that's where the data leaks. A practical guide to the design-to-install handoff for scaling installers.
Commissioning is where heat pump jobs get signed off - and where margin and customer satisfaction most often leak. A practical playbook for growing UK installers on MIS 3005, the MCS Installation Database, BUS V5 voucher applications and redemption, and clean handover.
G99 rejections delay solar installations by weeks. These are the most common causes of failed applications - and what to fix before you submit.