Legal Services Offshore blog
Discovery production volume reconciliation with offshore legal support
Reconcile approved production counts, folders, and transfer receipts while discovery counsel controls scope, privilege, and release.
Define the discovery production volume reconciliation lane
This workflow is for litigation teams preparing counsel-approved productions. Its purpose is narrow: prepare a source-linked reconciliation showing expected and observed volumes without opening substantive review. Before assigning it, the firm should name the permitted matter population, approved inputs, output template, reviewer, access window, and exact completion state. The support worker does not replace professional judgment merely because a source field looks routine. The firm remains responsible for deciding legal meaning, client advice, strategy, scope, and any external action. A written lane makes useful administrative work repeatable while giving reviewers a clear place to intervene.
Start with a source-controlled request
The intake packet should contain the approved production manifest, export folders, control totals, transfer receipt, and counsel instruction. Give every request a matter identifier, requestor, received time, current instruction version, due instruction, and named reviewer. Preserve original files or messages and work from links rather than detached copies where practical. If a required source is absent, label it absent instead of filling the gap from memory or a public search. This protects the distinction between what the firm supplied, what the worker observed, and what an authorized owner later decided.
Capture fields without inventing meaning
The working record should include production identifier, folder, expected count, observed count, byte total, transfer receipt, variance, reviewer, and disposition. Copy displayed values faithfully and retain the source location beside each field. Normalized formats may help sorting, but they should never erase the original value. Use explicit states such as not supplied, unreadable, conflicting, awaiting review, and resolved by owner. Avoid labels that imply a legal conclusion. The record should help discovery counsel or the firm-appointed production manager reach the source quickly, reproduce the worker’s observation, and understand what remains open without rereading the entire file set.
Separate preparation from authority
The support role may receive approved material, enter fields, compare mechanical totals, organize links, and flag exceptions. It should not decide rights, duties, legal sufficiency, privilege, credibility, strategy, or what a client should do. It also should not send external communications unless the firm has approved the exact channel, recipient, and wording. Put discovery counsel or the firm-appointed production manager on the decision side of the workflow and record that person’s disposition separately. This separation makes the handoff auditable and prevents tidy administrative status from being mistaken for legal approval.
Use a stop rule that works in practice
Pause when counts differ, a folder is unexpected, a file cannot be opened, privilege status is unclear, or release is requested. The escalation should include the matter identifier, current source links, the exact observed difference, the step being held, and one focused question. Give the worker a primary reviewer, backup reviewer, response target, and safe holding state. Correct escalation is completed work, not a productivity failure. Managers should never reward speed in a way that encourages staff to conceal ambiguity, broaden access, choose between conflicting sources, or move an item beyond the firm’s approval gate.
Walk through a realistic exception
Consider this example: The approved manifest lists 2,416 files, but the staged folders contain 2,415. The worker records both totals and pauses transfer rather than guessing which file is absent. The valuable output is a neutral comparison, not a guess about what probably happened. Preserve each source and state the mismatch in concrete terms. The reviewer can then correct the input, narrow the work, request another record, or close the exception. Use de-identified examples like this in training, including imperfect cases. Record the owner’s resolution as a new event rather than silently rewriting the worker’s initial observation, because a later reviewer should be able to reconstruct both.
Limit access from the task backward
Grant only the matters, folders, applications, fields, and actions needed for discovery production volume reconciliation. Use named accounts, multifactor authentication where supported, approved devices, and firm-approved transfer channels. Never share a lawyer’s credentials. Test what the account can view as well as what it can change. NIST Cybersecurity Framework 2.0 supplies a current organizing framework for governance and protection, but the firm must translate it into controls appropriate to its systems, clients, contracts, jurisdictions, and incident procedures.
Design review around evidence
A reviewer should be able to compare the output to the source without hunting through email. Use states such as received, prepared, source checked, exception open, reviewer assigned, correction requested, approved, and closed. Keep the worker’s observation distinct from the reviewer’s disposition. Sample records at the item level and categorize returns, for example wrong source, missing field, transcription error, stale instruction, permission problem, or late escalation. Those categories expose whether training, templates, access, or reviewer capacity needs repair.
Pilot before expanding the lane
Start with three approved productions from one review platform. Hold the task type, source set, reviewer, template, and definition of done steady long enough to observe failures. Include ordinary records and known exceptions. Review early outputs closely, then decide whether to retain, revise, narrow, or stop the lane. A successful pilot for one workflow does not justify broader system access or a different category of work. Expansion should follow documented evidence and the firm’s professional, security, client, procurement, and jurisdiction-specific requirements.
Measure useful performance
Track matched volumes, count variances, unexpected folders, transfer evidence, reviewer turnaround, and post-release corrections. Always publish the denominator, period, eligible population, and definitions beside rates or percentages. Separate worker-controlled defects from missing source material, late owner responses, system outages, and changed instructions. Throughput alone cannot show whether the work is safe or useful. Pair timeliness with source accuracy, access discipline, correct stopping, and reviewer acceptance. When an error repeats, inspect the template, examples, permissions, queue design, and supervision before treating it solely as an individual performance issue.
Keep supervision and closeout explicit
ABA Formal Opinion 08-451 discusses outsourcing legal and nonlegal support, including competence, supervision, confidentiality, and client communication. ABA Model Rule 5.3 addresses lawyer responsibilities concerning nonlawyer assistance. These sources are starting points, not jurisdiction-specific legal advice. Close an item only when required evidence is present, every exception has an attributable disposition, and the next owner is clear. Remove temporary access when the assignment ends and review the lane after a system change, scope change, incident, repeated defect, or new client restriction.
Turn the workflow into a scoped role
If this work recurs, bring one source packet, one acceptable completed example, the monthly volume, systems involved, access restrictions, common exceptions, and the proposed reviewer to a planning conversation. LegalServicesOffshore.com can use that concrete material to discuss a narrowly scoped e-discovery support role. The planning objective is not to promise outcomes or transfer professional responsibility. It is to define repeatable preparation, measurable handoffs, sensible access, and a firm-side decision gate that lets attorneys retain authority over every legal judgment.
See how this workflow fits the E-discovery support service.
Sources
- American Bar Association, Formal Opinion 08-451
Consulted for supervision, competence, confidentiality, and client communication considerations when legal and nonlegal support is outsourced.
- American Bar Association, Model Rule 5.3
Consulted for lawyer responsibilities concerning nonlawyer assistance.
- NIST Cybersecurity Framework 2.0
Consulted for a current framework covering governance, access protection, detection, response, and recovery.