Skip to content
Litigation.Held together.
Request a demo
All help guides

Discovery and production

Review documents and record their classification

Documents have arrived, but the review queue still shows uncoded material, an unknown side or role, or a model proposal awaiting the firm's decision.

For firm teamsReviewed Available. Classification controls depend on the user's role and the deployed review view.

Before you begin

  • Access to the matter and a defined review assignment.
  • The responsible attorney's instructions for responsiveness, privilege and classification.

What to do

  1. Open Discovery and Review documents. Confirm the review assignment and the material in scope. Received means that a file arrived. It does not mean someone read it, determined responsiveness, or cleared it for production or client access.
  2. Open the document and inspect its content, source and family context before coding it. If the file cannot be read or text recognition is incomplete, record that review issue. Do not treat a blank text pane as an empty document or mark the item reviewed solely to clear the queue.
  3. Record the review decisions supported by your assignment. Distinguish responsiveness from privilege and work-product classification. A model suggestion is a proposal for review, even when it appears beside a document that has already been received or processed.
  4. Where Classify the record is available, inspect missing role and side separately. The producing party cannot be inferred from Produced to, which names the recipient. Have the required attorney decide proposed classifications using the source and a reason, rather than accepting a batch without inspecting its basis.
  5. Save the coding and check the resulting status. Use the review overview to track recorded coverage and unresolved items. If a save fails, reopen the document before moving on; the local selection is not evidence that the review decision was recorded.

What you should see

The recorded review reflects the document actually inspected, with unreadable material and undecided classifications left open. Coverage reflects saved coding rather than files merely received.

Limits and unresolved problems

Review coverage counts recorded work. It says nothing about material outside the recorded set. Responsiveness, source role, source side, privilege and client visibility are separate decisions.

Product scope and requirements

Related guides

Still need a hand?

Record the screen, time, displayed status and steps you tried. Use your signed-in support route or contact your firm administrator. Do not include credentials or confidential documents in a public message.

Support contacts