Async Communication Guidelines
Reduce meetings and messages overload.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Write async communication guidelines. Tools used (email, chat, project tool): [TOOLS]. Time zones and working hours: [TIME_ZONES]. Current problems (too many pings, missed information): [PROBLEMS]. Produce: 1. Principles (five, one line each). 2. A channel table: Channel | Use for | Response expectation | Do not use for. 3. Message standards: context, ask, deadline, with three before-and-after examples. Example: Before "Can we chat?" After "I need a decision on the vendor by Friday. Options and my recommendation are in the doc [link]. Can you reply by Thursday 3pm?" 4. Rules for urgent issues: how to flag and the escalation path. 5. Status update templates (daily or weekly): done, next, blockers. 6. When to call a meeting instead. 7. Documentation habits: decisions written down, one source of truth. 8. "Quiet hours" norms that respect rest time. 9. A one-page summary and a monthly pulse of four questions. Working-time and right-to-disconnect rules vary by place [VERIFY in [JURISDICTION]]. This output is a working draft and not legal or HR advice. Before use or publication, ask an employment lawyer or HR professional familiar with [JURISDICTION] to check each legal, contractual or policy point.
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.