A data retention handoff identifies billing evidence that must remain available and lets the next authorized person find it without receiving unnecessary sensitive data. Begin with record reference, owner-supplied rule, source location, version, and access boundary. Do not invent a universal retention period.

Retain context, not clutter

List original source, calculation, exception note, owner decision, resulting event, and later correction. A screenshot without context is weak. Record source path, capture date, timezone, and limitations. Keep the original in the approved system when possible.

Separate retention from access. A retained document may be unavailable to the assigned specialist. Mark access-limited and route approval properly. Do not use another account, remove protections, or export protected identifiers for convenience. The specialist may inventory and link; the owner decides uncertain disposition.

Use an index with purpose, version, date, owner, access state, and next review. Preserve superseded versions when they explain an earlier action. Reopen after a correction, reversal, audit request, or new evidence. Good retention preserves accountability as well as data.

### Control points

  • Name retained evidence and rule source.
  • Preserve version, date, timezone, and access.
  • Keep retention and access decisions separate.
  • Avoid informal exports.
  • Link owner disposition.
  • Preserve history when it explains a result.
  • Reopen after material events.
  • ## Operating notes

+1. Write the operating purpose in one sentence before naming a metric, because a number without a decision context can invite the wrong action.

+2. Use the smallest stable identifier available and record where it came from, while keeping unnecessary personal or account details inside approved systems.

+3. Preserve the source wording beside any summary so a later reviewer can distinguish an observed fact from a preparer's interpretation.

+4. Record the date an event occurred, the date it was received, and the date it was reviewed when those moments have different operational meanings.

+5. State the timezone and business-day convention before comparing records created by people or systems working in different locations.

+6. Keep a missing source separate from a source that was not searched, and keep both separate from a source that was found but access-limited.

+7. Describe a calculation with its inputs and formula so another specialist can reproduce it without trusting an unexplained remainder.

+8. Do not borrow a field from a similar record merely because the target record is incomplete; similarity is a search clue, not evidence.

+9. Give every exception a named owner and one bounded question, rather than sending a broad request that hides several unrelated decisions.

+10. Set a next review date that follows the evidence or deadline, and record why that date is appropriate to the source.

+11. Use a carry-forward state when work is incomplete at a cutoff, and preserve the reason instead of counting it as silently finished.

+12. Retain rejected candidate matches because they explain why a plausible alternative was not accepted by the reviewer.

+13. Keep preparation, approval, posting, correction, communication, and release as distinct events in the record.

+14. Make clear which role may inspect, calculate, draft, approve, change, or communicate each part of the workflow.

+15. Treat a later event as an addition to history; do not erase an earlier observation simply because the current state looks cleaner.

+16. Compare periods only after checking that the source population, filter, definitions, and exclusion rules are materially the same.

+17. Report excluded, duplicate-risk, access-blocked, and unresolved items beside completed items so the denominator remains understandable.

+18. Explain a changed category or filter before describing a lower queue count as improvement or a higher count as deterioration.

+19. Use a specific exception status that tells the next person what evidence is missing and what action is permitted next.

+20. Do not use a generic pending label when the queue is waiting for different people, sources, or decisions.

+21. Preserve the source path and capture time for portal checks, exports, correspondence, and generated reports.

+22. Limit copied information to what the next reviewer needs, particularly when a working note could otherwise expose protected data.

+23. Route permission questions through the approved owner path and never use another person's account to complete a check.

+24. Keep a version link when a report, invoice, claim, statement, or source document changes after the first review.

+25. Record the exact event that caused a row to reopen, rather than describing the reopening as a general correction.

+26. Close a row only when its approved result, documented hold, or accountable carry-forward is visible.

+27. Use a short final reconciliation to prove that the opening population did not lose records between intake and disposition.

+28. Review a sample of completed rows for source traceability, boundary compliance, and clear next action before trusting an aggregate measure.

+29. Escalate contradictions early, because a confident summary built on conflicting sources is harder to repair than an explicit unresolved state.

+30. Make the handoff useful to a new shift: source, current state, evidence, owner, question, deadline, and next review should be findable together.

Separate retention from convenience

Retention is not a reason to keep every working copy forever. Identify the authoritative record, its required retention rule, the owner of that rule, and the event that starts the retention period. A support specialist can label files, preserve lineage, and flag conflicting versions, but should not invent a retention period or delete evidence to tidy a queue. When access changes during a handoff, record the change and route permission questions through the approved owner so the retained record remains both available to the right role and protected from unnecessary exposure. ## Additional review note

A retention handoff should also state how the next reviewer can verify that a link still works without copying the underlying record. Record the approved repository, access owner, reference convention, and review date. If a source is scheduled for disposition, retain the disposition instruction and approval before action. A handoff that preserves context while respecting least access is more useful than a large uncontrolled archive.