Practical guide
Review Mail Forwarding Before Offboarding
Define the need, recipient, duration, and privacy boundary before forwarding starts.
Published
Table of contents
Scope and operating boundary
Start with a case record containing the account, approved recipient, start and end times, excluded message classes, and approval. 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 access, retention, disclosure, deletion, or legal exceptions.
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 the temporary rule is verified and removed on its recorded expiry date. Record the source used, action taken, verification result, next owner, and date.