CASEFUSION ANALYZE

Understand your matter before it leaves the platform

CaseFusion® processes the collected population and analyzes it with context, so a legal team can understand the matter and reduce what goes to review. What remains moves downstream with that context attached.

See analyze in action Explore CaseFusion

Analyze content together with its context

Cloud collaboration creates a record around every document: which version, who opened it and when, and what role they held at the time. Most of it never reaches review. That is the context gap, and CaseFusion closes it by carrying the record into analysis alongside the content.

What changes when context reaches analysis

Plain-language questions | Ask the population a question and get an answer grounded in cited passages from the ESI. No citation, no answer.
Traceable answers | Each answer traces back to the population analyzed, the question asked, and the passages that produced it. It is a starting point for investigation rather than a coding decision.
Questions that reach context | Context captured as people work lets a question reach who was responsible when the events occurred, which repository an item came from, and which version the recipient opened.
Versions and who opened them | See a version of a document with the people who opened it and when.
Messages across versions | See the chat messages that referenced a different version of the same document.
People outside the email | See the people who worked on a document but never appear in the email at all.

Most analysis happens in a review platform

In the standard sequence, a legal team learns what a matter involves after the population has gone to a downstream provider, been processed, and been loaded for review.

Decisions become reversals | Processing has been paid for and hosting has started, so acting on what the analysis shows means unwinding decisions rather than making them.
Context arrives stripped away | A reviewer has to work out which repository a document came from, who held which role when it was created, which version the recipient opened, and why the item is in the matter at all.

See how CaseFusion analyzes before review

See analyze in action

What analyze does

Analyze runs against a defined matter population. Each result remains traceable to that population, the question or search used, and the ESI that produced it.

Process

Prepare collected ESI for analysis by extracting and normalizing text, metadata, and timestamps. Preserve families, threads, and version relationships during deduplication, then connect each item to available audit and access activity.

Assess the corpus

See the population before examining individual items: volume, sources, file types, languages, timelines, and apparent gaps.

Map the people

Review custodian identities and aliases, roles and reporting lines over time, and communication patterns during the relevant period.

Explore and search

Search the indexed population using keyword, semantic, and concept methods. Build and compare queries, then save the searches that become part of the matter record.

Ask questions in plain language

Ask the population a question and receive an answer grounded in cited passages from the ESI. Use the answer as a traceable starting point for investigation, not as a coding decision.

Validate and cull

Test the proposed scope through sampling and search-term reports across included and excluded populations. Reduce what moves downstream where the information supports it, and record the basis for each decision.

Better information does not always produce a smaller scope. It produces a scope supported by better information.

Act on what you find right away

Analysis may identify new people and sources, and CaseFusion makes acting on that information simple and efficient.

Reconstruct historical identity

Effective-dated identity shows that one custodian held a different role during the relevant period and identifies the manager responsible for that function at the time.

Issue hold notices

Hold notices are sent to the custodians in scope, with surveys asking what systems they used and who else was involved.

Apply preservation

Preservation is applied across each custodian’s mailbox, OneDrive, one-to-one chats, and the Teams and SharePoint sources they belong to.

Refine scope with activity

Indexed activity reveals sustained interaction with a departmental SharePoint site. The site is added to scope, while routine use of the company intranet is documented and excluded.

Reduce with proof

Reducing a population before review is only defensible when every exclusion can be explained and supported. Success is not measured by how much data was removed, but by whether the reasoning behind each decision can withstand scrutiny.

Named, repeatable rules

Culling rules are named, ordered, and repeatable.

Sampled before excluded

Populations proposed for exclusion are sampled before anything is excluded.

Every exclusion recorded

Each exclusion is recorded against the rule that produced it, the reason, the sample drawn, and the person who approved it.

Locked before promotion

Before anything is promoted, the reviewable population is locked, so what went downstream and what stayed behind are both fixed and both accounted for.

Every document that does not move forward has a reason you can inspect.

Where analyze ends

Analyze covers the work between collection and review: processing the population, understanding it, validating it, and deciding what moves on.

Review and production run downstream, in RelativityOne or another review workflow.
CaseFusion promotes the culled population with the context it was built from and the record of the decisions that produced it.

The receiving team does not repeat the work.

CaseFusion analyze FAQs

What is analyze in CaseFusion?

Analyze is the CaseFusion capability area covering the work between collection and review: processing the collected population, searching, filtering, and previewing it, asking questions of it in plain language, building chronologies, validating that the collection is the right one, and culling what moves downstream.

Does analyze include document review?

No. Review and production run downstream, in RelativityAiR or another review workflow. CaseFusion promotes the culled population with its context and the record of the decisions that produced it.

What does analyze do that a review platform does not?

It processes and analyzes the population inside CaseFusion, before anything is handed to a downstream provider or hosted for review, and it works on that population together with the information the collection was built from: effective-dated identity, the repositories and sources in the matter, the relationships among messages, attachments, files, and participants, and the record of scope decisions.

Does AI in analyze decide what is relevant?

No. AI-assisted questions run against a defined matter population and every result can be traced back to the population analyzed, the question asked, and the ESI that produced it. Relevance, responsiveness, privilege, and production scope remain legal determinations.

How is a pre-review reduction defended?

Culling rules are named, ordered, and repeatable. Populations proposed for exclusion are sampled before exclusion. Each exclusion is recorded against its rule, reason, sample, and approver, and the reviewable population is locked before anything is promoted.

Can what analyze finds change the scope of a matter?

Yes. A participant or a repository surfacing during analysis can be added to the matter, the hold extended to cover it, and its sources collected, without leaving CaseFusion or starting a separate effort.

Learn what you have while it is still yours to shape

See how CaseFusion analyzes a collected population with the identity, repository, and relationship information the collection was built from, and returns what it finds to the rest of the matter.

See Analyze in action Explore CaseFusion