Harvey's Word Add-In enables document-wide edits on 100+ page legal documents via orchestrator-subagent architecture
Harvey's initial Word Add-In was optimized only for targeted local edits, leaving longer documents requiring complex multi-page coordinated changes unsupported. Direct OOXML manipulation by LLMs produced poor outcomes and degraded reasoning quality, while one-shot edits on long documents missed large portions due to position bias.
Direct OOXML generation by LLMs produced invalid or schema-nonconformant XML and caused regression on legal reasoning tasks. One-shot edits on long documents suffered from position bias, missing content in the middle even with explicitly long-context models.
Harvey's Word Add-In now supports editing 100+ page documents with a single query, transforming hours of manual legal editing into a single seamless interaction.
Show all 6 reported metrics
Frequently asked questions
What did this team achieve with this AI workflow?
Harvey's Word Add-In now supports editing 100+ page documents with a single query, transforming hours of manual legal editing into a single seamless interaction.
What tools did this team use?
Harvey, Office JavaScript API, Office Open XML, Vault, Microsoft Word.
What results were reported?
Document size supported: 100+; Legal editing time saved: transforming hours of manual effort into a single seamless interaction; Evaluation development time: condensed years of manual work into weeks; Model combinations tested: 30+ (source-reported, not independently verified).
What failed first in this deployment?
Direct OOXML generation by LLMs produced invalid or schema-nonconformant XML and caused regression on legal reasoning tasks.
How is this legal document review AI workflow structured?
User submits edit query → OOXML translated to natural language → Orchestrator plans and decomposes → Subagents process bounded chunks → Changes applied via Word API → Automated offline evaluation.