When a client’s evidence lands on your desk as a few thousand screenshots, a pile of PDFs and a phone export nobody has opened, the attorney needs one thing from you: a reviewed, organized set they can trust. An evidence review workflow is the repeatable process that gets you there without losing originals, skipping items or making calls that belong to the attorney.

The workflow below runs in stages, and each stage has a single job. Separating them is what makes the review fast and defensible: you never code what you haven’t preserved, never rely on text you haven’t verified, and never export what nobody has checked. It works for family, civil and housing matters, and it scales from a few hundred items to many thousands.

What are the stages of an evidence review workflow?

A sound review moves through eight stages in order. Skipping ahead, especially coding before preservation, is where most problems start.

StageGoalOutput
1. PreserveLock originals before anyone works on themUntouched originals with hash values
2. InventoryKnow exactly what arrived, from whom, whenIntake log with counts by source
3. TriageFast first pass for relevance and priorityItems sorted into review buckets
4. Verify textConfirm OCR or extracted text matches the imageCorrected, searchable text
5. CodeAttach dates, people, issues, priorityA coded evidence log
6. FlagSurface privilege, privacy and admissibility questionsAttorney question list
7. Hand offGive the attorney a usable summaryReview memo and key-item list
8. Quality checkCatch errors before anything leaves the firmQC record and clean export

How do you preserve and inventory evidence before review?

Preserve first: copy the originals into a protected location, record a hash value for each file, and do all review work on copies. Then inventory what you received before you look at any of it in detail.

A SHA-256 hash is a fingerprint of a file’s exact contents. If the hash recorded on arrival matches the hash of the file you produce months later, you can show the file hasn’t changed. The guide to hash values in litigation explains what that fingerprint does and does not prove. Tools such as Evidence Helper hash originals automatically on arrival and keep them untouched, which removes a manual step that is easy to forget under deadline pressure.

Your intake log should capture, for each batch:

  • Source and custodian (client’s phone, client’s email, third-party records, opposing production)
  • How it arrived (upload, email, physical media, production) and the date received
  • File count and formats, including HEIC photos, chat exports and scanned PDFs
  • Anything the client said about the batch (“these are from my old phone”)
  • Who received it and where the originals are stored

How do you triage a large evidence set quickly?

Triage is a fast first pass that sorts every item into a bucket without detailed coding. The point is to find what matters early and stop spending time on what doesn’t.

Use a small, fixed set of buckets the attorney approves in advance:

  • Key: likely central to a disputed issue; route to the attorney early
  • Relevant: bears on an issue; code fully in stage 5
  • Background: context that may help a chronology but needs light coding
  • Duplicate: the same content captured twice; link it to the primary copy
  • Not relevant: no apparent connection to any issue; kept, but not coded
  • Attorney question: you can’t tell, or it raises privilege or sensitivity concerns

Duplicates are common with client-collected material, because the same conversation often arrives as screenshots and as an export. Link duplicates rather than deleting them. When the volume is overwhelming, the triage workflow for clients who send thousands of screenshots walks through sampling and time-boxing.

Why verify extracted text before coding?

Search, sorting and summaries all depend on the text extracted from images and scans, and extraction makes mistakes. Verify it against the source before anyone relies on it.

OCR and AI-assisted extraction struggle with exactly the details that matter most in litigation: names, phone numbers, dollar amounts, dates and times, and text over busy backgrounds. A misread digit in a time stamp can put a message on the wrong day in a chronology.

  1. Prioritize. Verify every key and relevant item fully; spot-check background items.
  2. Compare side by side. Read the extracted text against the image, focusing on names, numbers and dates.
  3. Correct without overwriting. Record corrections separately from the original extraction so the change is visible.
  4. Mark the item verified. Note who verified it and when.

The exhibit itself should reproduce the source image or document. Extracted text is a working aid for search and summaries, not a substitute for the original.

How should evidence be coded?

Code each relevant item against fields the attorney defines at the start, usually drawn from the claims, defenses and disputed issues. Consistent fields make the log sortable into a chronology, an exhibit list or a witness outline later.

Template: evidence coding fields

Item ID: unique number assigned at intake (never reused)

Event date/time: when the underlying event happened, with time zone if known

Received: date received and source/custodian

Type: text message, email, photo, document, social media post, recording

People: author, recipients, and people mentioned

Issues: one or more from the attorney’s issue list

Priority: key / relevant / background

Foundation: who could identify or authenticate this item

Flags: privilege, personal identifiers, minor’s information, attorney question

Reviewer / date: initials and date coded

The foundation field pays off at hearing time. Federal Rule of Evidence 901 requires evidence sufficient to support a finding that an item is what its proponent claims, and knowing early who can provide that testimony lets the attorney spot gaps while there is still time to fill them. Many state evidence codes track the federal rules closely, though numbering and details vary.

What should a paralegal flag for the attorney?

Flag anything that requires legal judgment, and don’t resolve it yourself. Your job is to surface the question clearly, with the item ID and a one-line reason.

  • Possible privilege. Client communications with the firm forwarded to others, notes prepared for counsel, or messages with other attorneys. If anything is withheld in discovery, Federal Rule of Civil Procedure 26(b)(5) generally requires describing it; see the practical guide to privilege logs.
  • Personal identifiers. Social Security numbers, financial account numbers, birth dates and minors’ names. For federal filings, Rule 5.2 limits these to partial forms such as the last four digits, a birth year and a minor’s initials; state rules vary.
  • Third-party sensitive information. Medical, counseling or school information about someone other than the client.
  • Authentication gaps. Screenshots with no visible sender, date or source, or items the client can’t explain.
  • Completeness concerns. Excerpts where the surrounding conversation might change the meaning.
  • Anything harmful to the client. The attorney needs to see it early, not on the eve of a hearing.

What does a good handoff to the attorney look like?

A good handoff is a short memo the attorney can read in five minutes, backed by a log they can sort. It says what was reviewed, what matters, what is missing and what needs a decision.

Template: review memo

Scope: 2,140 items from client phone and email, received [dates]. All originals hashed.

Results: 46 key, 312 relevant, 590 background, 1,104 duplicate or not relevant, 88 attorney questions.

Key items: IDs listed by issue, with one-line descriptions.

Gaps: no messages between [date] and [date]; client says phone was replaced.

Decisions needed: privilege flags (12), completeness concerns (5), redaction approach for minors’ school records.

How do you quality-check a review before export?

Check a sample of coded items against the source, confirm the numbers reconcile, and verify that nothing flagged was exported without a decision. Then record the check.

  • Re-review a sample from each reviewer for coding consistency
  • Confirm intake counts equal triage counts; nothing fell through
  • Confirm exported files trace to hashed originals
  • Check exhibit numbering for gaps and duplicates
  • Confirm redactions were applied to copies and actually remove the underlying text
  • Confirm every attorney-question item has a recorded decision

Evidence rules and filing requirements differ by court, and whether any item is admissible or persuasive is the responsible attorney’s decision. What the workflow does ensure is that when the attorney makes that decision, they are working from complete, verified, traceable material.