How to use the Meeting Policy Generator.
Meeting rules should support decisions and collaboration. Explain when synchronous discussion is useful and when a written update is sufficient.
Make the workflow fit your task.
Classify meetings by the decision or collaboration they support, then define preparation, participation and follow-up expectations. Identify updates that can be written and keep synchronous time for work that benefits from discussion.
- What you provide
- Team needs, calendars and communication norms.
- What you get
- Meeting rules and asynchronous alternatives.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Team has daily status meetings but few decisions to make. Draft a proposed meeting policy for team review.
Completed example
Proposed policy: routine status updates are written before the agreed check-in time. Hold a short discussion only when there is a blocker or decision requiring conversation; state that item in advance and invite the necessary people. Record decisions and owners afterward. The team must agree the update channel, timing and exceptions before adopting this proposal.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should all recurring meetings be replaced with written updates?
Review their actual purpose. Some decisions and collaborative work need discussion, while routine status may be handled effectively in writing.
Why do shorter meetings still fail to produce outcomes?
Name the decision, facilitator and follow-up owner. Reducing duration does not resolve an unclear purpose.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