Analyze current revision age and earlier review rounds without confusing a submitted file with completed acceptance.
Index
A document can move through several rounds with different owners. Time since its first submission does not tell you which revision currently awaits a response or where recurring outstanding work began.
The unit of analysis determines the result
The analytical unit should be document and review round. Retain submission date, response and the decision applied to that version. Current state informs today's action; historical rounds explain rework and accumulated time without turning every reply into another document.
A document platform may provide state reports. A custom layer fits organizations using different identifiers or responses arriving outside the platform. Records lacking confirmed links should remain in a data-quality queue instead of being joined because filenames happen to look similar.
Requirements for comparing BI proposals
- Define the event starting a round and the response ending its waiting interval.
- Separate returned-for-correction from conditional acceptance according to the contracted technical process.
- Show unanswered documents at the reference date with current round and owner retained.
A check before using the measure
In a hypothetical example, the first revision returns for correction while the second awaits the customer. Check each round's duration and current waiting age without counting the document twice as a deliverable. Add a response received with the wrong code and verify that it does not close another document accidentally.
Reference for assessing scope
Microsoft Learn: facts, dimensions and analytical model grain
Prepare your project with Quantum9
Bring Quantum9 a document package's history and the rules used to identify its revisions.