MCS Compliance: Are Your Office and Installation Teams Working From the Same Process?

The office says the job is finished. The installer says the final checks are still open. The customer has asked for their documents twice.

Someone needs to work out which answer is right.

While your teams search through emails, another job is starting. Staff lose time, the customer loses patience and a small gap becomes a bigger problem.

This can happen even when everyone is working hard. The office follows one set of steps. Installers follow another. Important details get lost where their work meets.

MCS sets standards for small renewable energy installations. Good MCS compliance depends on those links working well.

Your office team needs to know what is happening on site. Your installation team needs clear information about the work, the customer and any agreed changes.

Both need to understand what happens next and who is responsible.

Owners and managers have a key role here. If teams keep chasing each other for the same missing details, look at the process they have been given.

A clear, shared approach can help you spot problems earlier, reduce repeat work and give customers more reliable information.

A shared process gives different roles a clear link

Working from the same process means agreeing how a job moves through the business.

People will still have different tasks. An installer may carry out technical checks. An office colleague may gather the records and send the customer their documents.

The link between those tasks needs to be clear.

Ask each team to explain how a job moves from the first enquiry through to customer support after installation.

Listen for gaps. One team may believe a supervisor checks every file. Another may think that check only happens when someone raises a concern.

You might also find different meanings for the same words.

For example, “ready” could mean a customer has accepted the quote, the materials are available or the technical information has been checked.

Agree simple descriptions that everyone understands. Record what needs to happen before work moves to the next stage.

Keep the process suitable for each technology. A heat pump and a solar installation need different technical checks, even when your teams use a common way of planning and recording work.

Check the promises made before installation

Some problems begin well before a van reaches the property.

The customer has been given a date that leaves too little time for the job. A special access need is recorded in an email that the installers never see. Someone has agreed extra work without updating the instructions.

The team arrives carrying one plan. The customer expects another.

Review how information moves from sales and booking into technical planning.

Make sure the agreed work, customer needs, dates and open questions are clear. Give the right person time to review anything that could affect the design or delivery.

Office staff also need to know when to seek technical advice. A quick answer to a customer can create trouble if it promises something the system or team cannot deliver.

Under the redeveloped scheme, the MCS Customer Commitment includes clear customer information, agreed timescales and updates about delays.

Build those expectations into daily work. Before confirming an installation date, check that the people, information and resources needed for the job will be ready.

Give each job a record both teams can use

A job can become hard to manage when its history is spread across several places.

The quote sits in one system. A design change is in an email. Photos are on a phone. The office has a spreadsheet showing a different product from the one recorded on site.

Nobody can see the whole picture without asking several people.

Choose a clear place for the job information and explain how staff should use it. This could be a suitable digital system or a well managed set of linked records.

Give each job a clear reference. Make the latest instructions easy to find, with older versions kept out of everyday use.

Decide who updates customer details, who adds technical records and who checks that changes have reached the right people.

Access should match each person’s work. Protect customer information and keep records available to those who need them.

A useful test is to ask someone providing cover to find the current job information. If they struggle, simplify the route.

Agree checks before the team goes to site

A full diary can make it tempting to deal with missing details later.

That approach often pushes the problem onto an installer who has a customer waiting at the door.

Agree what needs checking before a job is released to the site team. Match those checks to the technology, the work and the requirements that apply.

Your review might cover whether the current design is available, the correct products have been ordered and outstanding questions have been answered.

Include practical details too. Is access agreed? Does the team know about customer needs? Is suitable supervision planned?

Give someone responsibility for confirming that the job is ready.

If a key item is missing, record it and agree the next step. Avoid letting a booking on the calendar become the only reason work goes ahead.

This also gives office staff a clear way to explain a delay. They can tell the customer what is being resolved, who is dealing with it and when they should expect an update.

Keep technical approval clear

An office check and a technical check serve different purposes.

An administrator may confirm that a test record has been received. Deciding whether the results show that the system meets the required standard needs the right technical knowledge and authority.

Make that difference clear in your process.

Under the redeveloped MCS scheme, each installation has a Technical Supervisor responsible for its safety, technical standard and quality. The scheme also requires suitable supervision of employees and subcontractors delivering installations.

Make sure the office knows who holds that role for each job and how to contact them. Explain what needs their review before documents are issued or work is described as complete.

Plan suitable cover when key people are unavailable. Changing a name on a file does not create the skills needed for that responsibility.

Give staff a clear route for raising concerns. They should know when to pause and seek advice, and who can approve the next step.

Record changes where both teams will see them

Consider a simple example.

A heat pump model becomes unavailable. Someone in the office discusses an alternative, while the installation team still has information for the original unit.

The customer then receives documents referring to the first model.

Everyone may believe they have dealt with their part of the job. The records still disagree.

Agree how proposed changes are raised, technically reviewed, approved and communicated. Include customer agreement and any other approvals needed for the work.

Make clear who can make each decision. Keep a record of what changed, why it changed and which information needs updating.

Check that the team doing the work has received the revised instructions. A message sent is not always a message understood.

The office also needs the outcome, so purchasing, customer updates and final documents remain accurate.

Use one recent change as a test. Could another team member follow the decision from the first question through to the completed installation?

Collect evidence while the job is happening

Missing records are easier to address when the people involved can still check the work.

Once the team has moved on, even a small query can become a long chase.

Agree what evidence is needed for each type of installation. Use the relevant MCS requirements, instructions and contract to guide that list.

