Paper → digital eBR · OCR + LLM extraction
Turn scanned paper batch records into reviewable electronic records.
AI reads the scan and maps entries onto the record; a person checks every extracted value before it is accepted.
Scans Read by AI
Weights, lots, times and signatures mapped onto the record.
Every Value Checked
A person reviews extracted values before they are accepted.
Original Kept
The scan stays attached to the electronic record.
What goes wrong today3 common problems
Legacy Paper Doesn't Fit the Modern Audit
10 years of paper batch records sit in binders. Reconstruction for CAPA, recall or APR takes weeks.
Manual re-typing is slow and error-prone
A single BMR can carry 400+ data points. Data-entry teams introduce transcription errors that then have to be QC'd.
No Trend Data Across Paper History
Yield, deviation and cycle-time trends against paper batches are invisible until someone rekeys them into a spreadsheet.
Everything V5 does here5 capabilities
Scan-to-structured extraction
OCR + LLM reads handwritten entries, weights, times, initials and signatures — with confidence scoring per field so the human reviewer only touches low-confidence values.
Recipe-Aware Mapping
Extracted values are mapped to the master recipe's step, material and spec — variances flagged in-line, not discovered at review.
Signature and Audit Trail Preserved
Each e-signature carries the original scanned pen-and-ink glyph plus the reviewer's Part 11 attestation of transcription accuracy.
Bulk Backfill of History
Historical batches processed in bulk; queryable and trendable the moment they land.
Same eBR spine as new production
Backfilled records share the object model with new eBRs — APR, CPV and trend queries treat old and new uniformly.
How it works, step by step5 steps
From binder to signed eBR in five stages.
- Sample and calibrate. 50-batch sample confirms model performance for the site's handwriting and forms.
- Recipe Mapping. Master recipes mapped so extractions land in the right step and material.
- Threshold Configuration. Per-field confidence thresholds set with QA.
- Bulk Backfill. Historical batches processed; low-confidence fields queued to the reviewer with scan overlay.
- New-Paper Capture. Any lingering paper stations ingest daily; site plans a full digital cutover on its own timeline.
What to look for when choosing
Paper-to-digital projects fail when they treat the scan as a picture rather than a record. These criteria separate a working migration from a very expensive filing cabinet.
Handwriting Confidence per Field
Does the extractor return a confidence score per extracted value so review effort focuses on the ambiguous entries? Every field carries confidence; a configurable threshold routes low-confidence fields to a human reviewer with scan overlay.
Recipe-Aware Mapping
Are extracted values mapped to the master recipe step and material, or dumped into a flat table? Extraction targets the recipe schema; variances surface at ingestion.
Signature Fidelity
Are the original pen-and-ink signatures retained alongside the electronic attestation? Original signature glyphs retained and linked to the Part 11 attestation of accuracy.
Bulk Backfill Throughput
Can historical batches be processed in bulk without a per-batch project? Bulk ingestion pipelines process thousands of batches per job with per-batch audit trail.
Same record model as new eBR
Do backfilled records share the object model with new eBRs, or do they live in a parallel archive? Backfilled and new records share the eBR spine; APR and trend queries treat them uniformly.
Retention of Source Scan
Is the source scan retained as the record of record? Source scan is retained, immutable and linked to every extracted value.
V5 Compared with Other Approaches
Paper-to-digital vs a data-entry team and vs template-OCR tools.
| capability | spreadsheet | legacy Qms | v5 |
|---|---|---|---|
| Confidence per field | None | Rare | Per-field with configurable threshold |
| Recipe-aware mapping | Manual | If templated per product | Native to recipe schema |
| Signature evidence | Not preserved | Sometimes | Original glyph retained |
| Bulk throughput | Per-batch labor | Per-template setup | Bulk pipeline |
| Same schema as new eBR | No | Separate archive | One eBR spine |
Regulations this supportsYour quality team stays responsible for compliance
The regulations that decide whether a paper-to-digital migration counts as a record.
21 CFR Part 11
Reviewer attests transcription accuracy at ingestion with e-signature; source scan retained; every downstream edit is audit-trailed.
21 CFR 211.188
Backfilled records carry the same structure and signatures as new BMRs — the migrated record is a real record, not a scanned artefact.
EU GMP Annex 11 §7.1
Source scans and extracted records held in immutable object storage with cryptographic integrity.
PIC/S PI 041
Attribution is the reviewer's e-signature; original is the scan; accuracy is confidence-scored and human-verified.
Standards Referenced
- 21 CFR 211.188 (batch production and control records)
- 21 CFR Part 11 (electronic records / signatures)
- EU GMP Annex 11 (computerised systems)
- ICH Q7 §6 (documentation and records)
- PIC/S PI 041 (data integrity)
Common questions3 answers
- Can V5 read handwritten batch records?
- Yes — the model is tuned for pharma / food / cosmetics record formats and returns a per-field confidence score. Anything below your configured threshold routes to a human reviewer with the scan side-by-side.
- Is the extracted record Part 11 valid?
- Yes. The original scan is retained as source; the electronic record carries the reviewer's attestation of transcription accuracy and the full audit trail of any post-extraction edits.
- How many batches can be processed at once?
- Bulk ingestion handles thousands of batches per job. Throughput depends on page count and handwriting density, not batch count.