Rescope Change Log
Quantify audit rescoping changes and change-log completeness.
Description
Rescoping changes planned effort and risk coverage.
Rescoping changes planned effort and risk coverage. Counts help check whether recorded changes cover additions and removals.1
Quantify audit rescoping changes and change-log completeness.
When to use Rescope Change Log
Use this tool to quantify audit rescoping changes and change-log completeness.
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 Rescope Change Log 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 originalPlannedHours, revisedPlannedHours, addedRiskCount, removedRiskCount, documentedChangeCount using the field table and calculation rules, then run the tool.
- Read hourChange, hourChangePercent, netRiskChange, changeLogComplete. 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 |
|---|---|---|---|
| originalPlannedHours | Original planned hours (h) | number; minimum: 0 | Required |
| revisedPlannedHours | Revised planned hours (h) | number; minimum: 0 | Required |
| addedRiskCount | Added risks | integer; minimum: 0 | Required |
| removedRiskCount | Removed risks | integer; minimum: 0 | Required |
| documentedChangeCount | Documented scope changes | integer; minimum: 0 | Required |
Enter positive original hours and nonnegative revised hours/counts. Return signed hours/percentage/net risk change and documented≥required gate.
hourChange=revised−original; requiredChanges=added+removed Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| hourChange | Planned-hour change (h) | number |
| hourChangePercent | Planned-hour change (%) | number |
| netRiskChange | Net risk change | integer |
| changeLogComplete | Changes documented | boolean |
{
"input": {
"originalPlannedHours": 100,
"revisedPlannedHours": 120,
"addedRiskCount": 2,
"removedRiskCount": 1,
"documentedChangeCount": 3
},
"output": {
"hourChange": 20,
"hourChangePercent": 19.999999999999996,
"netRiskChange": 1,
"changeLogComplete": true
}
}Limitations and assumptions
Documentation counts are not matched to particular changes; no scope appropriateness is validated.
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. A successfully returned false flag is an evaluated outcome; its meaning is explained above.
Alternative or Complementary methods
Use Audit-Universe Coverage: Audit audit-universe entity and process coverage. For a complementary task, use Team-Debrief Coverage: Audit engagement debrief topic coverage.
References
-
Rescope Change Log — tool.io
Similar or alternative tools
- Audit-Universe Coverage
Audit audit-universe entity and process coverage.
- Team-Debrief Coverage
Audit engagement debrief topic coverage.