Written . Original operational guidance, not legal advice.
Inventory before transferring
A handoff starts with a list of datasets and their owners, not a bulk upload. Record why each dataset exists, who is authorized to receive it and which version is authoritative. Keep official-office, campaign and unrelated personal information appropriately separated. Do not use a public product tour as a transfer destination.
- Dataset name, responsible owner and permitted recipient
- Source system and export date
- Field definitions and identifier meanings
- Sensitive fields that must be excluded or handled separately
Preserve context and exceptions
Store a read-only source copy in an approved location and record the transformation steps used for the working copy. Explain how blank values, duplicates and corrections were handled. A row count alone does not prove that two exports contain equivalent records or that financial totals reconcile.
- Known missing records or unresolved duplicates
- Corrections made after the export
- Outstanding reviews and the person responsible
- Expected reconciliation checks and recorded results
Confirm the receiving workflow
Ask the receiving coordinator to locate a representative record, explain its status and identify the next administrative action. Check that the information needed for that explanation survived the handoff. Then confirm access changes, retention instructions and any required deletion with the responsible owner rather than assuming the old account can remain indefinitely.
This is operational software guidance, not a legal retention policy. Required retention and reporting obligations depend on the record and jurisdiction. Consult the applicable official guidance and qualified advisers. The BlueRoots glossary links to federal definitions, but neither the glossary nor the demo establishes compliance.