What the MCS Technical Supervisor role requires, what happens when their qualification lapses, who can hold it, and when you need more than one.
Every business on the redeveloped MCS installer scheme has to name a Licensee, a Main Contact and at least one Technical Supervisor. The Technical Supervisor is the role that touches every job, because their name goes on every MCS certificate you raise, and their qualifications are checked against specific installations rather than against the business in general.
This guide is about that one role: what it requires, what happens when a qualification lapses, why it can be sub-contracted when the Main Contact can't, and when a growing business needs more than one. For the transition itself, the MCS audit checklist covers what your certification body will ask for.
The Installer Operating Requirements define the Technical Supervisor as the person who, for a specific installation, takes overall responsibility for the safety, technical standard and quality of the work. They must make sure it complies with the relevant MCS Installation Standard, the Pre-sale Information and System Performance Estimate Standard, other relevant industry standards and the manufacturer's instructions.
The old Nominated Technical Person was a scheme-level role: one named person who represented the technical competence of the business. The Technical Supervisor is linked to individual installations instead. Their sign-off is their agreement that a particular install, on a particular property, is fully compliant, and the requirements say you can't undertake or self-certify installation work without a Technical Supervisor available to give it.
At the time you certify an installation, the Technical Supervisor must hold one of two things:
The evidence is also per technology. You have to show your certification body that each Technical Supervisor holds at least one approved qualification for the technology they're declaring to be technically compliant. A heat pump qualification doesn't cover a solar install, and the other way round. MCS publishes the list of approved training courses that count.
The test is applied on the date each certificate is raised, not on the date of your last assessment. So a lapse doesn't surface as a general problem with the business. It surfaces against specific jobs. Clause 5.13 of the Installer Operating Requirements says that if the assigned Technical Supervisor doesn't meet the qualification requirement, a non-conformity is raised against the relevant installation or installations. Every certificate raised between the expiry date and the renewal is exposed.
Three other parts of the requirements decide how much that hurts:
The same logic applies when someone leaves. If an installation is picked for a site-based assessment and its original Technical Supervisor is no longer employed or contracted by you, clause 5.11 says you have to provide an alternative Technical Supervisor for that technology. A business with exactly one qualified person per technology has no answer to that question on the day they hand in their notice.
The two roles that sound similar are treated differently. The Main Contact has to be an employee of the company. They're your point of contact with your certification body and MCS, and their details are held against your record in the MCS Installations Database. The Technical Supervisor can be directly employed or sub-contracted, because the job is technical judgement on an installation, which a qualified outside specialist can provide.
If you sub-contract the role, MCS asks for three things:
Appendix A goes further for the most complex businesses, and it's a sensible template for anyone sub-contracting. The register should clearly flag sub-contracted Technical Supervisors, with copies of their qualifications and contracts easy to find. The contract should require them to keep their qualifications current and give them the authority to require changes to an installation, so they can sign off on your behalf as though they were directly employed. That authority is the part that matters in practice. A sub-contracted Technical Supervisor who can't stop a job or insist something is put right isn't really supervising it.
MCS says the number of Technical Supervisors must be appropriate to the size and complexity of your MCS work, and its own examples are the ones growing businesses hit: installing across different areas of the UK, or installing several technologies.
Appendix A turns that into four operating scenarios, judged on the number of people directly involved in MCS work, your use of sub-contractors and how widely your installs are spread:
| Scenario | What puts you there |
|---|---|
| A | Sole trader, no sub-contractors |
| B | 2 to 49 people, no sub-contractors, one region |
| C | Under 50 people using sub-contractors (including as Technical Supervisor) or working in more than one region, or 50 to 249 people |
| D | 250 or more people, or using sub-contractors and working in more than one region |
Two consequences are easy to miss. Sub-contracting your Technical Supervisor counts as using sub-contractors, so it moves a single-region business from B to C on its own. And supervision becomes something you evidence. Where the Technical Supervisor installs the work or is part of the installation team, the supervision requirement is satisfied. Where they aren't, you need processes that let them monitor how teams use checklists and work instructions, plus quality checks while the work is being done, set by the competency of the people installing and the risk of the job.
In practice, these are the signs one person has stopped being the right answer:
Each of those is cheaper to fix before an assessment than as a finding in one.
When you raise a certificate in the MCS Installations Database, the Technical Supervisor's full name is a mandatory field, and the information is available to both MCS and your certification body. The redeveloped scheme extends the window for raising a certificate after commissioning from 14 to 30 days, but the declaration hasn't changed: a named person is confirming this installation complied.
If an assessor asks which Technical Supervisor signed off a particular installation and what qualification supported it on that date, you want the answer in minutes. That means the sign-off, the commissioning records for the heat pump or solar job, and the qualification register all point at each other.
Your certification body decides when you move onto the redeveloped scheme, and MCS's transition runs until 31 March 2027, the deadline for every certified business to be operating under it. The Technical Supervisor decision is the part you can settle now. For the rest of your setup, the MCS readiness checker shows what's ready and what still needs work.
The businesses that find this easy are the ones whose answer to "who signed this off, and on what basis" already exists as a routine rather than a scramble. Keeping that trail attached to the job is what compliance management in Payaca is built for. If you want the certification evidence to be a by-product of doing the job rather than a project in its own right, book a demo.
See how Payaca helps clean tech installers save time and grow their business.
Book a demoWant more from Payaca in your Google results?
England relaxed permitted development for air source heat pumps, but the right hinges on an MCS 020 noise assessment under 42 dB(A). A practical guide for UK installers on what changed and where jobs slip into a full planning application.
Batteries have no permitted development class of their own. When a home battery needs planning permission, and what to capture at survey.
Your DNO is whoever owns the network at the property, not the energy supplier. How to look it up, and when you don't have to.
