MCS compliance documentation
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.