Independent technical practice

Commercial and contract dispute data gathering package

Map contract versions, email, collaboration, accounting records and logs before discussing preservation and collection with counsel.

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 technical consultant locate the records of negotiation, agreement, performance, payment and change across business systems.

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

Contract and commercial disputes, including digital agreements and performance records. Relevance, interpretation, damages and admissibility remain professional legal/expert work.

Before you gather

  • Build a transaction chronology with contract/project/customer IDs. Collect the executed agreement together with incorporated schedules, amendments, approvals and actual performance records. The documents that explain a deal can sit in different legal, sales, finance, engineering and provider systems.
  • A PDF of the signed contract may omit the negotiation history, referenced cloud document, signature envelope history and completion certificate. A current CRM report may omit prior field values and attachments. Ask the system owner what the actual export includes.
  • Source data, displayed reports and later calculations are different records. Preserve the source and identify how a report or damages schedule was prepared, including filters, assumptions, underlying transaction IDs and cutoffs. Do not infer a breach, assent or the amount of loss from a record category.
  • Sample discovery questions require counsel to tailor defined terms, dates and scope and to review interrogatory limits, burden, privilege, third-party control, local rules and case orders. They are not instructions to serve broad requests unchanged.

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.

CON-R01 Matter and transaction crosswalk

Ask
Counsel and business owner
Gather
Claims/issues, parties and roles, key dates, agreement/project/order/customer IDs, relevant entities, periods and disputed provisions.
Where to ask
Counsel, sales and contract team
Why it may be needed
Links a legal question to actual business systems and identifiers.
If missing or uncertain
Separate disputed interpretation from agreed facts; record missing IDs.

Reference: LG01 26; NY05 11-c

LG01 NY05

CON-R02 Agreement and incorporated material

Ask
Contract owner
Gather
Executed agreements, exhibits, referenced documents, statements of work, amendments, side letters, notices and version/effective dates.
Where to ask
Legal files, CLM, DMS and deal room
Why it may be needed
Defines which record family the specialist should organize.
If missing or uncertain
Identify missing incorporated documents or external links; do not assume the visible PDF is complete.

Reference: LG01 34; NI04

LG01 NI04

CON-R03 Drafts and negotiation

Ask
Counsel, sales and document owners
Gather
Relevant drafts/redlines/comments, version history, approval chains, emails/chats and negotiation notes within counsel-approved scope.
Where to ask
Mail, collaboration, DMS and CLM
Why it may be needed
Shows development of the agreement and the actual custodians.
If missing or uncertain
Counsel handles privilege; collect/segregate factual metadata without demanding advice in general questionnaires.

Reference: LG01 26(b)(5); NY05 11-b; MS05

LG01 NY05 MS05

CON-R04 Signature and acceptance records

Ask
Signing-service and contract owners
Gather
Envelope/agreement IDs, signed originals, history, completion certificate, recipient roles, delivery and acceptance records.
Where to ask
Signing provider, email and contracting system
Why it may be needed
Supplies supporting transaction records beyond the signature image.
If missing or uncertain
Availability is account/permission/retention dependent. Ask provider for the exact scope and field meanings.

Reference: DS01; LG02

DS01 LG02

CON-R05 Sales and commitments

Ask
Sales operations
Gather
CRM opportunities/quotes, product representations, pricing versions, approvals, attachments and relevant activity/history.
Where to ask
CRM, quoting tool, mail and proposals
Why it may be needed
Locates commercial representations and approval records.
If missing or uncertain
Determine available object/field history and linked-file capture; no universal CRM export is assumed.

Reference: NI04; LG01

NI04 LG01

CON-R06 Procurement delivery and performance

Ask
Operations and project manager
Gather
Orders, shipment/delivery/receipt, work logs, milestones, acceptance/rejection, service tickets, quality records and change requests.
Where to ask
ERP, logistics, project, service and quality systems
Why it may be needed
Enables a chronology of performance and disputes.
If missing or uncertain
Record separate date meanings and partial deliveries; identify third-party records.

Reference: NI04; LG01

NI04 LG01

CON-R07 Engineering and service versions

Ask
Engineering and service owner
Gather
Product/software/configuration versions, repository releases, change approvals, requirements and relevant existing technical logs.
Where to ask
Repositories, change systems and providers
Why it may be needed
Can connect what was promised, delivered, changed and supported.
If missing or uncertain
A current version is not evidence of the earlier deployment. Ask for historical records and limitations.

Reference: NI04

NI04

CON-R08 Invoices payments and adjustments

Ask
Finance
Gather
Invoices, credits, payment/remittance records, accounts receivable/payable, journals, approval history and disputed bank-detail changes.
Where to ask
ERP, banking records through owner, procurement
Why it may be needed
Supports traceable transaction and chronology review.
If missing or uncertain
Identify system/report cutoffs, currency and adjustments; specialist evaluates financial meaning.

Reference: NI04; LG01

NI04 LG01

CON-R09 Communications and meeting material

