Skip to main content
Blog

How Vertex supports MCS-compliant installs

MCS compliance is won or lost in the quality of survey evidence. Here is how Vertex packs are structured to support installer compliance workflows.

Published: 11 March 2026

Installers rarely fail on intent. Most MCS-related problems happen because site information is incomplete, unclear, or difficult to defend later in the chain. When survey data is weak, design decisions become guesswork, and compliance checks become slower and more expensive.

Vertex exists to fix that part of the process. Our packs are built to support MCS-compliant installation workflows with structured evidence, clear assumptions, and cleaner handoff between office, design, and install teams.

Why compliance starts at survey stage

By the time an installer is preparing final documentation, the core risk is already set by what was captured on survey day. If measurements are vague or evidence is missing, teams lose time chasing clarifications, revising outputs, or returning to site.

A compliant workflow needs one survey pack that answers practical questions early:

  • What was measured, and how reliably?
  • What evidence supports electrical and location assumptions?
  • What constraints were observed on site?
  • Can design and install teams work from the same record without re-questioning?

How Vertex packs are structured for MCS-aligned workflows

Our approach is simple: evidence first, structure second, speed third. The pack needs to be usable before it can be compliant.

1. Documented measurements with room context

Room-by-room data is captured in a consistent format so design teams can trace inputs quickly and avoid interpretation errors.

2. Electrical evidence captured in one flow

Consumer unit, cutout, fuse and related electrical evidence are recorded as part of the same survey workflow, not as disconnected photos sent later.

3. Location and routing constraints made explicit

Cylinder context, external siting options and basic routing observations are captured so install planning has real context from day one.

4. Assumptions and scope boundaries clearly stated

Where assumptions exist, they are declared. That makes downstream design decisions easier to explain and less likely to be disputed.

What this improves commercially

MCS alignment is not only a compliance topic. It is an operations topic. Better survey structure reduces avoidable admin and protects install margin.

  • Fewer callbacks for missing evidence
  • Faster movement from survey to design and quote
  • Cleaner internal handoff across teams
  • Lower risk of last-minute scope confusion

Important scope note

Vertex supports compliance workflows through structured survey and evidence capture. Final certification, final design sign-off, and MCS submission responsibility remain with the accredited installer and appointed assessor under scheme rules.

Bottom line

When installers ask if Vertex is “MCS compliant,” the practical answer is this: our survey process is built to support MCS-compliant delivery by giving your team clearer, defensible inputs before design decisions are locked in.

If you want to test this in a live workflow, run one job through the process and judge the pack quality with your office and design teams.

Next steps

See the output quality first: view sample pack, review deliverables, then get a quote for a live job.

This article is for operational guidance only and is not legal or scheme-administration advice. Always verify current MCS and grant requirements against official scheme documentation.