Use a Pause Reason in Employment Service Tracking

Start with a case record containing the permitted pause reason, start event, owner, next check, restart event, and raw elapsed time. Keep corrections as dated events instead of overwriting the earlier state.

Use explicit states such as received, incomplete, conflicting, ready for review, accepted, returned, and cannot determine. A status needs a source event, not an assumption based on silence or familiarity.

Coordination support can collect evidence, compare declared fields, maintain the queue, and route one precise question. The authorised owner decides which pauses count, target thresholds, exceptions, or service outcomes.

Store private material in the approved restricted system and point to it from the operating record. Do not copy sensitive values into a shared tracker or public message.

Close the check only when the restart event is recorded and another reviewer can reproduce the calculation. Record the source used, action taken, verification result, next owner, and date.