Closed document pilot
One report type and a narrow schema. Measured field-level extraction (including scans) and set human-review thresholds.

Home Cases Decades of technical reports turned into data an…
Last updated: 2026-11-17
We turned the historical report archive — including scans and handwriting — into a structured database and scoped predictive models on top.
Geoscience company in energy (UK). Confidential — name not published.
Technical well data lived across PDFs spanning decades: modern typography, low-quality scans and a non-trivial share of handwritten notes. The geoscience team hand-copied critical fields into internal databases to analyse trends. It was slow, expensive and impossible to scale at the pace the business needed.
Without a clean database with document→field lineage, any predictive model was fragile: you trained on incomplete tables or inconsistent campaigns. The risk was not only typing cost — it was deciding on partial evidence.
The client needed two things in order: first, reliable extraction into an agreed schema; then scoped models only where historical coverage allowed. Reversing that order («model now») would have amplified error.
We built a LangGraph agent pipeline aimed at closed document types, with human review on critical fields and PostgreSQL load with traceability. Predictive models arrived only after validating coverage and history.
We worked under sector confidentiality: we do not publish the name or identifiable screenshots. The technical pattern (archive→base→model) is reusable and is what we document here.
Every critical field had an owner on the client side. We agreed confidence thresholds by field type and what to do when a document contradicts a prior version.
Authorised qualitative outcome: the team stopped retyping the archive to feed analysis; the structured database became the starting point for models and reporting. Analysts spend time interpreting, not transcribing.
We do not invent global savings percentages or accuracy claims without a public client measurement protocol. Internally, field-level precision was measured per document type before widening scope — that discipline was part of the outcome.
The compound effect shows when the next report no longer starts from zero: schema, validators and lineage are ready, and the marginal cost of a new batch stays down.
One report type and a narrow schema. Measured field-level extraction (including scans) and set human-review thresholds.
LangGraph agents, queues, lineage and DB load. Trained the exception validators. Expanded to neighbouring types only with stable metrics.
With clean history, trained/validated predictive models on business-prioritised use cases. Governance: the model does not run where coverage is missing.
Field-level accuracy rules. A narrow, well-measured schema beats «extract everything» without a data owner. Handwriting has a ceiling — quality was measured before promising full coverage.
It fits energy, infrastructure and engineering with dense historical technical archives. It fits less if documents already birth structured in one system, or if nobody can validate critical fields in the pilot.
Describe document types and volume. We'll propose an extraction pilot with metrics.