Services

The memo became an email, the file copy became an attachment, the ledger became a spreadsheet on somebody’s drive. Because nothing governed how those moved or where they came to rest, the sprawl simply changed medium.

The file estate on your servers is not an archive. It is the sediment left by processes that were digitised but never designed.

That is why the two halves of this practice are one piece of work. Clearing the estate deals with what has already accumulated. Putting structure around how information arrives, gets read and gets filed is what stops it accumulating again. Do the first without the second and you are back where you started in three years.

Knowing what you hold

Shared drives accumulate for decades. Staff leave, departments reorganise, a migration gets half finished, and the naming conventions that made sense to one team in 2011 are opaque to everyone now. The result is an estate nobody can describe and nobody feels able to touch.

The first engagement is almost always an assessment. A read-only scan of the locations you nominate, producing a picture of what is actually there:

• Volume by location, and how that has grown
• Age profile — when files were last modified, not when they were created
• Duplication, including near-duplicates and superseded versions
• Orphaned content, where the owner has left and nobody inherited it
• Permissions that have drifted from what anyone intended

Nothing is moved, changed or deleted at this stage. The output is a document you can take to the people who have to authorise what happens next.

Disposing of it defensibly

Most organisations keep everything, because disposing of anything feels riskier than paying for another terabyte. That instinct is reasonable and it is also why the problem compounds.

The work is less about deletion than about being able to justify it afterwards. That means retention rules written down and agreed, legal hold applied where it belongs, and a record of what was removed, when, under which rule, and on whose authority. Disposal runs in stages, and each stage stays reversible until it is signed off.

Where an organisation has a statutory retention schedule, that becomes the spine of the rules. Where it does not, agreeing one is usually the most durable part of the engagement.

Making the remainder findable

Clearing the redundant majority is only half the value. What remains has to be easier to work with than what was there before, or the estate reverts within a year or two.

That generally means a sensible structure, consistent metadata on the material that matters, and search that returns the current version rather than eleven candidates. Where a SharePoint or cloud migration is planned, this is the work that should happen first — migrating an unassessed estate moves the problem rather than solving it.

Structuring what arrives

The second half of the work starts where information enters a process. For most organisations that is not the post room. It is an inbox: attachments, forms submitted as documents, spreadsheets exchanged between teams, PDFs that are really photographs of text. Scanned paper is one inbound channel among several, and rarely the largest.

Typically that material is read by a person, interpreted, and typed into a system before anything downstream can begin. The cost is not only the typing. It is the queue in front of it, the errors introduced along the way, and the copy that gets saved to a drive as a precaution and never removed. That last one is how the estate you have just cleared starts to rebuild.

The work involves:

• Capture and classification of what arrives, by type and by process
• Extraction of the fields that matter, including from image-only documents
• Validation rules, so what reaches your systems is checked rather than merely transcribed
• Routing, naming and retention applied at the point of arrival rather than retrofitted years later
• Exception handling, because a process that works for 95% of documents and silently mangles the rest is worse than no automation

The measure is end-to-end time and error rate, not how much text was extracted.

How engagements are shaped

Most relationships start with an assessment, because it is the only honest basis for scoping anything larger. If the answer turns out to be that you have a smaller problem than you feared, that is a good outcome and a short engagement.

How an engagement runs sets out the sequence in more detail.