Practical guide
Verify an Employee Directory Role Change
Keep directory labels aligned with the approved role record and access process.
Published
Table of contents
Scope and operating boundary
Start with a case record containing the approved role record, effective date, destinations, current values, and request owner. 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.
Workflow and evidence controls
Coordination support can collect evidence, compare declared fields, maintain the queue, and route one precise question. The authorised owner decides reporting lines, permissions, compensation, or employment status.
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.
Quality review and exceptions
Close the check only when every named destination is verified or assigned to an exception owner. Record the source used, action taken, verification result, next owner, and date.