Home is the short answer for one client. It is where you check live devices, current readiness, proof strength, and the best next move.
Start here
Start by choosing a client. This page should answer four things quickly: are devices live, how close is this client to Cyber Essentials, how strong is the proof, and what should happen next.
Proof strength tells you how much of the score is backed by fresh evidence from devices or connected sources, not just unanswered assumptions.
Use `Devices` to confirm reporting, `Readiness` to see blockers, `Checklist` to review exact answers, and `Reports` when the story is ready to share.
What you are looking at
What to do next
What matters now
Getting real proof
Follow-up queue
Who owes something
Change client
Choose the right workspace
Use this as the quick route from live devices to a clean Cyber Essentials story when you already know where you want to go next.
Pick the client scope you actually want to work in.
Make sure reporting devices tell a believable operational story.
Turn missing or weak controls into cleaner proof paths.
Use Reports & Sharing once the story is fit to hand over.
Keep the benchmark, evidence stack, and handover story aligned
Path to pass
Onboarding Hub
Create MSP
Admin onlyCreate Client
Admin / MSPDeploy Agent Bundle
Admin / MSPAdmin View Switching
Admin onlyOnboarding and source selection
Move from empty tenant to assessor-ready operating view
Start with the smallest defensible evidence stack. We only need enough connected proof to tell an honest Cyber Essentials story, then we can expand depth later.
Create scope
Create the MSP/client record, switch into the right view, and lock the benchmark scope.
Prove a device
Deploy the installer bundle and confirm at least one endpoint is actively reporting.
Connect authority
Add the minimum source-of-truth integrations needed for this client’s environment shape.
Prepare review
Run readiness, close obvious gaps, and generate the first CE autofill draft for review.
- One client in scope
- One reporting endpoint
- One trusted source-of-truth path
- One CE review run completed
- Readiness that means something
- Controls with evidence provenance
- Manual queue with guided attestation
- Assessor-style handover output
See whether this client can move from setup into Cyber Essentials review
This board keeps scope, device proof, source authority, and review readiness in one lane so the first-launch journey stays clear for operators and assessors.
What is happening in this first-launch path
Signals worth trusting
Recommended next moves
Where this client is in the launch journey
Executive summary
See what deserves attention before you read the dashboard cards
This lane separates benchmark gaps, proof strength, raw exposure, reporting coverage, and review readiness so first-time operators know where to go next.