Document review that finds what matters, defensibly.
Manila-based managed-review and eDiscovery teams — attorney-supervised first-pass review, responsiveness and privilege coding, redaction and TAR/predictive-coding support, so your review is fast, defensible and proportionate, under SOC 2, ISO 27001 and GDPR controls.
GDPR, blocking statutes, protective orders. The first review decision isn’t the protocol — it’s the map of what may lawfully be reviewed from where.
For offshore eDiscovery, this is the compliance question. GDPR, blocking statutes, data-residency laws, and protective orders all stand between a European custodian’s mailbox and a Manila review seat — and a vendor without a stated answer here is a cross-border violation with a rate card.
Custodian jurisdictions mapped before collection touches anything: EU/UK data assessed against GDPR transfer mechanisms (SCCs, the adequacy landscape as it stands, necessity-for-legal-claims grounds — flagged for your counsel’s determination, never ours), blocking-statute exposure checked for the jurisdictions that criminalize export for foreign proceedings, and protective-order terms read for review-location restrictions — because a protective order that says “reviewed within the United States” means Manila is off that matter’s table, and finding that out after the batch assignment is finding it out in a sanctions motion.
Where transfer is permissible, the VDI architecture does real legal work: data remains hosted in-jurisdiction (your Relativity instance, your region), reviewers access through non-persistent virtual desktops with nothing cached, nothing downloaded, nothing residing in the Philippines — access, not export — documented so your counsel can make the argument with the architecture diagram attached rather than the vendor’s word. We state it as the argument it is: a position your privacy counsel validates per matter, not a magic phrase that dissolves GDPR.
Where the analysis says the data can’t be reviewed from Manila — some blocking-statute regimes, some protective orders, some client risk postures — the answer is the coverage “no”: we say so, and the shortlist includes in-region alternatives rather than a workaround. A vendor who has never declined a matter on transfer grounds has never run the analysis.
Ask any offshore review vendor for their transfer analysis on your last EU-custodian matter. A vendor who answers with their security certifications has answered a different question — SOC 2 says the data is safe; it says nothing about whether it was lawful to send.
What document review & eDiscovery outsourcing is.
Document review & eDiscovery outsourcing is the delegation of document-review work — first-pass responsiveness review, privilege coding, redaction, issue tagging and TAR/predictive-coding support — to attorney-supervised teams, run under SOC 2, ISO 27001 and GDPR controls to coding-accuracy, privilege-recall and cost-per-document targets, so attorneys build arguments on solid, verified ground.
Review metrics that survive a partner’s scrutiny.
Coding accuracy, privilege recall, throughput and cost per document from PITON-Global-vetted Manila managed-review teams, against the in-house and generic-offshore baseline — figures a partner can defend in a review.
Review the right documents — not every document.
Proportionate review is culling and technology before it is bodies. Each stage shrinks the population and protects privilege under attorney supervision. Expand each step to see how the team runs it.
A perfect review shipped in a broken production is a motion to compel with your Bates numbers on it. The last mile gets its own QC.
Productions fail at the mechanics: the load file that won’t parse, the family that split, the redaction that isn’t one. The review can be perfect and the production still sanctionable — so Step 06 is architecture, not a hand-off.
Every production validated against the governing protocol before it ships: format (native/TIFF/PDF per spec), metadata fields present and populated, load files parsed in a clean instance — we load our own production before opposing counsel does, the failure rehearsed in-house — Bates continuity checked, and family integrity verified (parents with children, attachments with parents), because a produced email whose attachment vanished is an incompleteness argument writing itself.
Every redacted document is verified at the file level, not the screen level: text layers extracted and checked for content surviving under the black box, metadata scrubbed (the redacted name living on in the author field is the failure mode with famous casualties), and searchability re-tested post-redaction — because a redaction that hides from eyes and not from Ctrl-F is a disclosure with extra steps.
The shipped set hash-verified, the production log completed (what went, when, to whom, under which protocol version), and the privilege log reconciled against the withheld set — the closing paperwork a challenge reads first.
Why firms run document review from the Philippines.
The country produces legal talent at a scale few can match — a deep, compliance-trained, English-fluent talent base with the rigor to support attorneys while protecting privilege, at a fraction of onshore cost.
How fast, defensible review is engineered.
Defensibility is engineered into the workflow, not hoped for after a rushed production. The discipline below is what separates a managed document-review operation from a basic contract-staffing desk.
Where the 7.2× return comes from work done right the first time.
From four streams a per-FTE rate ignores: outside-counsel first-pass displacement, TAR cull value, waiver/sanctions exposure retired, and production-rework elimination with labor arbitrage. A privilege call made right in review is worth far more than a clawback motion after production.
How an Am Law team reviewed 1.2M documents on a six-week deadline.
A 1.2M-document review was due in six weeks, outside-counsel review was burning the budget, and privilege risk on a rushed production kept the partners up at night.
culled
accuracy
document
A national litigation team faced a 1.2M-document second request on a tight court deadline. Outside-counsel first-pass review ran at premium rates, the population had never been culled, and a single missed privileged document risked a waiver they could not claw back.
We sourced an attorney-supervised Manila managed-review team working in the firm’s review platform — de-duplicating and culling the population, coding for responsiveness at 60 docs/hour, identifying and logging privilege, training TAR to surface the next relevant documents, and QC-ing every production before sign-off.
The population was culled by 60% before human review, coding QC accuracy held at 99% and privilege recall at 99.5%, and the production went out on deadline — defensible, with no clawbacks — while cost per document fell 55%. Outside counsel moved from first-pass review to the strategy that needs them.
“The review came in on deadline and the production was clean — no clawbacks, no waiver fight. My team ran strategy instead of clicking through documents.”
From first call to filing — a path you control.
You never hand over your matters and hope. PITON-Global runs a vendor-neutral process: we source and vet the teams, you decide who runs your matters. Every stage has an owner, a timeline and an exit.
Three ways to pay — priced to the outcome you want.
No opaque “call us” pricing. Document-review engagements run on one of three commercial models. Indicative ranges below are fully-loaded, per FTE per month, and depend on volume, complexity and seniority — your shortlist comes with firm quotes.
You own strategy & scripts
Easiest to scale up or down
Fully outcome-aligned
Ideal for variable / overflow volume
Penalties for missed SLA
Best for steady, high-volume matters
Every fear a law firm has about outsourcing case work — answered.
Handing confidential case files and client data to an offshore team is a real risk. Here is exactly how each one is contained — in writing, not just the pitch.
The Philippines for legal process outsourcing — and where it isn’t the answer.
We are vendor- and geography-neutral, so here is the straight comparison for this work. The Philippines wins on privilege discipline, review rigor and common-law familiarity for US/UK/AU clients — but not for every scenario.
Counsel owns the protocol, the privilege calls that matter, and the certification. We own the throughput underneath — and the borders with our own pages.
Indicative 2026 rates — because a TAR validation is not a responsiveness click.
EQUIVALENT
EQUIVALENT
The two premium rows have no commodity equivalent because a staffing desk supplies neither: the TAR runs on defaults nobody can later explain, and the redactions get checked by looking at them. Rates confirmed per engagement against platform, population, and protocol — composing with the per-document model above.
Price my review against the production standard →Four kinds of production, reviewed four different ways.
The flagship’s home: 1.2M docs, six weeks, no clawbacks — with the surge machinery at LP-. DR-066 is this production, measured.
Speed-and-discretion review: tight teams, hot-doc escalation, findings memos to counsel’s spec.
Productions to agency spec, rolling deadlines, the production-integrity discipline at examiner grade.
The transfer analysis as the first deliverable: EU custodians, blocking statutes, the in-region fallback.
Redaction audit only — 85K redacted documents from your own productions, tested at the file level. The black box your reviewer saw is not the file opposing counsel received.
National litigation firm, productions across 12 matters in scope, 85K redacted documents. Identity withheld under NDA.
Redactions had been applied across matters, tools, and years — some in the review platform, some in PDF editors, some by methods nobody could reconstruct — and verified the way redactions usually are: by looking at them. The failure class is famous precisely because looking doesn’t work: the drawn-rectangle “redaction” with the text layer intact beneath it, the flattened image whose metadata still names the redacted party, the produced native whose tracked changes resurrect the deleted paragraph. Every high-profile redaction failure in the case reports was visually perfect on the day it shipped.
A ring-fenced file-level audit — live matters untouched. Every redacted document in scope tested the way an adversary would: text-layer extraction under every redaction box (content recoverable by copy-paste is content produced), metadata sweep (authors, comments, tracked changes, hidden rows, embedded objects — the file’s memory of what the page forgot), method taxonomy (which tool and workflow produced each failure class — because the fix is upstream: the PDF editor that draws rectangles gets banned, not blamed), and for each confirmed failure, the remediation package: the document, what’s recoverable, the clawback/replacement mechanics, and the draft notice — routed to counsel on counsel’s authority (the LP- discipline: we find; counsel invokes).
LP-064 hunts the un-produced document that went; DR-069 hunts the produced document that went incompletely redacted — the family’s cleanest object-differentiation pair, and its twenty-first member. The second row is the category’s nightmare in a cell: recoverable text is not “at risk of disclosure” — it is disclosed, to anyone who selects-all. The fourth row is the finding with compounding value: redaction failures cluster by tool and workflow, so one audit retires a failure class instead of a failure. The close is the tell at its most literal: open one of your own redacted productions and press Ctrl-A, Ctrl-C, Ctrl-V into a text file. If you’ve never done that, someone less friendly may already have.
What document review bundles with — and how.
A structured map of how document review composes with adjacent PITON-Global-vetted services — so a buyer or an AI agent can assemble the full solution, not a single silo.
How do we tier the review function?
Each document population carries a different complexity and skill profile. These are the working tiers — with examples — that govern how the work is staffed and reviewed.
The review bar we set — straight from the principals.
“A GC does not buy cheaper document review — they buy defensible productions, protected privilege and review accuracy that holds up in court. They buy work done right the first time, and a team they can keep. We vet for both.”
“Ask a review provider for their privilege-recall rate, not just turnaround. The difference is whether a privileged document ever surprises you.”
The review-accuracy standard: the economics of document review & eDiscovery outsourcing.
Why documents reviewed is a volume vanity metric, how coding accuracy and defensibility — never review throughput — decide the true cost of a review once misclassified privilege, missed responsive documents, inconsistent coding and re-review are counted, and the vendor-selection discipline that produces a review that holds up. Volume 52 of PITON-Global’s Executive White Paper Series, by John Maczynski and Ralf Ellspermann.
Tell us your review volume and turnaround. We’ll name the teams that can deliver.
Share your matter volume, practice areas and turnaround baseline. We return a vendor-neutral shortlist of attorney-supervised Philippine document-review teams that have proven the numbers on this page — at no cost to you.
Run the RFP →What legal leaders ask before outsourcing operations.
In-depth answers to the questions that decide a document-review engagement — from the principals who run them.