Independent technical practice

Departed employee data gathering package

Identify devices, cloud accounts, messages, archives and logs for a departed-employee matter. Prepare questions for counsel and client IT.

Bagged hard drive beside a forensic write blocker.

Global Digital Forensics · Information gathering library · October 18 2026

Edition GATHER-20261018-01 · Information-gathering edition

Read this guide freely. Request download access with your name and email.

GDF records the selected resource in its lead intake and private Stats.

Open your emailed link for seven days of preparation downloads in this browser.

No marketing subscription is created. Keep completed records in controlled systems.

Help counsel and a forensic consultant identify relevant people, devices, accounts, repositories and short-lived records before collection.

Attorneys, paralegals, business/medical contacts, project coordinators and client IT

Employment, confidential-information and departure disputes. This package does not assume theft, recoverability, employer ownership of personal accounts or authority to access another organization.

Before you gather

  • Begin with the alleged events and dates, not a request for every record on every device. Ask counsel to identify issues, custodians, time ranges and preservation priorities. Include records that may support or contradict the allegation.
  • Account disablement, license removal, transfer of ownership, device wipe and replacement can affect evidence. Coordinate security containment and preservation with counsel and authorized IT. The package does not require delaying necessary containment; document what changed and when.
  • A cloud-sync icon does not establish that a complete file resides locally. An email can link to a cloud document rather than attach it. Content, versions, sharing/access records and identity events may require different requests.
  • Federal and New York practice differ. Counsel should review preservation, proportionality, possession/custody/control, privacy, privilege, local rules and case orders. New York CPLR 3130 limits use of interrogatories in specified circumstances; commercial and uniform rules impose further limits. The sample questions are a drafting bank, not a ready-to-serve set.

Give each request to the suggested owner. Record what is available and what is unknown in the editable CSV checklist. Use a secure evidence location agreed with the recipient; the checklist is an index, not a place for passwords, real patient data or controlled technical information.

Records to find

Download the editable gathering checklist. CSV files contain plain records, without saved column widths or workbook formatting. Import as UTF-8, keep IDs as text, wrap text and widen columns before use. Blank client fields are intentional.

EMP-R01 Matter facts and timeline

Ask
Counsel and HR
Gather
Employment/role dates, departure timeline, relevant business files/events, parties, issues and permitted time range.
Where to ask
HR, manager and counsel
Why it may be needed
Directs a proportionate information request without presuming wrongdoing.
If missing or uncertain
Separate known facts, allegations and questions.

Reference: LG01 26; NY05 11-c

LG01 NY05

EMP-R02 Preservation and offboarding status

Ask
Counsel and authorized IT
Gather
Hold instructions/implementation, relevant retention settings, pending deletions, license changes, account disabling, wipes and replacement/reassignment records.
Where to ask
Counsel, messaging, identity and endpoint owner
Why it may be needed
Identifies time-sensitive risk of losing relevant information.
If missing or uncertain
Escalate imminent deletion or unknown hold coverage; no guarantee that a late hold recovers deleted data.

Reference: LG01 37(e); MS03; GO01

LG01 MS03 GO01

EMP-R03 Custodian and identifier list

Ask
HR and IT
Gather
Names, roles, aliases, employee/user IDs, email addresses, tenant/domain IDs, device IDs and relevant shared/group accounts.
Where to ask
HR, identity and asset systems
Why it may be needed
Allows the collector to resolve actual identities and sources.
If missing or uncertain
Record gaps for shared/renamed accounts and former/acquired domains.

Reference: NI04; MS01

NI04 MS01

EMP-R04 Devices and media

Ask
Asset owner and custodian
Gather
D01 to D03 and any home/personal device used for work, with ownership, location, custody, status and authority unresolved where appropriate.
Where to ask
Asset records and interviews
Why it may be needed
Surfaces devices and removable copies beyond the returned laptop.
If missing or uncertain
Ask counsel before seeking personal-device data; do not self-image or explore it.

Reference: NI04; LG01

NI04 LG01

EMP-R05 Mail calendars and archives

Ask
Messaging and archive owner
Gather
D04/D08/D19, shared/delegated mail, aliases, mail journals, archive migrations and relevant holds.
Where to ask
Messaging and archive systems
Why it may be needed
An individual active mailbox may omit the relevant communications.
If missing or uncertain
Identify archived/inactive/deleted sources and documented capture gaps.

