Paperless office
Paperless office software and digitisation sequence
A paperless office programme fails when it starts by scanning everything. The sequence that works is to stop new paper arriving first, digitise only what is still referenced, index the physical archive rather than scan it, and give every digitised record a retention rule on arrival.
Why paperless programmes stall
Paperless programmes fail for a reason that is obvious in hindsight and almost universal in practice: they start by scanning the archive. A team is assigned, boxes are collected, a scanner runs for months, and at the end the organisation has a large quantity of image PDFs nobody searches and paper still arriving through the front door at the same rate as before. The budget is spent and nothing has changed.
The sequence that works inverts this. Stop new paper arriving first, because every day you do not is a day the archive grows. Then digitise only what is still being referenced, which is usually a small fraction of what is stored. Then index the remainder physically rather than scanning it, because a box you can locate in thirty seconds is nearly as good as a scan and costs a hundredth as much.
The second reason programmes stall is that scanning is treated as the end state rather than the beginning. A scanned document with no metadata, no retention rule and no owner is a liability with a storage cost: it is discoverable in litigation, it counts as personal data if it names anyone, and nobody is scheduled to dispose of it. Digitisation without governance moves the problem rather than solving it.
The symptoms you will recognise
- A scanning project that ran, finished, and changed nothing about how documents arrive
- Image PDFs with no text layer, filed under names like "scan_0034.pdf"
- Paper still arriving by post and being filed in the same cabinets
- Off-site storage invoices that nobody can map to what is actually in the boxes
- Digitised documents with no retention rule, accumulating indefinitely
- Staff printing documents from the system in order to work with them
Configuration
Folder structure
Born digital
- Documents created in the system
- Documents received electronically
- Generated from templates
Digitised
- Scanned and indexed with metadata
- Awaiting quality check
- Scanned originals pending destruction authorisation
Physical archive (indexed, not scanned)
- Box register with contents summary
- Location and movement history
- Retrieval requests
Programme management
- Digitisation policy and scanning standard
- Destruction authorisations and certificates
- Progress reporting
Configuration
Metadata that makes digitisation worth doing
| Field | Type | Mandatory | Why it exists |
|---|---|---|---|
| Record class | Single-select | Mandatory | Determines the retention rule. A digitised document with no class is an unbounded liability. |
| Original date | Date | Mandatory | The date of the document, not the date it was scanned. Retention triggers depend on it. |
| Physical location | Text | Optional | Where the paper original is, if retained. Mandatory for anything not authorised for destruction. |
| Scan quality checked | Yes / no | Mandatory | Destroying an original against an unchecked scan is how a programme loses a document permanently. |
| Destruction authorised by | User | Optional | Mandatory before an original is destroyed. Someone must own that decision by name. |
| Subject or reference | Text | Mandatory | The retrieval key. OCR helps, but recognition on old paper is imperfect and a reference field is not. |
Configuration
The digitisation workflow
Step 1: Capture and OCR
The document is scanned to an agreed standard and OCR runs. Resolution and colour settings are set in a scanning standard rather than per operator, because inconsistent capture is what makes recognition unreliable.
Step 2: Index
Record class, original date and reference are applied — proposed by AI extraction where possible, confirmed by the operator. A scan reaching the repository without these is rejected back to the queue.
Step 3: Quality check
A sample or full check confirms the scan is complete and legible: no missing pages, no cropped edges, reverse sides captured. This step is why the programme does not lose documents.
Step 4: Authorise destruction, or shelve and record
Where the original may be destroyed, a named person authorises it and a destruction certificate is produced. Where it must be retained — deeds, wills, statutory certificates — its physical location is recorded instead.
Configuration
Retention rule
What starts the clock
The trigger is derived from the original document date, not the scan date. Using the scan date is the most common error in a digitisation programme and it extends every period by however long the backlog took to process — quietly turning a seven-year rule into a twelve-year one.
Outcomes
What changes
- New paper stops accumulating, because intake routes are digital before the archive is touched
- Only actively referenced material is scanned, so the programme is sized by use rather than by volume
- The remaining archive is locatable by box and shelf in seconds, without being scanned
- Every digitised document carries a record class and therefore a disposal date
- Originals are destroyed against a checked scan and a named authorisation, with a certificate retained
- Retention periods are calculated from the original document date, not the date of scanning
FAQ
Paperless office: common questions
Should we scan our whole archive?
Almost certainly not. In most archives a small fraction of the material is ever referenced again, and scanning the rest costs real money to produce documents nobody opens — while creating discoverable, retainable records you then have to govern. Index the archive physically, scan on demand, and spend the budget on stopping new paper instead.
What should we do first?
Close the intake routes. Redirect post to a scanning bureau or a monitored mailbox, switch supplier invoices to email, replace paper forms with e-forms, and move signatures to electronic capture. Until new paper stops arriving, any archive work is being outpaced by the inflow.
Can we destroy originals after scanning?
For most records, yes — but the legal position varies by document type and jurisdiction, and some instruments must be retained in original form: deeds, wills, certain certificates and anything requiring a wet signature by statute. Identify those classes and take advice on them before you authorise any destruction, and configure them as a record class that is explicitly excluded from scan-and-destroy so the exception is enforced by the system rather than remembered by a person.
What retention date should a scanned document get?
One derived from the original document date. If you use the scan date, a 2018 record scanned in 2026 will be retained until 2033 under a seven-year rule instead of 2025 — and a backlog processed over two years produces a schedule that is quietly wrong for every document in it.
How do we stop people printing things out again?
Usually by fixing the reason rather than the behaviour. People print because the document is hard to read on the device they have at the point of work, or because they need it somewhere without a screen. Mobile and tablet access, and OCR that makes a document searchable rather than scrollable, remove most of the motivation; a policy alone does not.
آخر مراجعة: 2026-09-01. See all seven use cases.