Start in your own words.
Develop the background, questions and scope in the case conversation. A versioned synopsis preserves the working brief, its history and author attribution. Supporting case files stay close.
Investigation, review and production software
Simply DiscovereDiscovery
Complex matters.
A clearer picture.
Bring conversations, people and evidence together. Follow the connections, review in context, and prepare a production with a record of the decisions behind it.
Follow the evidence- 01Understand the evidence
People, content and case context together.
- 02Reduce repeated work
From collection setup to focused follow-up.
- 03Explain the decisions
Review records and production checks.
The evidence. The connections. The case.
One matter.
Room to investigate.
Simply Discover eDiscovery connects evidence collection, investigation, review and production for legal teams, investigators and review professionals.
Explore the developing picture in an investigation workspace organised around Scope, Discover and Refine. Manage collection, processing, review, privilege, production and proof in the case workbench. Two complementary ways to work, with the matter's context retained.
An illustrative matter
“What changed in the Northstar agreement, who was involved, and when were the revised terms discussed?”
Maya Chen, commercial lead. Ellis Ward, external adviser. Fictional people and evidence, used throughout the examples below.
Consider the proposed setup.
The assistant can inspect configured sources and propose selections, labels and changes to entities or relationships. Examine proposals and accept or reject them before they are applied.
Keep the case in view.
Open synopsis, sources, custodians, labels, findings and files from the workspace dock. Move into a dedicated review surface with the case conversation available alongside it.
01 / Collect with purpose
The right sources.
A scope you can explain.
A contract question may reach across a mailbox, a chat and several document versions. Bring the relevant material into one matter, with a recorded boundary around the collection.
Reuse the connection. Define this collection.
Select an existing connection configuration, then set custodians, dates and repository locations. Browse SharePoint sites, OneDrive drives and folders deliberately. Scope previews, imported counts and source status make the selected material visible.
Keep a reference to what was collected.
Collection intelligence brings together connected sources, attached storage and external packages. Seal a versioned collection snapshot recording the source universe and integrity hashes. Export a collection proof pack with its manifest, membership information and audit events.
Collection depends on the configured connector, permissions and selected scope. Status shows what is queued, progressing, complete or needs attention.
Supported evidence sources
- Microsoft 365
- Mailbox collection through configured connections
- Gmail & Mimecast
- Correspondence through their source integrations
- Teams & Slack
- Supported conversations through a connector or export configuration
- SharePoint & OneDrive
- Selected sites, folders, drives and documents
- PST, MSG & EML
- Supported exported email files
- External packages
- Supported load files and associated content
Less routine handling. Visible progress.
Standard discovery processing excludes duplicate items from its initial selection. Reduction categories distinguish retained material from automated messages, mailing-list traffic, spam and exceptions. Import and classification status, category counts, pause states and failed work remain visible.
A controlled handover for external evidence.
Stage DAT, CSV or tab-delimited metadata with supported image load files, native files and extracted text. Save a versioned field mapping and validate before import. Failed validation prevents admission. Standard discovery's All Evidence review scope does not require AI classification first.
02 / Understand the connections
A name in an email.
A person in the picture.
An interactive entity graph brings people, organisations and relationships into view. Curate the connections as the investigation develops, and associate custodians with the people whose evidence you are examining.
Northstar agreementIllustrative investigation
Commercial teamAdvises on terms
People connected to sources and context
In the matter
Maya Chen
Commercial lead at Northstar, involved in the agreement discussions.
- Associated source
- Maya's Microsoft 365 mailbox
- Supporting context
- Email to Ellis, 12 June: requests revised terms before Friday.
- Question to examine
- Which version was discussed before the agreement changed?
The developing picture.
Add entities, edit relationship types and connect relevant custodians. The Context timeline records findings about people and relationships with supporting detection references.
The work behind it.
The Process timeline records investigation activity. Together with the curated graph, it gives a colleague taking over the matter a way to understand both the picture and how it developed.
03 / Read in context
A finding is a starting point.
The evidence is right there.
Classification can use the case synopsis, curated entity context and your configured labels. See summaries, rationale, confidence information and supporting passages, then make your own assessment.
Evidence & assessmentIllustrative email
12 June / Maya Chen to Ellis Ward
Northstar agreement: revised terms
Ellis,
Please send the revised terms before Friday. We need to compare them with the version discussed on Tuesday before the next meeting.
The commercial team has not yet confirmed the changes.
Maya
Agreement draft attached
Classify the item. Locate the passage.
Use whole-item labels for significance and passage extraction for matching phrases or details. Located excerpts appear as review highlights, so a classification can be checked against its source.
Find the next item, not the next tool.
Review email, chat and documents in a consistent list-and-detail surface. Search, labels, content types, unreviewed filters and named saved views help keep the queue focused.
Record the reviewer's decision.
Correct labels, adjust highlighted spans, make disclosure decisions and mark items reviewed. Discuss an item in the case conversation. Workbench review adds assignments, notes, issue tags and workflow flags.
04 / Follow the next question
New understanding.
Without starting over.
The first pass raises a narrower question: what did Ellis send in the days before the meeting? Refine the investigation through explicit proposals and human decisions.
Pause. Reflect. Decide.
Batch classification can pause for a reflection review. The assistant proposes coordinated changes to the synopsis, labels, entity relevance and graph based on material examined so far.
Approve the proposal, dismiss it, or exclude individual changes and approve the adjusted version. The workflow then resumes from that review point.
Proposed changes are reviewed before application.
A focused pass. Separate results.
A targeted probe proposes a follow-up classification over an email subset defined by sender, subject keywords or dates. Its proposal includes scope, rationale, classification and example evidence references.
Approval creates a separate scoped pass with its own definitions and results. Switch between the initial results and completed probes. The first pass remains available.
Example scope: Ellis · 10–14 June · revised terms
05 / Review with a shared basis
The strategy. The sample.
The sign-off.
A clear review process needs more than a completed queue. The governed review workflow connects the instructions, evidence population, validation and acceptance record.
- 01
Set the review strategy.
Record purpose, investigation questions, coding criteria, mode, context, exclusions and approval note in a versioned strategy. Promote a defined evidence population into a review set with a validation plan. Manual review is supported; governed AI runs also record the approved setup, evidence scope and execution provenance.
- 02
Validate against the evidence.
Review a recorded sample in a blinded evidence view and enter independent decisions. The validation record preserves the comparison with the original decisions. Adjudicate disagreements with a rationale while retaining the original validation outcomes.
- 03
Make acceptance specific.
Review and Quality Control sign-off are tied to the current strategy, review population, completion state and applicable validation evidence. QC requires a different authenticated reviewer from the Review signatory. Changes to the review basis supersede affected acceptance.
A record of what was checked, which evidence it covered and who accepted it.
06 / Prepare the right output
From reviewed evidence
to a considered production.
Communicate the findings, assemble reviewed material or prepare a formal Bates production. These are distinct outputs, with different purposes and workflows.
Investigation report
Explain the findings.
Synthesise completed classification passes into an executive summary, key findings, narrative and notable communications. Supporting excerpts, detection citations, severity and ownership can be included where available.
Generate and regenerate the report as completed analysis develops. It is a starting point for communicating findings, with references to check.
Reviewed-items pack
Assemble eligible material.
Build a pack from current review and disclosure decisions. Communications are assembled into PDF output, with eligible document outputs and the eDiscovery manifest in a ZIP.
Follow build phases and item progress, cancel if necessary and download on completion. This is not the formal Bates production workflow.
Bates production
Number. Package. Check.
Manage numbering series, assignments and previously assigned material. Produce manifests and structured load files with native and text mappings. Email export supports PST or ZIP, including a Bates-stamped PDF option within ZIP output.
Finalisation checks cover assignment state, ranges, required information, package assembly and hashes. Errors block finalisation and identify the affected details.
Privilege is an explicit decision.
Mark privilege-sensitive items pending review, withheld as privileged or cleared for production. Withhold by recognised item or Bates identifiers. Production protocols govern omission or placeholders, family handling, package changes and privilege-log requirements. Structured privilege logs record withheld material.
Redaction stays connected to review.
Use manual document and attachment redactions, with email redaction previews in relevance review. Investigation label and span decisions help determine reviewed-pack disclosure. Finalised productions retain event history; replacement productions can supersede earlier ones.
Our approach to redactionA matter with a record behind it
Explain the work.
Not just the result.
Collection snapshots, strategy versions, validation results, reviewer decisions and production events give the team a documented basis for supervision and handover.
The Proof and Audit workbench brings together package validation, production history, manifests and readiness information. Export collection proof, review records and production manifests from their respective workflows.
The collection boundary.
Recorded sources, membership, counts and integrity hashes.
The review basis.
Strategy, population, decisions, validation and sign-off.
The production history.
Assignments, checks, manifests and finalisation events.
Your environment. Controlled access.
Customer-hosted in Azure, AWS or on premises. Feature, role, case-access and applicable imported-data permissions govern sensitive actions and evidence.
More time for professional judgement
Less work around
each decision.
The advantage is practical: fewer repeated setup, reconstruction and packaging steps. Not a promise that every matter is simple.
| The repeated work | What changes with Simply Discover |
|---|---|
| Re-enter source details | Reuse connection configurations and select custodians and repositories. |
| Reconstruct the collection boundary | Refer to collection intelligence and a sealed scope snapshot. |
| Revisit routine traffic | Use duplicate exclusion and standard discovery reduction categories. |
| Read without the case context | Inspect synopsis-grounded classifications and supporting passages. |
| Build relationship maps in separate notes | Curate an entity graph with narratives and source associations. |
| Rebuild analysis for a narrower question | Approve a targeted probe with a separate scope and result set. |
| Recreate a useful review filter | Return to a named saved view. |
| Reconcile instructions and acceptance | Connect the versioned strategy, validation and Review/QC sign-off. |
| Assemble reviewed evidence by hand | Generate a reviewed-items pack with visible build progress. |
| Check numbering and outputs separately | Use Bates assignments, manifests and production checks. |
| Explain the process from memory | Use collection, review and production records for handover. |
eDiscovery software, explained
Useful answers.
A clearer starting point.
What does Simply Discover eDiscovery do?
It supports collection, investigation, evidence review and production in one platform. Legal teams and investigators can explore case context and relationships; review teams can assess content; review managers can validate decisions; IT and litigation support teams can manage scoped collection and structured outputs.
Which evidence sources are supported?
Microsoft 365 mailboxes, Gmail, Mimecast, Teams, Slack, SharePoint, OneDrive, supported PST, MSG and EML files, and supported external evidence packages. Collection depends on the connector or export configuration, source permissions and chosen scope.
Can we review evidence without AI classification?
Yes. Manual review is supported. In standard discovery, the All Evidence review scope includes admitted email, document and conversation items without requiring AI classification first. Where AI assistance is used, reviewers can inspect the evidence and make their own decisions.
How does case-aware AI help an investigation?
Classification can use the case synopsis, curated entity context and configured labels. Results include summaries, rationale, confidence and supporting evidence. Whole-item classification and matching passage extraction give reviewers both an assessment and the material behind it. AI assistance does not replace professional judgement.
What is a targeted probe?
A targeted probe is an approved follow-up classification pass over an email subset defined by sender, subject keywords or dates. It has its own definitions and results. Reviewers can return to the initial results as well as completed probes, without rebuilding the collection.
How are review quality and sign-off recorded?
Governed review connects a versioned strategy and defined review set with blinded sample validation, recorded disagreements and adjudication. Review and QC sign-offs relate to the current review basis. QC needs a different authenticated reviewer; relevant changes supersede affected acceptance.
Is a reviewed-items pack the same as a Bates production?
No. The investigation workspace can assemble eligible reviewed communications and documents into a pack with an eDiscovery manifest. Formal Bates production is a separate workspace for numbering, assignments, output protocols, load files, manifests and finalisation checks. Investigation reports are another distinct output for communicating findings.
Can we import evidence prepared by another provider?
Yes, through the supported external-package workflow. Stage metadata and associated content, define a versioned field mapping, validate, then import. Supported metadata includes DAT, CSV and tab-delimited files. Package validation must pass before the material is committed as case evidence.
Where does Simply Discover run?
Simply Discover supports customer-hosted deployment in Azure, AWS or on premises. Plan source connections, permissions and the enabled workflows for your environment. Access to sensitive case actions and imported evidence is governed by the applicable feature, role and case permissions.
Does eDiscovery include legal-hold administration?
Legal-hold administration and archive custody verification require additional Archive access. These are separate from the core eDiscovery workflow. Confirm the required modules and permissions when planning your deployment.
Does the software guarantee a legally defensible outcome?
No. Review controls, evidence references, validation and production checks support the process and its explanation. The organisation and its advisers remain responsible for scope, privilege, disclosure and the conclusions drawn from the evidence.
Simply Discover eDiscovery
More time understanding
what the evidence means.
Start with the matters your team handles, the sources you need and the decisions that take the most work.