ScanSoft UK All articles
Workflow Strategy

The Second Filing Cabinet: A 90-Day Plan for Merging Two UK Document Estates

ScanSoft UK
The Second Filing Cabinet: A 90-Day Plan for Merging Two UK Document Estates

When a UK business absorbs an acquisition, the integration checklist usually covers staff, customers, contracts and IT. Paper and scanned records sit lower down the list, often because they are assumed to be someone else's problem. In practice, the second filing cabinet arrives with its own retention schedule, its own naming conventions, its own access permissions and its own scanner habits. The result is not simply more documents. It is two document estates operating under different rules, with no single owner accountable for bringing them together.

A 90-day plan will not digitise every box. It can, however, establish control. The aim is to decide what is scanned, what is retained in physical form, what is destroyed under which schedule, how duplicates are identified and how access is reconciled. Those decisions belong in the first quarter, before anyone signs a purchase order for another scanner.

Days 1 to 30: establish ownership and legal boundaries

The first month is about authority, not equipment. Appoint a document integration lead with enough seniority to make decisions across both organisations. That person should not be the same individual responsible for running the scanners day to day. The lead needs a small working group covering records management, IT, data protection and the business functions that actually use the records.

Build a combined information asset register. Start with locations rather than individual documents: offices, storage rooms, off-site archive contracts, shared drives, cloud repositories, email archives and local scanner folders. For each location, record the estimated volume, the media types, the business owner and whether the records are active, semi-active or dormant. This does not need to be perfect. It needs to be honest enough to support decisions.

Next, compare the two retention schedules. Do not assume the parent company's schedule automatically applies to records created by the acquired business. Where the acquired company operated as a separate legal entity, its records may carry different retention periods, statutory obligations or contractual commitments. Take advice on legal hold and litigation risk before any disposal takes place. If a hold is in force, destruction must stop immediately and the instruction must be recorded.

Access is the other first-month issue. The parent company's staff should not automatically be able to read the acquired company's personnel files, customer records or commercially sensitive contracts. Map roles rather than names, identify which groups need access to which record sets, and document exceptions. The data protection officer should be involved early, particularly where personal data is being combined or transferred between systems.

Days 31 to 60: decide what moves, what stays and what goes

With the register in place, the second month turns to disposition. Divide the combined estate into three practical routes: scan and retain digitally, retain physically for a defined period, or destroy under the applicable schedule. A fourth route is sometimes necessary for records that are too awkward for standard capture, such as bound ledgers, unusual paper sizes or fragile documents. Those should be flagged for a separate capture route rather than forced through a scanner that will damage them.

Duplicate detection deserves its own workstream. Exact duplicates can be found through file hashes where records are already digital. Near duplicates require a more considered approach: compare document type, date, reference number and supplier or customer name. Version duplicates are common after an acquisition, especially where both businesses kept their own copies of the same contract or invoice. Do not delete simply because two files look similar. Establish a rule set, apply it consistently and record the rationale for retaining the chosen version.

Scanning decisions should be driven by use, risk and retention. Records that are consulted regularly, needed for audit or required to support a digital workflow should be prioritised. Records that are nearing the end of their retention period may not justify the cost of capture. Records subject to a legal hold should be preserved in their current form until the hold is lifted.

This is also the point to standardise metadata. At minimum, agree a document type, a date, a reference and a retention category. Without these fields, the combined archive becomes a larger version of the original problem: searchable in theory, unreliable in practice.

Days 61 to 90: consolidate access, evidence and exit

In the final month, move from decisions to controlled execution. Reconcile access permissions in the target repository. Remove inherited open shares, replace individual permissions with group-based access where possible, and test with sample users from both organisations. A common failure is to grant broad access during migration and promise to tighten it later. Later rarely arrives.

Produce an evidence pack. It should show what was scanned, what was retained physically, what was destroyed and under which authority. Include certificates of destruction from approved suppliers, quality-check samples from scanned batches and a log of exceptions. This pack matters not because anyone enjoys paperwork, but because a merger is exactly the moment when retention decisions are most likely to be questioned.

Finally, set an exit date for the old scanner habits. Retire local scan folders, unapproved cloud accounts and personal naming conventions. Issue a short capture standard covering file naming, metadata, resolution, colour settings and storage location. Keep it practical. A one-page standard that people follow is better than a twenty-page policy that they ignore.

Procurement comes last

Only after the first 90 days should the business consider new capture hardware or software. By then, it should know the volume, the media types, the metadata requirements and the retention rules. The specification will be smaller and more accurate. The business case will rest on evidence rather than assumption.

Merging two document estates is not primarily a scanning project. It is a governance exercise with a capture component. The organisations that manage it well are the ones that decide early who owns the problem, which rules apply and what evidence will be kept. The second filing cabinet can be closed. It just needs a plan before it is opened.

All Articles

Related Articles

Counting the Cost of the In-Tray: A Capture Business Case That Holds Up

Counting the Cost of the In-Tray: A Capture Business Case That Holds Up

The Handover Clause: Planning a Cloud Capture Exit Before the Ink Dries

The Handover Clause: Planning a Cloud Capture Exit Before the Ink Dries

From Letterbox to Ledger: Designing a UK Digital Mailroom That Earns Its Keep

From Letterbox to Ledger: Designing a UK Digital Mailroom That Earns Its Keep