How to use the After Action Review Generator.
An after-action review should compare expectations with observations. Focus on changes the team can make rather than hindsight or blame.
Make the workflow fit your task.
Compare the intended outcome and process with what actually happened, using observations rather than hindsight assumptions. Identify contributing conditions and assign a small set of improvements with owners and follow-up checks.
- What you provide
- Event objectives and factual outcomes.
- What you get
- Lessons organized around expectations, results and improvements.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Expected event setup: 30 minutes. Actual setup: 50 minutes. The projector connection was untested and took 20 minutes to resolve. Produce an after-action note without assigning blame.
Completed example
Expected: ready after 30 minutes of setup. Observed: ready after 50 minutes; the untested projector connection required 20 additional minutes. Contributing condition: no pre-event connection check was recorded. Improvement: test the actual presentation device and projector before the next event. Owner and check date: to be agreed. Follow-up: record whether the next setup meets its planned window.
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 an after-action review focus on identifying who caused the problem?
Focus on the sequence, evidence and conditions the team can change. Individual accountability should not replace understanding the process.
Why does the review produce lessons that never affect future work?
Turn each selected lesson into an action, owner and check date. General reminders are difficult to verify or sustain.
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 ↑