Explain who records the information, where it goes and when it will be reviewed.

Where photos are needed, identify the useful pre, mid and post installation stages. Make sure the images show the required details and clearly relate to the correct property.

Treat photos as one part of the record. They do not replace the required testing, technical decisions or supervision.

Office staff can help spot missing fields, files or signatures. Technical questions should go to the person qualified to answer them.

If something is missing, record the gap honestly. Arrange suitable advice on how it can be checked or resolved. Never fill a blank with an assumed result.

Include subcontractors in the same working approach

An outside team can create another handover where details get lost.

Before work starts, explain how they will receive instructions, return records and raise questions. Agree who reviews their work and who communicates with the customer.

Give them access to the information needed for their role. Check that they are using the current version.

Be clear about what happens if the work differs from the plan or a required record is missing. A subcontractor should know whom to contact while the issue can still be addressed.

Your office team also needs to understand the arrangement. Otherwise, a customer’s question may be passed between people who each expect someone else to answer.

Review the first few jobs together and deal with recurring gaps early.

Include these arrangements in your written subcontract agreement. Clear expectations at the start give both businesses a better chance of delivering a consistent service and returning usable records.

Be clear about what finished means

A team leaving site does not tell the office whether every part of the job is complete.

There may be a test to review, a customer question to answer or documents to provide.

Create clear status labels that show the actual position. For example, a job might be awaiting technical review or awaiting customer handover.

Avoid a single tick that hides several open tasks.

Agree who confirms each stage and what evidence supports that decision. Give outstanding actions an owner and a date for follow up.

Office staff should be able to explain the position without guessing. Installers should know which records are needed before their part of the job can be closed.

Include the people who prepare certificates and customer packs in this discussion. Check the rules and deadlines that apply to those documents.

A short review at this stage can catch conflicting product details, missing records or promises that still need to be met.

Make customer handover a joined effort

The customer needs to understand the system they will live with.

A folder of documents may help, but they also need clear guidance on using the equipment and getting support.

The redeveloped scheme’s Customer Commitment includes demonstrating the system, explaining its use and providing a handover pack. It also covers maintenance information, relevant warranties and how to get help.

Agree which parts are handled on site and which are managed by the office.

Leave time for the practical explanation. Record what was covered and any questions that need a further answer.

Check that the documents sent afterwards match the system installed. Use the relevant technology requirements when preparing the pack.

The office should know if the customer needs another demonstration or a different way of receiving information.

Make sure both teams give consistent contact details for support. A customer who calls after handover should reach someone who can see the job history and arrange the right help.

Learn from the questions that keep coming back

Repeated problems can show where your shared process needs work.

Perhaps the office often chases the same test record. Installers regularly ask which design to use. Customers keep saying they do not understand a control.

Bring those examples into a short discussion involving both teams.

Ask what caused the problem. Was an instruction unclear? Did the right person receive the information? Was enough time allowed?

Choose a practical change and check whether it helps.

For example, you could improve a job checklist, add a review before booking or make customer questions more visible.

Keep a few useful measures, such as incomplete files, repeat visits and time spent chasing records. Look for patterns across jobs.

Make sure staff hear what changed following their feedback. When they can see that raising a problem leads to action, they have a reason to keep sharing useful information.

Check which MCS requirements apply to your business

MCS is moving installers onto its redeveloped scheme in stages throughout 2026 and into 2027.

That means businesses need to understand their own position. Check your transition arrangements with your certification body, the organisation that assesses your business for certification.

The MCS Standards and Tools Library separates documents for the existing scheme from those for the redeveloped scheme.

Use the correct set for your business and check the latest versions and any dates for applying changes. Avoid mixing old forms with new instructions without reviewing them.

Nominate someone to monitor relevant updates and share what staff need to know. Make the effect on daily work clear.

For example, an update may affect a customer document, a technical check or the way a responsibility is recorded.

Ask both teams to confirm what changes for them. Keep the training and guidance suited to their tasks.

Buying new software or adding more forms will only help if the people using them understand the process.

The benefits of an MCS consultant’s support

When you are managing customers, staff and a busy order book, finding the cause of repeated problems can be difficult.

An MCS consultant can help you follow a job through the business and see where information or responsibility gets lost.

The benefits of an MCS consultant can include:

• Reviewing how office and installation tasks fit together.
• Helping clarify responsibilities and suitable cover.
• Identifying forms that repeat information or leave gaps.
• Supporting reviews of job files and customer handovers.
• Helping teams understand relevant changes and prepare for assessment.

Good support should fit the way your business works.

A small team may need clearer instructions and a simpler record system. A business using several crews or subcontractors may need stronger checks between more people.

Ask how staff will be involved in testing the proposed changes. A process needs to work during a busy week, when questions and changes happen.

Consultant support can help your business improve its approach. Your team still needs the right technical skills, and your business remains responsible for the work it delivers.

Put one job through the test

Start with a recent installation.

Bring together someone from the office and someone involved in delivering the work. Follow the job from the first agreed quote through to handover.

Check whether both teams can find the current information, explain the decisions and identify anything still open.

Write down the first three gaps you find. Give each one an owner and agree when you will review progress.

This gives you a clear starting point for improving MCS compliance across the business.

Compliant can help you review the links between your office and installation teams, identify gaps and build practical ways of working that staff understand.

Speak to Compliant about your certification plans.