After Action Review Expected Actual Template
Compare expected and actual actions after case-normalization and build a structured after-action review template.
Description
An after-action review compares intended and observed actions before recording causes and lessons.
An after-action review compares intended and observed actions before recording causes and lessons. Text matching is a starting point for discussion.1
The returned values include Matched actions, Missing actions, Review template, Unexpected actions. The How section below explains the calculation, input rules and interpretation.
When to use After Action Review Expected Actual Template
Use After Action Review Expected Actual Template when you need to evaluate the supplied records under the calculation and evidence rules below. No root-cause inference, outcome verification or automatic action execution occurs.
Define the question, evidence and scenario assumptions first. Supply the chosen score scales, time horizons or reference selection explicitly. Interpret generated text as a discussion template and screen labels as the stated rules.
How to use After Action Review Expected Actual Template and understand its results
- Define the question, evidence and scenario assumptions first. Supply the chosen score scales, time horizons or reference selection explicitly. Interpret generated text as a discussion template and screen labels as the stated rules.
- Enter actualActions, expectedActions, outcome using the field table and calculation rules, then run the tool.
- Read matchedActions, missingActions, reviewTemplate, unexpectedActions. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| actualActions | Actual actions | list of string | Required |
| expectedActions | Expected actions | list of string | Required |
| outcome | Outcome | string | Required |
Require nonblank outcome and action lists, possibly empty. Trim nonblank entries and lowercase comparison keys. Preserve duplicates and original trimmed spelling in matched/missing expected and unexpected actual lists. Return a fixed review template with unfilled causes/lessons.
matched=expected labels present in actual ignoring case Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| matchedActions | Matched actions | list of string |
| missingActions | Missing actions | list of string |
| reviewTemplate | Review template | string |
| unexpectedActions | Unexpected actions | list of string |
{
"input": {
"actualActions": [
"PILOT COMPLETED",
"Report published"
],
"expectedActions": [
"Pilot completed",
"Stakeholders briefed"
],
"outcome": "The pilot informed the next release."
},
"output": {
"matchedActions": [
"Pilot completed"
],
"missingActions": [
"Stakeholders briefed"
],
"reviewTemplate": "Outcome: The pilot informed the next release.\nExpected and matched: Pilot completed\nMissing: Stakeholders briefed\nUnexpected: Report published\nRoot causes: [to complete]\nLessons: [to complete]",
"unexpectedActions": [
"Report published"
]
}
}Limitations and assumptions
No root-cause inference, outcome verification or automatic action execution occurs.
Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Core numeric and string lists are limited to 100,000 entries; text entries are subject to the general large-text limit. Follow any smaller calculation limits above. Extremely large text inputs are rejected. Missing fields without a declared default, extra fields, wrong value types and violations of the calculation rules are input errors.
Alternative or Complementary methods
Use Signal Insight Action Pipeline Stage Tracker: A signal-to-action pipeline distinguishes observation, interpretation, action and completion. Stage labels determine the next template prompt. For a complementary task, use Assumption Reversal Question Generator: Reversing an assumption can prompt alternative strategies and evidence tests. The template creates questions rather than a logically derived negation.
References
Similar or alternative tools
- Signal Insight Action Pipeline Stage Tracker
A signal-to-action pipeline distinguishes observation, interpretation, action and completion. Stage labels determine the next template prompt.
- Assumption Reversal Question Generator
Reversing an assumption can prompt alternative strategies and evidence tests. The template creates questions rather than a logically derived negation.