Start Here: Preparing a Useful Specialist Handoff

How to use this library

Begin with the records you already have.

Each package follows the same pattern. It opens with the facts to settle before you gather, lists the records to find with a suggested owner for each, gives a short question set for client IT and system owners, and closes with the decisions that belong to counsel or the receiving specialist. An unanswered question is a request for help, not evidence of a problem.

Work from the CSV worksheets. Import them as UTF-8, keep the ID columns as text, and widen and wrap the columns before you start. The blank response columns are for your entries. Each worksheet is an index: point to records held in your approved evidence location rather than pasting passwords, patient data or controlled technical information into it.

The first conversation

Open Intake-template.csv and settle seven topics with the business sponsor and counsel: the matter and organization, the purpose and who asked for the work, the period and locations, the people involved, the systems and data, any immediate concerns, and how records will be shared. Immediate concerns come first. An active incident, imminent deletion, expiring logs, a court order or a contractual deadline goes to counsel or the responsible specialist at once, ahead of the worksheet.

Walkthrough from request to handoff

Eight steps take a matter from the first request to a controlled handoff.

1. Name the matter and the recipient

Record the legal entity, business unit or case, the intended recipient, the purpose, the relevant period, the sites, the systems and the client contact. Ask the recipient which criteria, versions and deliverable format they expect. Keep an audit preparation request separate from an incident response or litigation deadline.

2. Identify people and places

Ask the business owner what work occurred and ask IT where the resulting information lives. Include providers, acquired businesses, former accounts, paper files and legacy systems. Start with the data source atlas and create one inventory row per actual tenant, repository or device, not one row per vendor name.

3. Check authority and preserve when necessary

Before anyone changes accounts, retention settings or content, ask counsel and the authorized system owner what must be preserved and who can act. Escalate short lived logs and pending deletions promptly. Check that each hold covers the intended scope and was applied successfully, and record the date it took effect.

4. Gather existing records safely

Request existing exports and documentation through approved channels. Ask for a scoped collection plan if forensic acquisition, production testing, restoration or third party access is needed. Use IDs and redacted examples until the receiving specialist confirms a secure route, and keep passwords, recovery secrets, private keys, patient records and controlled technical data out of ordinary email and web forms.

5. Describe what was supplied

Give every request an ID and every record an identifier. Record the source system, account or tenant, owner, period, collection time with time zone, method, filters, permissions, file format and known omissions. Where appropriate, the collector creates and verifies a cryptographic hash. A matching hash shows two copies are identical, so the specialist reviews exactly the record that was collected.

6. Show gaps and limits

Use the statuses Not started, Requested, Received awaiting specialist review, Partially received, Not available after inquiry, and Proposed not applicable awaiting confirmation. Explain a missing period, an excluded field, a failed export or an uncertainty. Keep Unknown as Unknown, and mark a request complete when every record it asks for has arrived.

7. Prepare a controlled handoff

Reconcile the request checklist with the file inventory. Separate ordinary records from restricted evidence and potentially privileged material. Agree access, permitted recipients, transmission encryption and retention, then obtain a receipt and list the follow up questions. The recipient decides whether the information supports the proposed engagement.

8. Keep the package current

Keep the edition and the date the sources were last checked with the handoff. Recheck the rules and vendor documentation before the next engagement and whenever the facts change. Version new submissions, keep the earlier index and explain the changes. Release a preservation hold or destroy records only on the decision of the owner and counsel.

Who helps with the gathering

Small organizations combine roles; the decisions stay with the person who holds the authority.

Suggested handoff folders

Use Record-index-template.csv for one row per file or defined record set: the request it answers, the original source, date range, collector and method, approved location and limits. Handoff-checklist.csv tracks the ten handoff steps.

Choosing the right package

Seven packages cover the most common requests. For other programs, the table shows what to collect first.

Common terms

Receiving the package and timing

Receiving the package

Ask the recipient to acknowledge what arrived, name any unreadable or missing files and confirm the next request. Keep their substantive review separate from the delivery receipt. A complete collection is the starting point the specialist works from for the audit, export review or test planning.

Timing and urgent matters

Agree gathering dates with the recipient based on records, access and provider availability. Those dates are project targets. Active incidents, imminent deletion, filing deadlines, litigation orders and pending transactions go to counsel or the responsible specialist immediately, outside the ordinary package schedule.