Audit-Universe Coverage
Audit audit-universe entity and process coverage.
Description
An audit universe identifies entities and processes considered for planning.
An audit universe identifies entities and processes considered for planning. Coverage is relative to that selected universe.1
Audit audit-universe entity and process coverage.
When to use Audit-Universe Coverage
Use this tool to audit audit-universe entity and process coverage.
Prepare the documented facts, aligned totals or expected/observed evidence labels requested. Choose applicable requirements and thresholds separately before interpreting a planning screen.
How to use Audit-Universe Coverage and understand its results
- Prepare the documented facts, aligned totals or expected/observed evidence labels requested. Choose applicable requirements and thresholds separately before interpreting a planning screen.
- Enter requiredEntities, coveredEntities 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 |
|---|---|---|---|
| requiredEntities | Required audit-universe entities | list of string | Required |
| coveredEntities | Covered entities | list of string | Required |
Enter requiredEntities as the nonempty expected list and coveredEntities 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": {
"requiredEntities": [
"alpha",
"beta",
"gamma",
"delta"
],
"coveredEntities": [
"beta",
"alpha",
"extra"
]
},
"output": {
"coveragePercent": 50,
"matched": [
"alpha",
"beta"
],
"missing": [
"gamma",
"delta"
],
"unexpected": [
"extra"
]
}
}Limitations and assumptions
No universe completeness, audit depth or risk coverage is independently verified. 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 Sampling Coverage: Measure audit sample coverage by item count and value. For a complementary task, use Rescope Change Log: Quantify audit rescoping changes and change-log completeness.
References
-
Audit-Universe Coverage — tool.io
Similar or alternative tools
- Sampling Coverage
Measure audit sample coverage by item count and value.
- Rescope Change Log
Quantify audit rescoping changes and change-log completeness.