Count accepted results alongside the effort of managing the work.
A fictional handbook update illustrates why generated drafts, review activity and accepted changes need different descriptions.
Original educational material. No worker survey, measured effort ratio or productivity finding is reported.
Define what counts as finished
Imagine a fictional project updating a handbook section. A draft has been produced, but its references have not been checked and the responsible owner has not accepted the change. Calling the section finished at that point would describe the completion of drafting while concealing the remaining work. The meaning of ‘finished’ needs to be clear before any comparison of activity is useful.
For this example, an accepted change would have an identified source, a completed review within the agreed scope and a clear decision about the version readers should use. Those conditions are illustrative, not a universal approval process. Their purpose is to make the endpoint understandable so that a generated paragraph is not confused with an accepted result.
Follow the path from a draft to an accepted result
Trace what happens after the first draft appears. A reviewer may verify a reference, ask for clarification, return an ambiguous sentence or confirm that the proposed wording preserves the intended meaning. These activities should be described in relation to the result they support. A long sequence of status changes is not necessarily evidence that the handbook has become more useful.
Keep unfinished and withdrawn work visible as well. A draft may be set aside because its source is obsolete or because another update already resolves the same question. That outcome is different from acceptance, even if substantial review effort was involved. Recording the distinction prevents an activity total from implying that every item reached the same endpoint.
Use a record that can explain the difference
A useful record identifies the item, its current state, the reason for that state and the next decision where work remains. It should help someone explain why a draft was accepted, returned or withdrawn. Avoid collapsing those outcomes into a single success label merely because each involved an interaction with a tool.
When comparing approaches, keep the task boundary and acceptance conditions consistent enough to understand the comparison. If one approach stops at drafting and another includes source review, describe that difference before interpreting their activity. This guide offers a way to connect work to a defined endpoint. It makes no claim about how actual employees divide their time or whether a particular technology increases productivity.