Fragmented documentation

Your quality lives in several different spreadsheets. No one knows which one is true.

Fragmented documentation isn't just messy, it turns every follow-up into detective work.

5 min read · published September 2, 2026

Ask where the participant list lives, and the answer often gets complicated. One version sits on a shared drive, updated by an administrator. Another version lives with each employment consultant, in their own notes. A third lives in the system that was meant to replace all the others, but that only half the team actually logs into.

This is a recurring pattern in many employment services organizations. No one deliberately decided to spread the information out. It grew, case by case, template by template, until no one has full oversight of where the truth actually lives anymore.

A common scenario is an organization where each employment consultant keeps their own notes in their own format, an administrator compiles numbers for the quarterly report in a separate spreadsheet, and leadership presents a third version in its own summaries to the board. When the numbers don’t match between the three, a lot of time goes into finding where the discrepancy arose, instead of working on what actually matters.

The cost is rarely one big crisis. It’s instead a constant leak of time. Someone needs to answer how many participants are currently active, and it takes half an hour to piece together the answer from several sources. A report needs to be compiled, and three people need to send their parts before anyone can assemble the whole. Individually, these are small moments. Over a year, it adds up to significant time that never reaches the participants.

There’s also a vulnerability in it. If the one person who understands a particular spreadsheet falls ill or leaves, the knowledge of how to interpret the information disappears with them. No one else really knows which columns mean what, or why certain rows are highlighted yellow.

The deeper cost is about trust in the data. When the numbers differ between sources, each recipient picks the version that suits them best in the moment, consciously or not. Leadership trusts its own compilation. Staff trust their own notes. No one is sure which one is actually correct, which makes it hard to make decisions with confidence.

The obvious reaction is to look for a new, better tool. But the question that actually matters is rarely which tool is used. It’s about who owns the truth, and whether everyone else actually trusts that person enough to stop building their own parallel versions.

The solution is rarely to buy yet another system. Many organizations have already tried that, and found the new system just became one more source alongside all the old ones, because no one made everyday work actually run through it. What’s more often missing is a shared, defined source of information, a place everyone knows to both write to and look in, and a routine for keeping it current. This isn’t about gathering everything uncontrolled in one place, but about handling personal data and documentation according to the organization’s information security, access control, and applicable rules, while it’s clear where the shared truth lives.

Getting there requires someone being given ownership of the structure, not just the technology. Who’s responsible for a piece of information existing in only one place. Who ensures everyone actually uses that place, not their own version on the side. Without that kind of ownership, the habit reverts after a few months to everyone solving their own need in the moment.

It’s also a matter of money, even if an invisible one. The time spent every week looking, comparing, and reconciling between different sources is time that could otherwise have gone to participants or to employer contacts. Across a whole team and a whole year, it’s rarely a matter of a few hours. It’s a significant share of a full-time position that, in practice, goes toward compensating for a scattered structure, rather than contributing to the organization’s actual mission.

It’s also worth noting that fragmentation rarely arises from carelessness. It arises because each individual solution, at the moment it was created, solved a real need. A new spreadsheet because a report needed to be produced quickly. A personal template because the shared one felt clunky. Individually reasonable decisions, which together over the years have built a structure no one plans as a whole anymore.

Sorting it out rarely requires a big technical solution from the start. The first step is often simpler than you’d think, just mapping which sources are actually used today, by whom, and for what. Many organizations are surprised at how many separate sources turn up in such a mapping, and that surprise alone is usually enough to create the will to actually do something about it.

Digital quality assurance starts with shared definitions, clear information ownership, and a structure that’s used day to day.

Want to see how scattered your own situation is? Do a simple mapping of your most important data, for example the participant list or follow-up data:

The number of different sources and unclear owners says more about your vulnerability than you might think.

← Back to all articles

Curious how big your own gap is? Take the quality test, takes two minutes →