Practise the standard verbs for writing runbooks that actually work under pressure.
0 / 5 completed
1 / 5
Fill in: 'We ___ a runbook for every repeatable operational task, so handling it at 3am doesn't depend on one specific engineer being awake and reachable.'
We 'write a runbook' — the standard, simple collocation for documenting an operational procedure step by step. The other options are less idiomatic here.
2 / 5
Fill in: 'Writing a runbook nobody has actually followed under real conditions can ___ a step silently missing exactly when someone finally needs it during a live incident.'
We say an unverified runbook will 'leave' a step missing during a real incident — the standard, natural collocation for the resulting gap. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ a runbook end to end at least once before trusting it, since a step that looks correct on paper can still fail the first time it's actually run.'
We 'test a runbook' — the standard, simple collocation for verifying a procedure actually works as written. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ every runbook whenever the underlying system changes, since a step describing a command or dashboard that no longer exists is actively worse than no step at all.'
We 'version a runbook' — the standard, simple collocation for tracking updates to an operational document over time. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ every alert directly to its matching runbook, so whoever's paged first thing gets a concrete next step instead of an empty alert with no obvious action.'
We 'link an alert' — the standard, simple collocation for connecting monitoring output to its response procedure. The other options are less idiomatic here.