Show-Report Coverage
Audit nightly show-report section coverage.
Description
A nightly show report organizes performance observations into sections so departments can follow up.
A nightly show report organizes performance observations into sections so departments can follow up. Section coverage measures the presence of required headings rather than the quality of their contents.1
Audit nightly show-report section coverage.
When to use Show-Report Coverage
Use this tool to audit nightly show-report section coverage.
Prepare production measurements or checklist records for one planning period. Confirm units, staffing assumptions and caller-selected criteria before running the calculation.
How to use Show-Report Coverage and understand its results
- Prepare production measurements or checklist records for one planning period. Confirm units, staffing assumptions and caller-selected criteria before running the calculation.
- Enter requiredSections, presentSections 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 |
|---|---|---|---|
| requiredSections | Required show-report sections | list of string | Required |
| presentSections | Present sections | list of string | Required |
Enter requiredSections and presentSections label lists. Trim labels, reject blank entries and match case-insensitively with en-US lowercase. Deduplicate each list, requiring at least one distinct required item; an empty observed list is allowed. Return matched, missing, unexpected labels and coverage. Duplicate normalized labels keep their last trimmed spelling at the first key position.
coverage%=100 matchedDistinctRequirements/distinctRequirements 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": {
"requiredSections": [
"alpha",
"beta",
"gamma",
"delta"
],
"presentSections": [
"beta",
"alpha",
"extra"
]
},
"output": {
"coveragePercent": 50,
"matched": [
"alpha",
"beta"
],
"missing": [
"gamma",
"delta"
],
"unexpected": [
"extra"
]
}
} Limitations and assumptions
It does not read a report or judge incident documentation and follow-up. Spelling differences beyond case and outer whitespace remain distinct.
Numeric inputs 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 Running-Sheet Coverage: Audit running-sheet action coverage. For a complementary task, use Rigging Sign-Off Audit: Audit required rigging sign-offs.
References
-
Show-Report Coverage — tool.io
Similar or alternative tools
- Running-Sheet Coverage
Audit running-sheet action coverage.
- Rigging Sign-Off Audit
Audit required rigging sign-offs.