What Legal Process Outsourcing Can and Can’t Move Offshore

Someone in IT mentions a batch of new Relativity logins. A partner’s calendar shows a “transition workshop” with a vendor nobody in the paralegal room has heard of. Two weeks later the first-pass review batches stop arriving in your queue, and the answer when you ask is that the firm is adding capacity. You are not being paranoid. Work is moving, and nobody will say which parts.

So here is the straight version, for whichever side of this you are on. Legal process outsourcing is the transfer of defined, supervisable legal support tasks to people outside the firm, usually offshore. It can move document review, e-discovery processing and coding, contract abstraction, due diligence support, docketing, patent support, transcription and the first draft of a research memorandum. It cannot move legal advice, strategy, a court appearance, or any judgment a licensed lawyer has to make personally. That boundary sits on top of the unauthorised practice of law, which is why the arrangements that survive look nothing like the ones sold off a rate card. What follows is general information about how the rules work, not legal advice, and no substitute for reading the rules your own jurisdiction has adopted.

What legal process outsourcing moves, and what it can’t

Work travels when the output is defined in advance, the instructions can be written down, and someone onshore can check it without redoing it.

  • Document review and e-discovery. ESI processing, de-duplication and threading, first-level responsiveness coding, issue tagging, privilege flagging (flagging, not determining), redaction mechanics, production and load-file QC.
  • Contract and diligence work. Abstraction into a CLM system, obligation and clause extraction, lease and MSA summaries, playbook-driven redlines against fixed fallbacks, data room review against an agreed issues list.
  • Research and drafting. A memorandum drafted offshore, then adopted, rejected or rewritten by a lawyer who has formed their own view of it.
  • Docketing, patent support, records. Rules-based date computation and entry; prior art searching, proofreading, IDS preparation; record retrieval, chronologies, template-driven deposition summaries.

What does not travel is shorter and harder to police: advice to the client, what to plead and when to settle, any appearance before a tribunal, the signature on a filing, the final privilege determination, the decision about what a review result means. One test sorts almost everything. Would this output reach the client or the court without an admitted lawyer forming an independent view of it first? If yes, it cannot move, whatever the brochure says about the vendor’s “US-qualified team”.

The rules that decide this, and whose rules they are

Most write-ups get the first point backwards. The ABA Model Rules of Professional Conduct bind nobody. They are a template. Your obligations come from the rules your state’s highest court has adopted, which usually track the Model Rules and sometimes do not, plus your state’s ethics opinions, which vary more. A partner who read a national summary and stopped has not done the work.

The numbers are worth knowing, because that is how the opinions are written. 1.1 competence. 5.1 and 5.3 supervision, the second covering nonlawyer assistance, which is what a vendor’s staff are. 1.6 confidentiality. 1.4 communication with the client. 1.5 fees. 1.7 and 1.10 conflicts and imputation. 5.5 unauthorised practice, including assisting someone else’s. One note on sourcing: the ABA’s own Model Rules pages would not load for me and its formal opinions sit behind member access. There is an ABA formal opinion on outsourcing, numbered 08-451, whose text I could not verify, so I will not tell you what it says. Everything quoted below comes from rules and opinions I read in full.

The District of Columbia’s adopted Rule 5.3 is representative, and its comment addresses outside providers head on. A lawyer may use nonlawyers outside the firm for document management, data storage and similar services, but must “make reasonable efforts and communicate appropriate directions to ensure that the services are provided in a manner that is compatible with the lawyer’s professional obligations”, weighing the provider’s reputation, confidentiality protections and the legal environment where the work sits. In England and Wales the source differs and the shape does not: SRA Code of Conduct for Firms, paragraph 2.3, “You remain accountable for compliance with the SRA’s regulatory arrangements where your work is carried out through others”.

Assistance is permitted. Practice is not. Supervision is the difference.

The North Carolina State Bar’s 2007 Formal Ethics Opinion 12 draws the line about as plainly as it can be drawn. Foreign assistants may handle administrative support and defined legal support work including document review, due diligence, drafting and research, but they “may not exercise independent legal judgment” and cannot “provide any legal advice or services directly to the client”. The lawyer must “review thoroughly all work-product”.

New York City Bar Formal Opinion 2006-3 got there a year earlier and remains the most complete treatment I could read in full. A lawyer may outsource legal support services overseas if the lawyer “rigorously supervises the non-lawyer, so as to avoid aiding the non-lawyer in the unauthorized practice of law”, preserves confidences, avoids conflicts, bills appropriately and obtains advance client consent where necessary. The lawyer must “shoulder complete responsibility for the non-lawyer’s work”. Unusually, it lists the diligence steps too: background on the intermediary, résumés, reference checks, an interview in advance, and communication during the assignment rather than at the end.

In practice, supervision that holds up looks like this:

  • A named onshore lawyer per workstream. Not “the litigation team”. A name, in writing, who can be asked afterwards what they did.
  • A written protocol before the first batch: coding definitions, worked examples of close calls, and what gets escalated rather than decided.
  • A QC sample with a number in it. Put the percentage in the SOW and define the error rate that triggers re-review. The sampling rate that fails is the one nobody set.
  • A direct channel to the supervising lawyer. Questions routed via an account manager arrive three days late and pre-averaged.
  • No client contact from offshore staff, and an escalation log recording every judgment call a lawyer actually decided.

