Authoring that keeps pace with engineering
Industrial manufacturer · regulated technical content
- Problem
- A structured-authoring team maintained multiple document families across product variants and markets. Time-tracking in the diagnostic showed the largest single block of authoring hours went to cross-checking released engineering data — specifications, references, variant applicability — not to writing.
- What we did
- Six-week baseline of hours per document type across the delivery line. Then a two-week throwaway prototype: a drafting agent over an LLM API with retrieval on released engineering data, proposing updates with source citations. Two-week limited deployment with a handful of senior authors, every output behind a validation gate owned by the lead author.
- How it's measured
- Instrumented as hours per document type vs. the pre-agent baseline, plus a citation-accuracy audit on every gated output. Drafting cleared the gate and scaled to the full team; a second candidate — auto-translation of safety-critical passages — was killed at the two-week mark for unacceptable review burden.