Verified
The journey was checked and the evidence supports it.
Cover
Keep the journeys that matter checked as your system changes
Maintained checks on named business journeys, an assessed status every cycle, and a stated limit on what that status covers.
01A place to start
If your platform is already live, start here
Cover is not only where the other products lead. It is a way in on its own: if the platform is live and you know which journeys matter, you do not need an assessment to tell you that. Cover’s onboarding builds the checks and you begin.
The suite is built for your live platform, in your test environment or CI. Nothing is built or run in production. Being live is what makes a platform worth covering — it is not where the work happens.
02What it is
Maintained checks, assessed evidence, a named lead
Cover applies to named, accepted business journeys — not to a platform in general, and not to every line of code. The checks run in the agreed non-production test environment, or in CI, against builds and release candidates intended for production.
03The status
Four verdicts, and the difference between two of them
Verified with residual risk
Checked, and it passes — but something known remains, and we say what.
Not verified
It ran, and it did not pass. There is a result and the result is a problem.
Not assessed
It did not run at all — out of scope this cycle, blocked, or not in the register. No result exists.
04The boundary
What Cover covers
- Functional assurance on named, accepted live journeys
- Checks maintained as the system changes
- Evidence assessed by a named lead each cycle
- A clear record of what was not covered
- New journeys added through scope and acceptance controls
What Cover does not do
- Test directly in production
- Approve your releases
- Cover a whole platform, or every line of code
- Include performance, security, accessibility or resilience unless separately agreed
05Adding journeys
How the register grows
New journeys go through the same gate as the first ones: named, banded, and accepted against a working environment before they count as covered. Nothing is added quietly, and nothing is billed quietly.
Discuss Cover scope
Bring the journeys you already know matter. If the environment and the data can support them, that is the conversation.