Partners, the cost note: none of that is free. Supervision at this standard consumes real associate hours, far more in month one than the rate card implies. A deal that only works if the supervision is nominal is a deal that does not work.

Privilege, confidentiality, and the vendor in the middle

Does handing documents to a vendor waive privilege? The mechanism: privilege protects confidential communications made for the purpose of legal advice, and disclosure to a third party can destroy the confidentiality it depends on. The long-standing exception covers the lawyer’s own agents assisting in rendering that advice, which is why vendor review is possible at all. How far it reaches is decided jurisdiction by jurisdiction, and I could not verify the controlling authority for any state from a primary source. That is the mechanism, not the answer for your matter.

Worth doing regardless is a protective order, because the rule text is unambiguous and the order is cheap. Federal Rule of Evidence 502(d): “A federal court may order that the privilege or protection is not waived by disclosure connected with the litigation pending before the court”, and that non-waiver travels to any other federal or state proceeding. Rule 502(b) is the fallback, and it is conditional. Inadvertent disclosure escapes waiver only where the holder “took reasonable steps to prevent disclosure” and “promptly took reasonable steps to rectify the error”.

Read 502(b) again with an offshore review in mind. Your access controls are not security hygiene. They are the evidence you file when you argue your steps were reasonable, which makes this an evidentiary checklist rather than an IT one: access per matter, need-to-know, by named individual, no shared logins; review inside a hosted platform with per-user audit logging and with export, print and download disabled for the vendor role; no local storage and no removable media on the review floor; same-day offboarding evidenced by a log you can pull; contract terms making the vendor your agent, barring subcontracting, requiring notice if any authority compels the data, and requiring certified destruction at the end. A vendor that cannot produce a per-user record of who opened which document on which matter leaves you unable to answer the only question anyone will ask.

Cross-border data, briefly

Sending client data offshore raises a separate stack: GDPR and UK GDPR transfer mechanisms where EU or UK personal data is in the collection, US restrictions on bulk transfers of sensitive data, foreign blocking statutes, protective orders limiting where ESI may be hosted, and outside counsel guidelines that bind harder than any of them. That analysis is the one every offshore arrangement needs and is covered in our piece on modelling offshore access risk.

The conflicts check nobody runs

This step gets skipped because conflicts feels like an intake problem and the vendor feels like a supplier. A provider serves many firms at once, and nothing in its ordinary operation stops it, sometimes on the same floor, from coding documents for a party adverse to your client on another matter. Your firm’s imputation machinery does not reach it, because the vendor is not your firm.

The New York City Bar sets out the enquiry: ask the intermediary about its conflict-checking procedures and how it tracks work performed for other clients; ordinarily ask both the intermediary and the individual nonlawyer whether either is performing services for any party adverse to your client; and remind both in writing of the obligation to safeguard confidences.

Then put teeth on it. A matter-level conflicts check the vendor runs and evidences before staffing. A named-individual roster you approve that cannot change silently. A lock-out on named adverse parties for the life of the matter, with notice-and-remove rights. Separate workspaces per matter, permissions that make other matters invisible rather than merely discouraged, no floating pool of reviewers. One diagnostic before you sign: ask for a report showing which named individuals touched which matters last quarter. A provider that produces it in a day can answer a conflicts question. One that cannot has no idea, and after signing, neither will you.

Telling the client, and billing the hours

Disclosure is not automatic everywhere. NYC Bar 2006-3 declines to require it reflexively, then identifies when consent is needed anyway: where the nonlawyer plays a significant role, where confidences or secrets must be disclosed, where the client reasonably expects only firm personnel, or where the nonlawyer’s time is billed on any basis other than cost. North Carolina found an obligation “to disclose the use of foreign…assistants and to obtain the client’s written informed consent to the outsourcing”. Two respectable bars, two defaults. Yours is the one that counts, and for most firms the practical answer is to disclose in the engagement letter and stop worrying about the split. A contract question bites sooner anyway: outside counsel guidelines often restrict offshore handling or require approval first, and breaching a term you already signed produces a write-off and an unpleasant call with general counsel.

Billing is where a defensible arrangement turns into a real problem. The NYC Bar states the default, adopting the standard of ABA Formal Opinion 93-379: absent a specific agreement with the client to the contrary, the lawyer “should charge the client no more than the direct cost associated with outsourcing, plus a reasonable allocation of overhead expenses directly associated with providing that service”. No markup unless the client has agreed to one.

So there are two clean options. Pass the vendor cost through as a disbursement, at cost, disclosed on the invoice. Or charge it as a fee at a rate the client expressly agreed in the engagement letter. The dangerous third thing, and the reason this surfaces in fee disputes and billing audits, is taking vendor hours bought at a low unit rate and billing them on a timekeeper line as firm paralegal or associate time. That is not aggressive billing. It is a misrepresentation on an invoice, and its discovery is rarely gradual. Consent obtained after a client challenges a bill is not consent. It is a negotiation you have already lost.