Reference: MS01; GO01; NI04

MS01 GO01 NI04

EMP-R06 Work drives and shared files

Ask
Cloud/file administrators
Gather
D05/D06/D09/D25, exact site/share paths, owners, external links, versions and relevant sharing records.
Where to ask
File servers, OneDrive, SharePoint, Drive and DMS
Why it may be needed
Finds the cloud original and collaboration history beyond synced copies.
If missing or uncertain
List external-owner links and recycle-bin/hold limitations.

Reference: MS03; MS05; GO01

MS03 MS05 GO01

EMP-R07 Messages and meetings

Ask
Collaboration owners and custodians
Gather
D07/D10/D11/D12, direct/group chats, external/shared channels, recordings/transcripts and linked attachments.
Where to ask
Collaboration systems and interview
Why it may be needed
Identifies communications that were never email.
If missing or uncertain
Ask about actual apps, subscriptions, history and limits; do not promise deleted-message recovery.

Reference: MS02; GO01; SL01; SL02

MS02 GO01 SL01 SL02

EMP-R08 Access transfer and security traces

Ask
Security and network teams
Gather
D13 to D18 and relevant D34; log coverage, earliest/latest dates, field legend, device/IP mappings and permissions.
Where to ask
Identity, SIEM/EDR/DLP, VPN, proxy and cloud admins
Why it may be needed
Lets the forensic specialist evaluate leads and gaps.
If missing or uncertain
Do not label an alert, download or USB event as theft. Record unknown actor/content and missing coverage.

Reference: NI04; MS04; GO02; AW01

NI04 MS04 GO02 AW01

EMP-R09 Business and project sources

Ask
Business and application owners
Gather
D22 to D28, customer/project lists, code/design repositories, tickets and relevant documents/workflows.
Where to ask
CRM, engineering, projects and practice systems
Why it may be needed
Can show legitimate work, chronology and alternate explanations as well as disputed activity.
If missing or uncertain
Identify actual modules and export omissions rather than assuming the current report is complete.

Reference: NI04; CL01

NI04 CL01

EMP-R10 Backups and historical environments

Ask
Backup/migration owner
Gather
D20/D21, catalogs, retention/overwrite dates, restore dependencies, keys held by owner and earlier export copies.
Where to ask
Backup provider and migration project
Why it may be needed
Determines whether potentially relevant earlier copies exist.
If missing or uncertain
Request a cost/scope estimate for specialist-planned isolated restoration; do not alter production.

Reference: NI04; LG01 26(b)(2)

NI04 LG01

EMP-R11 Personal external and third-party sources

Ask
Counsel and custodian
Gather
Known work-related external accounts, recipient organizations and relevant third-party systems, with the basis for knowledge and control.
Where to ask
Interview and business records
Why it may be needed
Enables counsel to choose consent, party request or lawful third-party process.
If missing or uncertain
No guessed passwords, bypassing access or blanket demands for private accounts.

Reference: LG01 34,45; NY05

LG01 NY05

EMP-R12 Collection and response index

Ask
Coordinator and collector
Gather
What was actually preserved/collected, who performed it, exact scope/filters, date/time zone, hashes where used, errors and missing sources.
Where to ask
Collection report and file index
Why it may be needed
Allows the receiving expert to assess coverage and request remaining work.
If missing or uncertain
A successful download or zero search result is not proof of completeness or absence.

Reference: NI04; MS06

NI04 MS06

Questions for client IT and owners

Download the response template. A useful answer names the actual system, period, supporting record and limits. If you do not know, name the person or provider who can answer.

1. Which accounts and devices did the person use for the relevant work, including shared and renamed accounts?

Suggested responder
Client IT or system owner
Useful supporting record
Identifier crosswalk with dates and ownership.

2. Which offboarding actions have occurred and what remains scheduled?

Suggested responder
Client IT or system owner
Useful supporting record
Dated action/change records and preservation confirmation.

3. Where do linked cloud files live, and who owns the external/shared copies?

Suggested responder
Client IT or system owner
Useful supporting record
Exact tenant/site/share/workspace IDs and owner list.

4. Which non-email tools did the person and coworkers actually use?