Ask
Custodians and collaboration owner
Gather
Relevant mail, chats, calls/recordings if made, minutes, internal/external channels and linked attachments.
Where to ask
D04 to D12 and D19
Why it may be needed
Captures non-email discussions and external-party collaboration.
If missing or uncertain
Identify unsupported meeting content, external retention and unavailable recordings; no assumed call recording.

Reference: MS02; GO01; SL02

MS02 GO01 SL02

CON-R10 Damages inputs and workbooks

Ask
Finance and counsel
Gather
Existing source transactions, calculation files with formulas, assumptions, revisions and relationship to the claimed categories.
Where to ask
Finance systems and working files
Why it may be needed
Allows experts to test or explain calculations later.
If missing or uncertain
Keep native spreadsheets and source IDs. A PDF summary is not the calculation model.

Reference: LG01 26; NI04

LG01 NI04

CON-R11 Archives backups and former platforms

Ask
IT, archive and migration owners
Gather
D19 to D21, older deal rooms/tenants, catalogs, relevant dates and restoration feasibility.
Where to ask
Historical systems and providers
Why it may be needed
Identifies records that a present application search misses.
If missing or uncertain
Specialist evaluates proportionate isolated restoration; coordinator records known cost and access barriers.

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

LG01 NI04

CON-R12 Third-party and legal-practice copies

Ask
Counsel and legal operations
Gather
Counterparty, broker, logistics, advisers, insurer and practice-management source inventory, including portals and separate module exports.
Where to ask
D28 and D35
Why it may be needed
Reveals distinct copies and possible lawful request paths.
If missing or uncertain
An adviser relationship is not authority for every file. Privilege and control need counsel review.

Reference: LG01 34,45; CL01

LG01 CL01

CON-R13 Preservation and collection report

Ask
Counsel and collector
Gather
Actual preservation/collection, source list, time zone, queries/filters, versions, exports, errors, chain of custody and known exclusions.
Where to ask
Preservation file and collection reports
Why it may be needed
Allows the receiving specialist to understand the record set limits.
If missing or uncertain
Record incomplete families, unresolved links and missing periods; do not overwrite originals with corrected reconstructions.

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 IDs join the agreement, quote, order, project, invoice and support case?

Suggested responder
Client IT or system owner
Useful supporting record
Crosswalk with system owners and date definitions.

2. Where are versions, comments, approvals and side agreements kept?

Suggested responder
Client IT or system owner
Useful supporting record
DMS/CLM/workspace paths and relevant custodians.

3. What does the executed-contract export omit?

Suggested responder
Client IT or system owner
Useful supporting record
List of incorporated documents, signature artifacts and linked files.

4. Which records show delivery, acceptance, rejection or a requested change?

Suggested responder
Client IT or system owner
Useful supporting record
Existing operation records and their authors/dates.

5. How are sales/finance records corrected and can prior values be retrieved?

Suggested responder
Client IT or system owner
Useful supporting record
Audit/history settings and reports for the period.

6. Which outside parties hold distinct performance or transaction records?

Suggested responder
Client IT or system owner
Useful supporting record
Third-party source list, ownership and proposed counsel request route.

7. How was each existing damages schedule generated?

Suggested responder
Client IT or system owner
Useful supporting record
Native workbook, source IDs, filters, periods and assumptions.

8. What was migrated or deleted, and what remains available elsewhere?

Suggested responder
Client IT or system owner
Useful supporting record
Migration/reconciliation and retention records.

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 and repositories of the agreement identified as [agreement ID] and its incorporated schedules and amendments.
  2. Identify the systems used to store drafts, revisions and approvals for [defined agreement] during [period].
  3. Identify the signing-service envelope or agreement identifiers and the custodian of the available history and completion certificate.
  4. Identify the order, project, invoice and support identifiers associated with [defined transaction].
  5. Identify the sources of records concerning [specified delivery or acceptance event] and their responsible custodians.
  6. Describe the report, fields, filters and source records used to prepare [identified factual transaction summary], excluding privileged advice.
  7. Identify relevant third-party repositories and the factual basis of the responding party control over records within them.
  8. Identify known retention, migration or export limitations affecting [defined record class] during [period].

Download the drafting worksheet

Worked gathering example

Example only: An invoice dispute references a change order signed through an electronic-signature service. The gathering team links the order ID, signed document, incorporated scope, envelope history and project acceptance records. It records missing sources; it does not decide whether the change was legally effective.

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.

CON-Q01 Which agreement family, period and transaction issues define the request?

Ask
Counsel with business owner
Gather
Claim/case documents, agreement IDs, chronology and contract family
Resolution needed
Written scope and proposed search/collection plan.

CON-Q02 Which reports omit history, attachments or relationships?

Ask
Application owner and receiving consultant
Gather
Export documentation, data dictionary, sample and error reports
Resolution needed
Documented export plan and limitations, not an assumed complete report.

Download the open-question register

Preparing the handoff

  • Agreement and transaction IDs connect records across systems.
  • Source records, summaries and calculated schedules remain distinguishable.
  • Signature events and ordinary business records support later evaluation without being treated as conclusive proof.
  • Counsel-approved scope, privilege handling and known gaps accompany the file index.

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.