How to read regulatory task rework as a risk metric

Regulatory task rework is the share of completed tasks that return to an earlier stage for clarification, correction or renewed approval. The measure is useful only when the workflow records why the task returned.

A basic register can capture the original assignment, the return date, the reason code and the stage to which the task was sent back. The reason codes should distinguish missing information from a changed interpretation or an approval issue.

Rework can indicate that the first handoff lacked enough context. It can also reflect a healthy review process catching a problem before implementation. The metric should therefore be read alongside the reasons, not as a standalone score.

The gaming risk is closing a task and opening a new one to avoid recording the return. The identity of the underlying issue must survive the handoff.