Most companies still rely on Word files and shared folders to manage critical documentation. For a while, it works. Someone creates a template, saves it to a shared drive, and the team starts copying it for each new project.

Then things start to drift.

How it happens

It doesn’t happen overnight. A project manager copies last year’s specification and updates a few sections. Another colleague does the same, but from a different version. Someone renames a file to add “v2-FINAL” to the end. Within a few months, the shared folder is a graveyard of near-identical documents with no reliable way to tell which one is current.

This is the reality for most teams managing complex documentation. Engineering firms, construction companies, maritime operators, infrastructure projects. The industries where a wrong specification can mean expensive rework or, worse, safety incidents.

Having spent eighteen years working on superyacht projects across integrators, shipyards, and owner’s teams, I saw the same document management problem everywhere. Not because any one organisation was doing it badly, but because the tools available simply weren’t built for this. Hundreds of technical specifications, spread across shared drives, with no reliable way to tell which version was current. The technology improved over the years. The underlying problem didn’t.

Where the costs show up

The damage from document chaos rarely announces itself. It accumulates quietly, in ways that are hard to trace back to the root cause.

Outdated specifications get reused in new projects. A team pulls a template from a previous job, not realising that key requirements were updated six months ago. The project moves forward on old information. By the time someone catches it, the rework costs real money and real time. On a construction project, this might mean tearing out electrical work that was installed to a superseded standard. On a shipyard, it could mean a system that passes internal review but fails the classification society survey. Either way, someone is paying for the mistake. Research from ASCE puts construction rework at 4–10% of total project cost, and studies compiled by Buildern attribute around 22% of that rework to inaccurate or inaccessible information.

Revision numbers become unreliable. When documents live as individual files, version tracking depends entirely on discipline. Someone forgets to increment the version number. Someone else saves over the latest copy. Now there are two “current” versions, and nobody knows which to trust. I’ve seen project teams waste entire days trying to reconcile two versions of the same specification because nobody could determine which one was actually approved.

Scope creep slips in through copy-paste edits. Small changes accumulate when specifications are assembled by copying text between documents. A paragraph gets tweaked here, a requirement gets softened there. Over time, the document no longer reflects what was originally agreed. On projects where specifications form part of a contractual deliverable, this gets expensive fast. A subtle change to a performance requirement can shift liability without anyone noticing until it’s too late.

Contracts reference documents that are no longer accurate. If a contract points to a specification that has since been updated, or one that was never properly versioned, disputes follow. And they drag on, because neither side can prove definitively which version was current at the time of signing. In the maritime industry, where a single vessel build can involve hundreds of referenced specifications across dozens of subcontractors, an incorrect document reference can trigger change orders worth hundreds of thousands of euros.

And through all of this, there’s no clear audit trail of what changed, when, or why. In regulated industries, traceability isn’t optional. ISO 9001 clause 7.5 requires organisations to identify changes to documents, track who made them and when, and maintain revision history with formal approval before release. Classification societies, safety authorities, and compliance auditors all expect to see that record. But when documents are managed as files on a shared drive, there’s no reliable way to answer basic questions. Who made this change? When? Was it reviewed? Was it approved?

It compounds

These problems feed each other. Unreliable versions lead to outdated reuse. Lack of audit trails makes it impossible to catch scope drift early. Copy-paste workflows make every document a potential source of inconsistency.

The longer a team operates this way, the harder it gets to fix. Each new project adds more files, more versions, more uncertainty. Teams develop workarounds: colour-coded folders, naming conventions, spreadsheets tracking which documents are “really” current. These are patches. They don’t solve anything. They just add another layer of manual process on top of an already fragile system.

The workarounds also create a false sense of security. A colour-coded folder structure might look organised, but it still depends on every team member following the convention perfectly, every time. One person saves a file in the wrong folder, and the whole system becomes unreliable. And unlike a proper version control system, there’s no way to detect the error automatically.

What it actually costs

For a mid-sized engineering or construction firm, the cost of document chaos isn’t abstract. It shows up as rework hours when teams build from outdated specifications, delayed project handovers because document packages aren’t consistent, and commercial disputes over which version of a specification was contractually binding. It shows up as compliance failures when audit trails don’t exist.

Then there’s the quieter cost: staff frustration. The hours spent searching for the right document instead of doing actual work. An often-cited IDC white paper put the figure at roughly 2.5 hours per day spent searching for information. Later studies revised that downward, but Autodesk research still found construction professionals spending 35% of their time searching for project data, averaging 5.5 hours per week just looking for plans and documents. The tools have improved since 2001, but for teams managing complex technical documentation across shared drives, the problem hasn’t gone away.

These costs stay invisible until something goes wrong. A failed audit. A contractual dispute. A rework cycle that blows a project timeline. By then, the damage is done, and the root cause is buried in a shared folder somewhere.

The honest question

If your team manages complex documents across projects, ask yourself: how confident are you that every document in circulation is current, consistent, and traceable?

Most teams in document-heavy industries can’t answer that with a straight face. The only real question is whether you’ve decided to do something about it, or whether you’re still hoping the colour-coded folders will hold.