Sample Statement of Work
A real SOW we'd send you.
The fastest way to understand how an LPO engagement actually works is to read one. Below is a redacted sample SOW, the same template we'd send you after a discovery call. Download it, share it with procurement, push back on anything that doesn't fit your shop.
What's in the sample
- Scope. Concrete description of the work, e.g. "first-pass responsiveness review of ~12,000 documents in Relativity"
- Deliverables. What you receive and when, coded review output, daily QC reports, end-of-engagement summary memo
- Team composition. Profile mix (e.g. 1 senior reviewer + 4 mid-level + 1 PM), with named substitutes if anyone is unavailable
- Schedule. Start date, milestones, target end date, capacity per week
- Pricing. Either FTE-month rates or a fixed-price hour pack, with overage handling
- Security & data handling. Where data lives, who has access, retention, destruction
- Quality control. Sampling rate, QC team, override protocol, error budget
- Reporting. Cadence, format, named recipients
- Termination. Notice period (typically 30 days for FTE-month, immediate for hour packs)
- Standard riders. NDA, DPA, IP assignment, conflicts policy, BCP/DR
What it won't have
We don't pad SOWs with boilerplate that exists only to scare procurement. If a clause isn't operative, it's not in the document. Most of our SOWs are 6–8 pages.