Disagreement Resolution
Summarize draft-report disagreement resolution and escalation status.
Description
Disagreement tracking distinguishes open issues from previously resolved issues.
Disagreement tracking distinguishes open issues from previously resolved issues. Material open items can trigger escalation.1
Summarize draft-report disagreement resolution and escalation status.
When to use Disagreement Resolution
Use this tool to summarize draft-report disagreement resolution and escalation status.
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 Disagreement Resolution 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 openDisagreements, materialDisagreements, resolvedDisagreements, governanceNotified using the field table and calculation rules, then run the tool.
- Read unresolvedCount, resolutionPercent, status. 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 |
|---|---|---|---|
| openDisagreements | Open disagreements | integer; minimum: 0 | Required |
| materialDisagreements | Material disagreements | integer; minimum: 0 | Required |
| resolvedDisagreements | Resolved disagreements | integer; minimum: 0 | Required |
| governanceNotified | Governance notified when required | boolean | Required |
Enter nonnegative integers with materialOpen≤open and governance flag. Return unresolved=open; total zero gives 100%. Escalate material open without notification, else action-required if open, else clear.
resolution%=100resolved/(open+resolved) Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| unresolvedCount | Unresolved disagreements | integer; minimum: 0 |
| resolutionPercent | Resolution rate (%) | number; minimum: 0; maximum: 100 |
| status | Resolution status | string; one of "clear", "action-required", "escalate" |
{
"input": {
"openDisagreements": 1,
"materialDisagreements": 1,
"resolvedDisagreements": 3,
"governanceNotified": true
},
"output": {
"unresolvedCount": 1,
"resolutionPercent": 75,
"status": "action-required"
}
}Limitations and assumptions
No disagreement merits, resolution evidence or reporting obligations are decided.
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 Open-Item Certification: Roll forward audit issues and assess zero-open-item certification readiness. For a complementary task, use Cold-Review Escalation: Route post-signoff cold-review findings by impact and remediation status.
References
-
Disagreement Resolution — tool.io
Similar or alternative tools
- Open-Item Certification
Roll forward audit issues and assess zero-open-item certification readiness.
- Cold-Review Escalation
Route post-signoff cold-review findings by impact and remediation status.