Engagement rhythm
How we work through an assessment
A plain map of the Reliability Assessment flow — what happens each week, who needs to be available, and when you receive the findings pack.
Built for measurement, not theatre
This page exists so stakeholders know what they are commissioning before the first login is shared. The same rhythm scales down for a Latency Audit and informs how we prep Error Budget Workshops.
Flagship assessment details-
Week 0 — Scope call
Confirm journeys in scope, peak windows, success criteria, and the named technical contact. You leave with a one-page scope note and a credentials checklist.
-
Week 1 — Instrumentation review
We map how latency, errors, timeouts, and retries are already observed. Gaps are noted; we do not invent a monitoring estate mid-engagement.
-
Weeks 1–3 — Measurement window
Baselines across peak and off-peak periods. Failure-mode walkthroughs cover partner stalls, partial outages, and retry behaviour on the paths you named.
-
Final week — Findings & readout
You receive the ranked findings pack and a 90-minute readout with engineering stakeholders. Remediation items are ordered against your release calendar where you share one.
-
Optional — Quarterly review
Teams that want a steady checkpoint can continue with a Quarterly Reliability Review using the same metric sources.
Ready to put a measurement window on the calendar?
Tell us which integrations matter commercially. We reply within two business days with questions and a draft estimate.
Request a briefing Browse all engagements