PBC Request Status Summary
Summarize caller-supplied PBC request statuses into stable status counts.
Description
PBC request status summaries help track client-provided audit information.
PBC request status summaries help track client-provided audit information.1
Summarize caller-supplied PBC request statuses into stable status counts.
When to use PBC Request Status Summary
Use this tool to summarize caller-supplied PBC request statuses into stable status counts.
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 PBC Request Status Summary 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 statuses using the field table and calculation rules, then run the tool.
- Read openCount, inProgressCount, completeCount, blockedCount, unknownCount. 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 |
|---|---|---|---|
| statuses | PBC request statuses | list of string | Required |
Enter status strings, trim/lowercase and return five counts. Empty lists are allowed.
count normalized open/in-progress/complete/blocked; remainder unknown Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| openCount | Open count | integer; minimum: 0 |
| inProgressCount | In-progress count | integer; minimum: 0 |
| completeCount | Complete count | integer; minimum: 0 |
| blockedCount | Blocked count | integer; minimum: 0 |
| unknownCount | Unknown count | integer; minimum: 0 |
{
"input": {
"statuses": [
"open",
"complete",
"in-progress",
"blocked",
"complete"
]
},
"output": {
"openCount": 1,
"inProgressCount": 1,
"completeCount": 2,
"blockedCount": 1,
"unknownCount": 0
}
}Limitations and assumptions
Blank/alternative labels count as unknown. No requests are sent and completeness of evidence is not verified.
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 Committee Preread Coverage: Audit audit-committee preread coverage. For a complementary task, use Remediation Aging: Age remediation findings against a caller-supplied target.
References
-
PBC Request Status Summary — tool.io
Similar or alternative tools
- Committee Preread Coverage
Audit audit-committee preread coverage.
- Remediation Aging
Age remediation findings against a caller-supplied target.