Institutions do not have a document. They have a shelf
Batch work is a different shape of problem from single-document work: the survey happens once, the treatment applies across a selection, and the output has to arrive filed rather than as a folder of loose results. Every page is processed independently, so one difficult sheet fails alone.
- per-page
- isolation on every run
- survey once
- condition recorded for the intake
- filed
- output lands where it belongs
A register of certificates running page by page, each with its own status - one sheet retried, the rest filed. Per-page isolation, shown live.
One precious page, or a whole shelf of them. Batch Restoration runs the same either way — here is the damage it takes on, and the records it runs across.
and the records it runs across
Why this is harder than it looks
Tools built for one document at a time collapse at scale: a single failure takes down the batch, there is nowhere to record a condition survey once, and the output lands as an undifferentiated pile that somebody then has to file by hand.
What this handles
- Registry runs of degree certificates
- Digitisation programmes with a standing backlog
- Whole filing cabinets of government records
- Career-length runs of payslips
- Bound volumes captured page by page
- Thousands of instances of the same form
How batch restoration runs
The same three moves on every job, and the third one is the part most tools skip.
Survey once
Record the condition for the run in a conservator's vocabulary - storage, handling and capture damage - and it applies across the intake.
Treat a selection
Select rows and apply a treatment across them, opening any single sheet that needs individual attention without leaving the register.
Deliver filed
Results land in the collection they were assigned before the job started, with captured details exported as one table.
What actually happens to the page
The survey happens once, the treatment applies across a selection, and the output arrives filed. Three moves turn a shelf into a run.
The condition is recorded for the whole intake
Record the condition for the run in a conservator's vocabulary - storage, handling and capture damage - and it applies across the intake. There is one place to record a condition survey, rather than repeating it document by document.
- Conservator's vocabulary for the survey
- Storage, handling and capture damage noted once
- The survey applies across the whole intake
Apply a treatment across rows, open any one that needs it
Select rows and apply a treatment across them, opening any single sheet that needs individual attention without leaving the register. Every page is processed independently, so a difficult one can be handled - or retried - on its own.
- Treatments applied across selected rows
- Any single sheet opened without leaving the run
- Each page keeps its own progress and failure state
Results land where they were assigned, exported as a table
Results arrive in the collection they were assigned before the job started, with captured details exported as one table. Nobody files a folder of loose results by hand afterwards - the filing is part of the run, not a task that follows it.
- Output filed on arrival, not sorted afterwards
- Captured details exported as a single table
- One page failing never stops delivery of the rest
How a shelf actually runs
Scale is a different problem, not a bigger one. A few properties are what make a register survive a real backlog.
Hundreds per register
A shelf rather than a sheet - hundreds of pages per register is the design target, and the register is the interface.
Failure is isolated
When one page fails, nothing else does - each carries its own progress, result and failure, so you retry the one sheet.
Mix types within a console
A certificate register happily holds degrees, diplomas and training certificates together; different families use different consoles.
Filed, not piled
Output lands in its assigned collection and exports as one table - there is no folder of loose results to sort by hand.
Built to be trusted at the edges
Batch Restoration is one capability inside a pipeline built on a single idea: a restoration you cannot trust at the edges is a picture of one.
Everything is read back
Every restored page is read as text and compared against what was legible before, so nothing appears out of nowhere without being flagged.
The original is never lost
The untouched capture is always delivered beside the restoration - the recovery is a new version, never an overwrite.
Refusals are the product
What cannot be recovered is marked, not guessed. The guarantee is built into how the pipeline runs, not asked of a model.
It reads back as data
Fields come out checked against the document's own arithmetic, with withheld values kept in their own column - never mixed with blanks.
One sheet or a whole shelf
Per-page isolation means a single difficult document never stops the run - each page keeps its own progress, result and failure.
Free to try, no card
Free to start, no watermark, and if a document is not recoverable we would rather tell you than sell you a plan.
Where a general-purpose tool goes wrong
The same page, two philosophies. One optimises for a convincing picture; the other for a correct one - and says so when those two part ways.
What most tools do
- One failure takes down the whole batch
- Nowhere to record a survey once
- Output lands as a pile to file by hand
- Treats scale as just a bigger single job
What Docovly does
- Per-page isolation - one sheet fails alone
- Survey recorded once, applied to the intake
- Results filed on arrival, exported as a table
- The register is the interface for the run
What it will not do
Enforced by how the pipeline is built rather than by instructions given to a model - which is the only kind of guarantee worth writing down.
- 1One page failing never takes down the batch
- 2Every page keeps its own progress, result and failure
- 3Output is filed on arrival, not sorted afterwards
per-page
isolation on every run
once
the condition survey is recorded
hundreds
of pages per register, by design
filed
on arrival, exported as one table
Consoles that use this capability
Batch Restoration, answered
What people ask before sending us documents to recover, verify and deliver.
Have a document you are not sure about?
Send us a photograph of it. We will tell you honestly whether it is recoverable before you spend anything.
Ask usA shelf rather than a sheet - hundreds per register is the design target, and the register is the interface rather than an upload box.
Also in Recover & deliver
Recover it, then read it back
Whatever state it is in - faint, cramped, sealed, or a shelf of them. Free to start, no card, and the original is never overwritten.