After Action Review Generator — illustrative 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.

RESULT
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.

REVIEW
An after-action review should compare expectations with observations. Focus on changes the team can make rather than hindsight or blame.

This is a teaching example, not a live execution record.