Running-Sheet Coverage
Audit running-sheet action coverage.
Description
A running sheet records production actions and their cues.
A running sheet records production actions and their cues. Comparing required action labels with documented labels exposes omissions before detailed cue review.1
Audit running-sheet action coverage.
When to use Running-Sheet Coverage
Use this tool to audit running-sheet action 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 Running-Sheet 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 requiredActions, documentedActions 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 |
|---|---|---|---|
| requiredActions | Required running-sheet actions | list of string | Required |
| documentedActions | Documented actions | list of string | Required |
Enter requiredActions and documentedActions 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": {
"requiredActions": [
"alpha",
"beta",
"gamma",
"delta"
],
"documentedActions": [
"beta",
"alpha",
"extra"
]
},
"output": {
"coveragePercent": 50,
"matched": [
"alpha",
"beta"
],
"missing": [
"gamma",
"delta"
],
"unexpected": [
"extra"
]
}
} Limitations and assumptions
It does not inspect cue order, timing, staffing or the action text. 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 Show-Report Coverage: Audit nightly show-report section coverage. For a complementary task, use Quick-Change Handoff: Budget a quick-change handoff with task overlap and required buffer.
References
-
Running-Sheet Coverage — tool.io
Similar or alternative tools
- Show-Report Coverage
Audit nightly show-report section coverage.
- Quick-Change Handoff
Budget a quick-change handoff with task overlap and required buffer.