Rigging Sign-Off Audit

Audit required rigging sign-offs.

Description

Rigging sign-offs document review or authorization steps defined for a production.

Rigging sign-offs document review or authorization steps defined for a production. A list match confirms recorded labels rather than inspecting equipment or authenticating approval.1

Audit required rigging sign-offs.

When to use Rigging Sign-Off Audit

Use this tool to audit required rigging sign-offs.

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 Rigging Sign-Off Audit and understand its results

  1. Prepare production measurements or checklist records for one planning period. Confirm units, staffing assumptions and caller-selected criteria before running the calculation.
  2. Enter requiredSignoffs, completedSignoffs using the field table and calculation rules, then run the tool.
  3. Read coveragePercent, matched, missing, unexpected. The explanation below defines the units, signs, ordering and any flags or placeholder values.
  4. 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 fieldMeaningValue type; see rules belowRequirement
requiredSignoffsRequired rigging sign-offslist of stringRequired
completedSignoffsCompleted sign-offslist of stringRequired

Enter requiredSignoffs and completedSignoffs 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 fieldMeaningValue type
coveragePercentCoverage (%)number; minimum: 0; maximum: 100
matchedMatched itemslist of string
missingMissing itemslist of string
unexpectedUnexpected itemslist of string
json
{
  "input": {
    "requiredSignoffs": [
      "alpha",
      "beta",
      "gamma"
    ],
    "completedSignoffs": [
      "beta",
      "alpha",
      "extra"
    ]
  },
  "output": {
    "coveragePercent": 66.66666666666666,
    "matched": [
      "alpha",
      "beta"
    ],
    "missing": [
      "gamma"
    ],
    "unexpected": [
      "extra"
    ]
  }
}

Limitations and assumptions

It does not verify signatory authority, inspect rigging or determine whether the chosen requirements satisfy applicable rules. 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 Rigging Inspection Due: Calculate the next rigging inspection date from a supplied interval. For a complementary task, use Show-Report Coverage: Audit nightly show-report section coverage.

References

  1. Rigging Sign-Off Audit — tool.io

Similar or alternative tools

Don't forget to set a bookmark for tool.io!
Privacy | Imprint | Cookies