Scope-Limitation Decision
Route a scope limitation from supplied evidence and effect indicators.
Description
Scope limitations require evaluation of evidence alternatives and potential effects.
Scope limitations require evaluation of evidence alternatives and potential effects. This tool routes supplied facts mechanically.1
Route a scope limitation from supplied evidence and effect indicators.
When to use Scope-Limitation Decision
Use this tool to route a scope limitation from supplied evidence and effect indicators.
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 Scope-Limitation Decision 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 evidenceUnavailable, alternativeProceduresSuccessful, effectMaterial, effectPervasive, managementImposedLimitation using the field table and calculation rules, then run the tool.
- Read recommendedResponse, severityScore. 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 |
|---|---|---|---|
| evidenceUnavailable | Required evidence unavailable | boolean | Required |
| alternativeProceduresSuccessful | Alternative procedures successful | boolean | Required |
| effectMaterial | Potential effect is material | boolean | Required |
| effectPervasive | Potential effect is pervasive | boolean | Required |
| managementImposedLimitation | Limitation imposed by management | boolean | Required |
Enter booleans. Failed alternatives with management limitation take escalation priority; otherwise material/pervasive leads disclaimer-or-withdraw, material alone qualified-opinion, else continue.
score=max(0,unavailable+2material+3pervasive+2management−2alternatives) Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| recommendedResponse | Recommended response | string; one of "continue", "qualified-opinion", "disclaimer-or-withdraw", "escalate-management-limitation" |
| severityScore | Limitation severity score | integer; minimum: 0 |
{
"input": {
"evidenceUnavailable": true,
"alternativeProceduresSuccessful": false,
"effectMaterial": true,
"effectPervasive": false,
"managementImposedLimitation": false
},
"output": {
"recommendedResponse": "qualified-opinion",
"severityScore": 3
}
}Limitations and assumptions
The response logic does not gate on evidenceUnavailable. No opinion or withdrawal decision is issued and applicable standards must be assessed separately.
Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.
Alternative or Complementary methods
Use Sensitive-Matter Routing: Route sensitive audit matters from supplied indicators. For a complementary task, use Cold-Review Escalation: Route post-signoff cold-review findings by impact and remediation status.
References
-
Scope-Limitation Decision — tool.io
Similar or alternative tools
- Sensitive-Matter Routing
Route sensitive audit matters from supplied indicators.
- Cold-Review Escalation
Route post-signoff cold-review findings by impact and remediation status.