Legal Services Offshore blog
Meet-and-confer issue logs prepared with offshore litigation support
Organize counsel-selected discovery issues and source references without proposing concessions, legal positions, or response language.
Define the decision before assigning meet-and-confer issue-log preparation
Meet-and-confer issue logs prepared with offshore litigation support starts with a narrow operational decision: can discovery teams preparing for attorney-led conferences see what arrived, what is missing, and who has authority to act next? Control S22-B08 covers preparation of a reviewable record. It does not authorize legal advice, a conclusion about rights or obligations, a filing, payment, external promise, or a broader search through client files. Write the lane, source systems, working hours, and named reviewer before granting access. The firm should separately confirm the professional rules, client terms, court requirements, privacy duties, and employment arrangements that apply to its work.
Freeze the source packet and instruction version
Begin with counsel-approved requests and responses, correspondence, issue categories, source documents, participant list, and written preparation instructions. Record where each instruction came from, when it was approved, and which version governs the task. If an expected source is absent, create an exception instead of finding a plausible substitute in an unrelated matter. If two records compete, preserve both and ask the owner which one controls. This discipline is especially important in legal operations because a familiar name or document may belong to a different client, version, court, or transaction. A reliable support worker makes uncertainty visible and does not improve the record by silently inventing continuity.
Design a record another person can audit
The working record should capture issue identifier, request reference, response version, correspondence source, status supplied by counsel, open fact, document link, owner, and last instruction. Separate copied source facts from staff observations and reviewer decisions. Keep the earlier value when an authorized correction arrives, then add the corrected value, decision owner, time, and reason. Use stable links or document identifiers when copying confidential text is unnecessary. A clean audit trail lets a second reviewer reconstruct the handoff without opening every file or relying on memory. It also makes coaching specific: the manager can distinguish a missing input, a transcription error, an unclear instruction, and an unauthorized judgment.
Make the stop rule usable under time pressure
Pause when a legal position must be summarized, privilege or relevance is disputed, a concession is proposed, scope changes, a deadline must be calculated, or external communication is requested. The escalation packet should contain the matter or request identifier, exact source links, the observed difference, the action currently paused, and one focused question for discovery counsel. Do not turn an observation into a recommendation. Give the worker a primary reviewer, a backup, a response target, and a safe holding state when neither is available. Treat correct escalation as successful work. If managers reward only speed and volume, staff learn to hide the very uncertainty that a supervised offshore workflow should surface.
Work through a realistic exception
Consider this example: Counsel’s note says an issue is narrowed, but the latest email does not identify the narrowed date range. The support worker links both records and leaves the range as an open question. The useful output is not a guess about what probably happened. It is a compact comparison that preserves the source, identifies the mismatch, and names the decision owner. Build training examples from de-identified records and include at least one imperfect case. Perfect examples teach clicks; imperfect examples teach boundaries. After review, add the owner’s disposition to the example without presenting it as a universal rule. A future matter may involve a different instruction, jurisdiction, client term, or source record.
Set access from the task backward
List the systems required for meet-and-confer issue-log preparation, then grant only the matters, folders, fields, and actions needed for that lane. Use named accounts, multifactor authentication where supported, approved devices, and firm-approved transfer methods. Never share a lawyer’s credentials. Test what the account can view as well as what it can change. NIST Cybersecurity Framework 2.0 offers a current structure for governance, identification, protection, detection, response, and recovery. The firm still must translate that structure into controls suited to its systems, clients, contracts, and legal obligations.
Build the handoff around distinct states
Use states that describe evidence, not conclusions: requested, received, source checked, question open, reviewer assigned, correction requested, approved, and closed. Avoid one vague “complete” field that can hide whether the firm has reviewed the work. The output should let discovery counsel compare the prepared record with its sources quickly. When the owner decides an exception, record that decision separately from the worker’s original observation. If a later event changes the answer, add a new event instead of overwriting history. This keeps operational status distinct from legal effect.
Run a bounded pilot before expanding
Start with one conference covering no more than 25 counsel-selected issues. Include ordinary items and at least one known exception. Keep the task type, input sources, reviewers, and definition of done steady long enough to learn whether the process works. Review early items closely, but do not use the pilot to bypass professional, security, client, or procurement requirements. At the end, choose deliberately: retain the lane, revise the guide, narrow access, add reviewer capacity, or stop. Evidence from one workflow should not be used to justify broader access or a different category of work.
Measure the queue with the denominator visible
Track issues linked to controlling sources, version conflicts found, open facts surfaced, owner review time, duplicate issues, and corrections before the conference. Report the eligible population, reviewed sample, period, and definitions beside any percentage. Separate worker-controlled defects from missing source material, system outages, late reviewer answers, and changed instructions. Throughput alone does not show whether the work is safe or useful. Pair speed with source accuracy, access discipline, and boundary adherence. When one error repeats, inspect the template, training example, permissions, queue design, and reviewer behavior before deciding that the problem belongs only to an individual worker.
Keep lawyer supervision concrete
ABA Formal Opinion 08-451 discusses outsourcing legal and nonlegal support, including competence, supervision, confidentiality, and client communication considerations. ABA Model Rule 5.3 addresses lawyer responsibilities regarding nonlawyer assistance. These are starting references, not jurisdiction-specific clearance or legal advice. The responsible lawyers should determine what their jurisdiction, clients, courts, contracts, and insurers require, then convert those decisions into instructions the support team can follow. Schedule source-based sample review, explain corrections, and keep final authority with the firm-appointed owner.
Close the item and improve the routine
Close an item only when the required record is present, discovery counsel has handled every exception, the disposition is attributable, and the next owner is clear. Retain records according to firm policy and remove temporary access when the assignment ends. Review the workflow after a system change, new client restriction, security incident, repeated defect, or scope change. If this lane matches your firm’s workload, bring one source packet, one acceptable finished example, and the proposed reviewer to a planning conversation. That is enough detail to discuss a narrowly scoped litigation support role without promising unsupported outcomes.
See how this workflow fits the Litigation 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 the responsibilities of lawyers who direct or supervise nonlawyer assistance.
- NIST Cybersecurity Framework 2.0
Consulted as a current organizing reference for governance, access protection, detection, response, and recovery controls.