Suggested responder
Client IT or system owner
Useful supporting record
Custodian interview notes with apps/accounts and purpose.

5. What event types were logged at the time and how far back can each source be retrieved?

Suggested responder
Client IT or system owner
Useful supporting record
Coverage/retention table, earliest/latest examples and field legend.

6. Could a device, account, IP or badge have been shared or used by an administrator?

Suggested responder
Client IT or system owner
Useful supporting record
Assignment, delegation and remote-support records.

7. What migrations, deletions, license changes or policy changes may have affected records?

Suggested responder
Client IT or system owner
Useful supporting record
Change log with known gaps and decision owners.

8. What can a permitted export omit, and which errors or unindexed items need separate work?

Suggested responder
Client IT or system owner
Useful supporting record
Export process report and documented limitations.

Sample questions for counsel

Sample questions are drafting prompts for counsel. They are not a complete discovery request or a direction to serve them. Define the event, source, period and parties. Check relevance, proportionality, privilege, privacy, possession/custody/control, current local rules and case orders. Federal Rule 33 ordinarily limits interrogatories to 25 including discrete subparts absent stipulation or order. New York uniform and Commercial Division rules and CPLR 3130 impose separate limits and restrictions; especially check the interrogatory/deposition choice in negligence personal injury/property/wrongful-death actions. Split or narrow prompts only as permitted; do not disguise subparts. Use a document request, interview or deposition topic where that is the appropriate device. No requests are sent by these packages.

Supporting procedural sources: LG01, NY05, NY06, NY07 and NY08. These questions are separate from the internal IT interview.

LG01 NY05 NY06 NY07 NY08
  1. Identify the custodians of records concerning [defined disputed event] during [period] and each custodian role.
  2. Identify the devices assigned to [person] during [period], including their unique identifiers and current custodian.
  3. Identify the business accounts used by [person] for [defined project], including aliases and shared accounts.
  4. Identify the repositories holding [defined project records] during [period], their responsible administrators and relevant external owners.
  5. Describe the retention/deletion settings applicable to [defined source] during [period], including material changes and known data gaps.
  6. Identify the log sources that record [defined activity] for [period] and the person able to explain their coverage and fields.
  7. Identify the preservation and collection actions actually taken for [defined source], including dates and persons performing them, without requesting privileged advice.
  8. Identify responsive sources not searched or produced and the factual basis for claimed inaccessibility or limitation, subject to the applicable rules and orders.

Download the drafting worksheet

Worked gathering example

Example only: A returned laptop contains an online-only shortcut to a project folder. The coordinator records the shortcut and asks IT for the tenant/site owner, relevant versions and sharing records. The specialist chooses a collection method; the coordinator does not conclude the laptop contains the full folder.

Missing facts and specialist decisions

These are explicit handoff questions. Marking records Received does not resolve them. Add client-specific questions and a responsible person.

EMP-Q01 What sources and time ranges are proportionate and within lawful possession, custody or control?

Ask
Counsel
Gather
Claims, issues, chronology, ownership and proposed source inventory
Resolution needed
Counsel-approved scope and authority before collection; preserve separately where required.

EMP-Q02 Can the relevant activity be attributed, and what alternatives remain?

Ask
Forensic specialist
Gather
Original records, timestamps, IDs, mappings and limitations
Resolution needed
Expert analysis after collection, not a conclusion from a checklist or isolated log.

Download the open-question register

Preparing the handoff

  • Issue/date/custodian scope and authority are agreed with counsel.
  • Imminent deletion and offboarding actions are recorded and escalated.
  • Cloud/archives/backups and business systems are addressed alongside endpoints.
  • The source inventory distinguishes possible, confirmed, preserved and collected locations.

Download the record index. Use the shared walkthrough for custody, restricted records, missing information and receipt steps.

Sources for this package

Official laws/rules establish duties within their scope. Guidance explains programs; NIST supplies methods; vendor documentation describes possible product behavior. Actual contracts, facts, configuration and case orders still matter.

Privacy center

Choose your site settings

Optional technology stays off until you choose otherwise. You can change these browser settings at any time. Access to the core site does not depend on optional technologies.

Technology preferences
Sale or cross-context sharing: not used GDF does not sell or share website personal information for cross-context behavioral advertising.