Skip to main content

MCS compliance documentation guide: evidence, standards and sign-off

A practical approach to documenting evidence and assumptions for installers working under MCS-related requirements.

MCS keeps the standards library, MID support, and technical support routes separate. Knowing which one you need saves time when the paperwork gets messy.

Related: ASHP surveys · heat pump design support · solar surveys · MCS:2025 audit cycle guide · MCS renewal checklist · view sample report

MCS paperwork gets easier when the proof is easy to find and the assumptions are written clearly.

What this guide covers (and what it doesn’t)

  • How to lay out a site report so evidence is easy to find
  • How to document assumptions and constraints clearly
  • Not legal advice, and not a substitute for scheme/provider guidance

What MCS compliance documentation should make clear

  • Which photos, measurements, documents and assumptions support the job file
  • Which evidence was measured on site, supplied by the installer or customer, or assumed for design review
  • Which open points still need an installer, designer, Certification Body or scheme decision before sign-off

Evidence first

  • Keep photos legible, labelled, and grouped by category
  • Place the note next to the evidence it supports
  • Flag constraints early so they aren’t missed

Assumptions made visible

  • Write assumptions in plain language
  • Make scope boundaries explicit (what’s included vs not)
  • Document constraints and access issues

Official MCS routes worth knowing

  • The MCS Standards & Tools Library is where the standards themselves live.
  • The MID support page explains how certificate creation and late registration work, including the 10-working-day rule.
  • The technical queries route is for clarification on standards, and MCS says the Certification Body may be able to respond faster in some cases.

Sources checked on 17 June 2026: MCS Standards & Tools Library, MID support, and MCS technical queries.

How to use this page on a live job

Use this guide as a decision check, not as a generic reading page. The useful question is whether the evidence behind mcs documentation guide: evidence, standards and sign-off is strong enough for an installer, designer, or homeowner to move to the next step without another round of avoidable questions.

Before booking

Confirm what evidence is missing

For mcs evidence, the weak point is usually not the headline requirement. It is the missing photo, document, measurement, or site note that stops the next person from trusting the job record.

During survey

Capture the detail once, then label it properly

A survey report should show what was seen, what was measured, what could not be accessed, and what still needs a design or installer decision. That keeps assumptions visible instead of hiding them inside a photo set.

After delivery

Use the report to reduce internal handover friction

The office, design, and install teams should be able to open the same report and understand the evidence path. If the page helps you spot what to ask for before survey day, it has done its job.

For a live project, pair this guidance with the sample report, deliverables, and guide price builder so the job is reviewed against the same standard Vertex uses for survey delivery.