ServiceNow Incident Communication Quality Audit
Check the clarity and timeliness of incident updates.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Audit the quality of incident updates. Sample of 20 incidents with the public updates written, times of updates, and user complaints: [INCIDENT_UPDATES]. Users should be able to act on an update without a second message. Scoring guide: 5 means all five elements are present and clear (what is affected, what is known, what is being done, what users should do, when the next update comes), 3 means one is missing, 1 means almost nothing, such as 'we are looking into it'. Worked scoring: Update A 'We are aware of an issue and are looking into it' scores 1 of 5; Update B names the affected service, the number of users, the action, a workaround and the next update time and scores 5. Rewrite A into B with invented details; example rewrite: 'Email is slow for some users in the London office since 09:10. We have found a fault with one server and are moving users to another. Please keep working; sending may take a few minutes. Next update by 10:30.' Check jargon, blame, speculation and timeliness against the agreed cadence (14 of 20 on time is 70 percent), and score all 20 with the average. Return a table, the commonest gaps, a template, a cadence rule by priority, a short training exercise for communicators, and two rewritten updates. Names of fields and features vary by release and set-up; flag what you cannot confirm [VERIFY] instead of presenting it as fact.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.