Document scanning and archive digitisation
Document scanning should connect paper capture with the way people need to retrieve information. A useful archive begins with the way people need to retrieve information. This guide connects scanning, search and organisation questions so a project can be scoped around real records and agreed deliverables.
On this page
Document scanning: turn paper into a usable archive
Archive digitisation is more than converting a stack of pages into image files. The intended result should make records easier to find, read and organise. Archivogo focuses on paper scanning and searchable documents in Athens, Greece. A useful brief starts with the documents you have and the retrieval problem you want to solve.
Read about Archivogo’s approach to searchable archives for the service’s scope and the practical distinction between capturing a document and making its contents useful to the people who need them.
A document scanning pilot can include representative clean pages, difficult pages and records with a different layout. Explain why each example belongs in the sample. The pilot should answer questions about the real archive rather than demonstrate only the easiest material. Original condition, missing attachments and existing identifiers can affect what the output needs to preserve. A brief can describe these categories without transferring confidential examples in the first enquiry or assuming the entire collection is ready for processing.
- Identify the document categories.
- Estimate the broad volume.
- Describe how people need to find records.
Select a representative starting batch
A first batch should reflect the different materials in the archive. Loose sheets, bound papers, mixed page sizes and faint print can require different handling decisions. Describe those variations before agreeing a process. A representative sample makes it easier to discuss output quality without assuming every document behaves like the cleanest page.
- Note document condition.
- Identify mixed sizes or binding.
- Describe sensitive categories without sending them.
For example, a search by a known reference and a search by a phrase inside a letter can require different preparation. These are illustrative retrieval tasks, not descriptions of an existing client archive.
Separate image quality from text recognition
A readable page image and accurate recognised text are related but different outcomes. Orientation, contrast and completeness affect the scan; OCR introduces another layer that can contain mistakes. Important names, dates and numerical fields may need additional checks. The project scope should state what is reviewed rather than promising perfect recognition of every character.
During document scanning review, consider the image and the record relationship together. A page may be readable on its own while being separated from the file or attachment that gives it meaning. Agree how those connections are represented in the deliverables. For example, an explicitly synthetic record could contain a main page and a supporting appendix. The naming and grouping should help a recipient recognise that relationship instead of treating both pages as unrelated items found through separate searches.
- Check page completeness.
- Review orientation and legibility.
- Identify text fields that need validation.
Agree practical output formats
Searchable PDF can combine a page image with recognised text, while retained image files may support other uses. The right deliverables depend on the archive and the intended workflow. Agree formats, file names and any metadata before processing a large batch. A technically valid file is not automatically a well-organised archive.
- Choose the required deliverables.
- Agree naming conventions.
- Define any metadata to include.
Before a larger batch, compare a clean printed page with one that contains faint text or a mixed layout. Agree how those differences will be represented in the output and exception record. The comparison can clarify review needs without implying that every original will produce identical recognition quality.
Review exceptions openly
Archives can contain missing pages, duplicates, damaged originals or text that cannot be recognised reliably. A useful quality process makes those exceptions visible. Agree how issues are recorded and which ones need a decision before handover. This helps prevent a neatly named folder from concealing unresolved problems in the underlying records.
A document scanning handover should explain what the recipient has received. Identify the output format, the organisation conventions and the unresolved exceptions. If recognised text is included, clarify which checks were performed rather than implying every character was independently confirmed. The handover discussion should also address original papers and retained copies through the agreed scope. These practical decisions help the archive remain understandable after delivery, without inventing a universal retention policy or a claim of perfect recognition. The pilot discussion can identify which document relationship is most important to preserve. A record with an attachment may require a different grouping convention from independent single-page items. Describe that distinction before agreeing the larger batch’s organisation.
- Record incomplete material.
- Flag uncertain recognised text.
- Agree how exceptions are resolved.
Design for the next retrieval task
Organisation should reflect how people will use the documents after scanning. A date, project identifier or document category may be more helpful than an elaborate folder tree. Start with a few realistic search scenarios and use them to test the proposed structure. Retrieval needs and document organisation therefore belong in the same conversation.
Document scanning quality should be discussed in relation to the record’s intended use. A readable capture and a useful retrieval result need separate checks.
- Test a realistic search.
- Use stable identifiers.
- Keep the structure understandable to its users.
Prepare an Athens project brief
An initial enquiry can describe approximate volume, document types and the desired searchable output. It does not need confidential records or an entire archive attached to an email. Handling, transfer, access and retention should be discussed through an agreed project scope. The first step is to understand the work, not to move private material prematurely.
- Include a volume estimate.
- Describe the intended use.
- Ask how a suitable pilot should be scoped.
Frequently asked questions
Does OCR make every character accurate?
No. Text recognition can produce mistakes, especially with difficult originals. The scope should identify the fields and records that need review and how exceptions will be handled.
Should I email the entire archive first?
No. Begin with the document categories, approximate volume and desired retrieval use. Any transfer of records should follow an agreed scope and handling arrangement.
How are output and retention decided?
Formats, recipients, treatment of original papers and retention expectations are project decisions. They need to be agreed for the actual archive rather than assumed from a general service page.
Further reading
The U.S. National Archives provides digitisation resources covering records and quality considerations. Read them as technical background in their federal-record context, rather than as proof of compliance for an Athens project.