Practise the standard verbs for keeping status page updates timely and accurate.
0 / 5 completed
1 / 5
Fill in: 'We ___ a status page update cadence of every thirty minutes during an incident, rather than a silence nobody outside the team can actually interpret.'
We 'set a cadence' — the standard, simple collocation for defining how often incident updates go out. The other options are less idiomatic here.
2 / 5
Fill in: 'A missed status page update during a long outage can ___ customers assuming a fix nobody's actually confirmed is deployed.'
We say a missed update will 'leave' customers assuming an unconfirmed fix — the standard, natural collocation for the resulting confusion. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ each update against a plain-language template, rather than jargon nobody outside engineering can actually follow.'
We 'draft an update' — the standard, simple collocation for writing a customer-facing incident message. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ every posted update against the actual incident timeline, rather than a claim nobody's actually verified is accurate.'
We 'check an update' — the standard, simple collocation for confirming a status page post matches reality. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ update cadence in the postmortem, rather than a gap in communication nobody's actually flagged at the time.'
We 'review cadence' — the standard, simple collocation for assessing communication frequency after an incident. The other options aren't idiomatic here.