Tabletop Exercise Coverage
Audit futures tabletop exercise coverage.
Description
Tabletop exercises need coverage of agreed scenarios and response capabilities.
Tabletop exercises need coverage of agreed scenarios and response capabilities. Recorded topic coverage differs from demonstrated readiness.1
Audit futures tabletop exercise coverage.
When to use Tabletop Exercise Coverage
Use this tool to audit futures tabletop exercise coverage.
Prepare the recorded observations, ratings, assumptions or expected/observed lists requested. Choose thresholds and definitions appropriate to the planning question.
How to use Tabletop Exercise Coverage and understand its results
- Prepare the recorded observations, ratings, assumptions or expected/observed lists requested. Choose thresholds and definitions appropriate to the planning question.
- Enter requiredInjects, coveredInjects using the field table and calculation rules, then run the tool.
- Read coveragePercent, matched, missing, unexpected. 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 |
|---|---|---|---|
| requiredInjects | Required exercise injects | list of string | Required |
| coveredInjects | Covered injects | list of string | Required |
Enter requiredInjects as the nonempty expected list and coveredInjects as observations, which may be empty. Trim entries, compare case-insensitively using en-US lowercase and collapse duplicates. Return matched/missing expected labels and unexpected observed labels. Output follows first occurrence order with the last duplicate’s trimmed spelling.
coverage%=100matchedUnique/expectedUnique Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| coveragePercent | Coverage (%) | number; minimum: 0; maximum: 100 |
| matched | Matched items | list of string |
| missing | Missing items | list of string |
| unexpected | Unexpected items | list of string |
{
"input": {
"requiredInjects": [
"alpha",
"beta",
"gamma",
"delta"
],
"coveredInjects": [
"beta",
"alpha",
"extra"
]
},
"output": {
"coveragePercent": 50,
"matched": [
"alpha",
"beta"
],
"missing": [
"gamma",
"delta"
],
"unexpected": [
"extra"
]
}
}Limitations and assumptions
No exercise is conducted or response effectiveness measured. Blank entries are errors; requirements are entirely caller-supplied and items have equal weight.
Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Lists are limited to 100,000 entries; the rules above may require smaller limits. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.
Alternative or Complementary methods
Use Agent Workflow Autonomy: Classify agent-workflow autonomy from step and intervention counts. For a complementary task, use Five-Whys Chain: Check a five-whys chain for depth and repeated answers.
References
-
Tabletop Exercise Coverage — tool.io
Similar or alternative tools
- Agent Workflow Autonomy
Classify agent-workflow autonomy from step and intervention counts.
- Five-Whys Chain
Check a five-whys chain for depth and repeated answers.