The report
A report of how you worked.
Every scored run ends with an account of what happened: whether the fix held, the path taken, the changes made and the places where access stopped an action.
What the report contains
Individual explains the run and builds a progress history. Pro adds the services you worked in and recommendations for what to practise next.
Behaviour analysis
A timeline narrative of the run: what you looked at, when you acted, and how you used hints along the way. It reads like a debrief from someone who watched over your shoulder, not a log dump.
Mapped to six pillars
What you demonstrated is mapped against six pillars of cloud operation, so a score says what it is a score of.
- Operational excellence
- Security
- Reliability
- Performance efficiency
- Cost optimization
- Sustainability
Pro adds services worked
Every service you touched during the run, classified by how you touched it:
- Explored
- You looked at it.
- Fixed
- You changed it to resolve the challenge.
- Out of scope
- Unrelated to this challenge; no action expected.
- Ignored but relevant
- It mattered, and you did not look.
Pro adds recommendations
Specific suggestions for what to practise next, based on which pillars and services still need the work.
What the report actually looks at
Two engineers can both bring the service back. If one took forty minutes and made three risky changes on the way, the report says so.
Did the fix hold
The platform checks the live environment the way a user would: reachable, working, nothing exposed.
How the fix stacks up architecturally
The final state against the provider's good-practice framework: security, reliability, operations.
How you paced yourself
How long you looked before changing anything, read from the cloud audit trail.
How wide the fix reached
How many resources you changed, and whether they were part of what was broken.
Where you hit the walls
The moments a permission or policy stopped an action. Recorded as facts, not mistakes.
How a raised hand is judged
Asking for a hint early, after a real attempt, counts as good judgement. Asking before you have tried anything does not.
A sample report
Every scored run closes with a report. The example below shows what the same run includes on each plan.
Sample report · Checkout API: 503 after deploy
Result
Resolved
Score
82 / 100
What happened on this run
You found the failing release within four minutes, rolled it back, and confirmed checkout was serving again before touching anything else.
How it maps to the six pillars
- Operational excellence: Rolled back through the pipeline, no manual hot-patching.
- Security: No credential or permission was touched to get there.
- Reliability: Confirmed checkout recovered before declaring the run over.
- Performance efficiency: No capacity change was needed to resolve this one.
- Cost optimization: Rollback introduced no lingering spend.
- Sustainability: No extra capacity was left running after the fix.
Pro adds what services you worked in and recommendations for next time.
Progress report extract
Built from every ride and challenge so far, not just this one.
Sample report · Checkout API: 503 after deploy
Result
Resolved
Score
82 / 100
What happened on this run
You found the failing release within four minutes, rolled it back, and confirmed checkout was serving again before touching anything else.
How it maps to the six pillars
- Operational excellence: Rolled back through the pipeline, no manual hot-patching.
- Security: No credential or permission was touched to get there.
- Reliability: Confirmed checkout recovered before declaring the run over.
- Performance efficiency: No capacity change was needed to resolve this one.
- Cost optimization: Rollback introduced no lingering spend.
- Sustainability: No extra capacity was left running after the fix.
Pro adds what services you worked in and recommendations for next time.
Progress report extract
Built from every ride and challenge so far, not just this one.
Where the report is used
A run report explains one attempt. The history built from those reports shows progress for an engineer, a team or a training cohort.
For the engineer
See the run narrative, the six-pillar mapping and progress across previous scored runs.
For the team
Read the same measures across engineers, by kind of failure and over time.
For a cohort
Give the client one consolidated outcome for the group, alongside each participant’s own report.