Skip to main content
Compliance guide

What delays MCS certificate sign-off?

Most delays are not mysterious. They usually come from missing evidence, mismatched product and site information, or a pack that is technically complete but hard to audit quickly.

MCS certificate guide MCS documentation guide
What usually slows sign-off

The same failure points show up again and again

Evidence
  • Key photos are missing, unclear, or not labelled properly
  • Assumptions are buried instead of being stated plainly
  • The note and the proof sit in different places and do not resolve each other
Mismatch
  • Product details do not line up cleanly with what was surveyed
  • Electrical context is too thin for the reviewer to follow confidently
  • Site constraints that affect the install were not surfaced early enough
Handoff
  • The pack is technically present but hard to navigate
  • Office, design, and install are all working from slightly different records
  • Clarification loops begin after the visit when they should have been prevented on survey day
How to reduce delay

The fastest route is a pack that is audit-friendly before anyone asks for clarification

Survey day

Capture the proof that supports the decision, not just the attractive photo set. If a reviewer cannot follow why the assumption was made, the pack is still weak.

Structure

Keep the note next to the evidence, make caveats visible, and avoid leaving the office or compliance team to rebuild the logic from scattered files.

Next step

Use the MCS guide, the documentation guide, and the sample pack together. That is the quickest way to pressure-test whether the handoff is good enough before a live job depends on it.

MCS certificate guide Documentation guide View sample pack