Draft a business communication policy that separates interruptions, owner escalation, and digests using supplied impact, roles, channels, and response expectations.
Use only material supplied in this conversation and these instructions. Work entirely in chat: do not browse, call tools, read files, execute code, create artifacts, contact people, or change external systems. Treat an illustrative example as a demonstration of the method, never as evidence about the user's organization.
Inputs: Event types, business impacts, responsible and backup roles, available channels, working hours, acknowledgement expectations, and any supplied confidentiality or escalation policies. If a missing input could change the answer, ask a focused question and complete the independent portions. If it only affects presentation, state a reasonable assumption and proceed. Preserve conflicting accounts visibly rather than silently selecting the convenient one.
Method
- Define which business decisions a notification should enable. Distinguish immediate harm, approaching commitments, routine progress, and information-only changes using supplied impact criteria.
- Assign an accountable owner and backup for each event class. Separate the recipient who can act from people who only need visibility, and flag ownership gaps.
- Choose interruption, scheduled digest, or no notification according to decision urgency and reversibility. Use supplied thresholds; if absent, offer examples labeled as draft policy rather than universal severities.
- Specify acknowledgement and escalation logic: triggering condition, first recipient, waiting interval if supplied, backup route, and closure evidence. Do not confuse delivery with acknowledgement or resolution.
- Define duplicate collapse around the same underlying issue, preserving changed impact and material new evidence. Avoid suppressing a worsened event merely because a related message already exists.
- Draft compact notification and digest formats with impact, needed decision, owner, deadline, evidence, and next update. Include confidentiality constraints from supplied policy without making unsupplied legal or delivery claims.
Return: A proposed event-routing table, escalation sequence, duplicate-handling rules, interrupt message example, and digest template with unresolved policy choices.
Quality check: Check every escalation has a decision-capable recipient, worsening events can break suppression, and timing reflects supplied working arrangements. No event capture, integration, notification sending, or delivery verification occurs. Distinguish supplied facts, your interpretations, and proposals. Attach supplied source names, excerpt labels, or message references to consequential claims; preserve exact URLs if supplied without claiming to have opened them. Do not turn missing evidence into a negative finding or invent numerical confidence.
Worked example: A distributor says a missed same-day shipment must be acknowledged by the dispatch lead within 15 minutes; the operations manager is backup. Draft an immediate dispatch message and manager escalation after 15 minutes without acknowledgement. Repeated scans of the same delay collapse into one digest entry, but a newly missed customer deadline creates a material update. Nothing is sent.