Evidence checklist · 8 MIN

Check your operating model

Identify missing owners, controls, and recovery evidence. Create a practical action list.

The situation

A fictional team wants to release an internal expense app. Its feature tests pass, but nobody has tested recovery or assigned incident cover. Use the example to find what remains before you assess your own service.

What to do

  1. Select Expense app example. Read the stated evidence and the resulting action list.
  2. Select Start my assessment to clear the example. Assess one service. Use Evidence verified only for a current document or test result.
Need the background? Read the lesson

Start with an example

Each example fills the fields below and shows the result. You can then change the values yourself.

Assess one limited service or use case. Select “Evidence verified” only when you can identify a current document or check result.

What do the choices mean?
Unknown
You cannot identify current evidence. For example, no recovery exercise has been run.
Partial evidence
Some work exists, but the requirement is not fully verified. For example, recovery instructions exist but have not been tested.
Evidence verified
You can identify a current document or test result that covers the whole statement. For example, a recovery test records its result and responsible person.
Where do you have evidence?

TO FINISH

The feature tests pass. What is the first useful action before release?

Compare your answer with the explanation

Assign a person to lead the recovery test and record its result. Also assign incident cover and verify the remaining gaps. A passing feature test does not prove that the team can restore or support the service. Prioritize actions by their possible harm, not by the order of this list.

Use this at work

Take one missing item to your team. Agree on its owner, due date, and the evidence needed to close it.

Choose another exercise