If you are the paralegal whose work is moving

You deserve numbers rather than reassurance. The US Bureau of Labor Statistics puts paralegals and legal assistants at 404,900 jobs in 2025, median pay $62,890 as of May 2025, and projects “little or no change” in employment from 2025 to 2035, roughly 0%. Around 40,800 openings a year are still projected, mostly replacing people who leave the occupation. BLS attributes the limited demand to technology including AI making paralegals more efficient at research and document preparation. Note what it does not say. BLS does not name offshoring as the cause. The flat line is real; the cause is contested.

Inside that flat aggregate, exposure is uneven. Most exposed is high-volume, protocol-driven work checkable at a distance: first-pass responsiveness review, document coding, records retrieval and indexing, transcription, template-driven deposition summaries, contract abstraction, docket data entry, production mechanics. If your day is mostly batches, assume the question has been asked. Least exposed is anything anchored to something physical or jurisdictional. E-filing across local rules that change by county. Trial preparation and on-site support. Client and witness contact. Real estate closings, probate, immigration filings with in-person steps. Knowing which judge’s chambers wants what, and when.

The move that works is from doing the protocol to owning it. Write review protocols instead of following them, because whoever authors the coding definitions and escalation rules supervises the work regardless of who executes it. Learn the platform as an administrator rather than a user: workspace setup, search term testing, batching, technology-assisted review workflows, production sets and load files. Own defensibility end to end, meaning ESI protocols, privilege logs, redaction QC and what a production must look like to survive a challenge. Volunteer to run the QC sample on vendor output and report the error rate, which puts you on the supervision side of the arrangement worrying you. Get numerate about sampling, throughput and unit pricing, because vendor management is a numbers job most people in the room cannot do. Then ask to sit on the vendor call. Somebody has to translate between the lawyers and the review manager, and that person is hard to remove.

One caveat, because the usual version of this advice quietly invents a figure. E-discovery project management and litigation support technology are widely described as the growth end of the domestic market, and job postings support the impression, but BLS publishes no separate occupational series for those roles. I cannot give you a growth number, and anyone who does is making it up.

Questions that come up next

Our vendor’s staff are qualified lawyers in India. Does that change the analysis?

Not the parts that matter. Someone admitted in another country is not admitted in your state, so for your rules they are nonlawyer assistance, and both the 5.3 supervision duty and the 5.5 unauthorised practice analysis apply unchanged. Foreign qualification can genuinely lift output quality. It does not convert assistance into practice, and it does not let anyone advise your client.

We use our own captive centre offshore, not a third party. Is that different?

On conflicts, meaningfully: a captive serving only your firm removes the adverse-vendor problem and brings those people inside your ordinary conflicts systems. On consent, often: clients who object to a third party frequently do not object to your own staff. On supervision and unauthorised practice, not at all. Check the client’s guidelines first, because most define offshore by where the person sits, not who signs the payslip. The same logic covers AI review: technology-assisted review changes who does what, never who is responsible for the output.

The client’s guidelines prohibit offshore work. Is asking for a waiver worth it?

Often, and it lands better narrow. Name the single workstream, the platform and hosting location, the access model, the QC sample rate, the supervising lawyer and the billing treatment. A scoped request with controls attached reads as competence. A general request to relax the guideline reads as a cost exercise aimed at the client’s budget.

If you have to build this properly, the hard part is not finding people who can code documents. It is standing up an arrangement where the access model, the audit trail, the conflicts segregation and the QC sample all exist before the first batch goes out. AB7 Solutions builds that kind of offshore support function: BPO and KPO teams and dedicated remote professionals for high-volume document and data work, human-in-the-loop data operations where quality is measured by sampled error rate rather than asserted, and a cybersecurity practice that can specify and test the access controls, logging and segregation the confidentiality analysis above depends on. If the gap is onshore instead, our recruitment and contract staffing work covers the litigation support and e-discovery project management seat that has to sit above any vendor. We are not a law firm and do not practise law, which is rather the point: supervision and every legal judgment stay with you, and we will say so when a scope you describe should not leave your office at all. Call +1 321 341 7733, email ab@ab7solutions.com or director@ab7solutions.com, or start at www.ab7solutions.com.

Sources: New York City Bar Association, Formal Opinion 2006-3, Outsourcing Legal Support Services Overseas (Aug 2006), which quotes the cost-plus-overhead billing standard of ABA Formal Opinion 93-379; North Carolina State Bar, 2007 Formal Ethics Opinion 12; District of Columbia Bar Rules of Professional Conduct, Rule 5.3 and Rule 5.5; Federal Rules of Evidence (Dec 1, 2024), Rule 502(b) and (d); US Bureau of Labor Statistics, Occupational Outlook Handbook: Paralegals and Legal Assistants (May 2025 pay, 2025-2035 projections); Solicitors Regulation Authority, Code of Conduct for Firms, paragraph 2.3. The ABA’s own Model Rules and formal opinion pages could not be retrieved and are not relied on here.

Leave a Comment

Your email address will not be published. Required fields are marked *