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

Sharing and exports

Check the document copy or archive you are handing over

An export is prepared, but you need to establish which document version it contains, whether the actual files are included, and what the recipient can verify.

For firm teamsReviewed Available. Prepared-document receipts and archive manifests describe different export paths.

Before you begin

  • The prepared document copy or downloaded archive and its receipt or manifest.
  • The intended recipient, purpose and authorized scope of the handoff.

What to do

  1. Identify whether you are handling a prepared copy of one document or a firm export archive. For a document copy, read the prepared-export receipt and confirm the filename, output kind and saved version. Check the intended audience and use when the receipt records them.
  2. Inspect the actual prepared copy before releasing it. Compare the content, pagination and relevant attachments with the document you approved. If the source was edited afterward, determine whether a new copy is needed instead of assuming the prepared bytes changed with the editor.
  3. For an archive, read its manifest and omissions alongside the preview. Confirm whether document bytes were included. An entry in a CSV or manifest can identify a document without containing the file itself; open representative files and investigate any missing material the handoff requires.
  4. Use the supplied verification material to check the recorded files. A match answers a question about those bytes. Read the proof state as stated and keep any omitted, unavailable or disclosed removed material in the recipient's explanation rather than calling the archive complete.
  5. Release or transfer the reviewed copy only through the authorized workflow. Record which version or package was handed over. If the download failed or a receipt is missing, establish the outcome before repeating the action, and preserve the failure details for support.

What you should see

The handoff names the exact copy or archive, its intended scope and any omissions. The recipient knows what can be checked and whether the document files are actually present.

Limits and unresolved problems

A matching digest proves a byte match, not truth, legal sufficiency or completeness. Preparing an export and approving its release do not establish that a recipient received it.

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