Why one department cannot see what another department holds

The organisation is not the thing holding your record

From the outside, a large organisation looks like a single entity with a single memory. Inside, it is closer to a federation of departments, each running software chosen for its own work and holding the parts of your record that its own processes need. There is rarely one master file containing everything. There are several files, each complete for one purpose and entirely silent about the others.

That is why “I can see you on the system, but I can’t see that” is nearly always a literal statement. The person is looking at an application built for their function, which was never given a window onto anything else. Whether the other record even exists is not something they can determine from where they are sitting.

Systems arrive one at a time and get joined afterwards

Almost nobody designed their technology in one sitting. A payments system was bought in one decade and a records system in another, a case management tool arrived after a reorganisation, and each was justified by the department that needed it. Joining them up is separate work, and it is expensive, slow and deeply unglamorous, so it tends to get funded only where the case for it is obvious to somebody holding a budget.

The result is a map with strong links along the paths that money and cases actually travel, and no links whatsoever across paths nobody has yet had a reason to use. A department that has never needed to exchange data with another one will not have a connection to it, however obvious that connection looks from the customer side of the desk.

Access is granted by purpose rather than by employer

The second reason is deliberate rather than historical. Access to personal records is normally granted on the basis of what a role needs in order to do its job, with everything else closed by default. Working for the same organisation does not, on its own, entitle anybody to read a record held by a different part of it.

That principle is unpopular in precisely one situation — the one you are standing in, where the information you need is somewhere in the building and the person in front of you cannot reach it. It is considerably more popular in all the other situations, including every one in which somebody with no business reading your file would like to. A rule that could be suspended whenever suspending it was convenient would not be doing anything.

What crosses a boundary is a message, not a view

Where two departments are connected, the connection is usually a message rather than a shared screen. One system sends a defined set of fields to another at a defined moment: an address change, a status update, a payment confirmation. The receiving system stores what it was sent, and nothing beyond that.

This explains the odd, partial visibility people keep running into. A department may know that a case exists and what state it is in, because state is one of the fields it receives, while knowing nothing at all about the correspondence, the evidence or the reason for the delay, because none of that was ever included. The window is not narrow through carelessness. Somebody specified its width years ago, based on what the receiving process needed then.

The seams become visible at the worst possible moment

Boundaries are invisible while every copy agrees and extremely visible the moment two of them diverge. One department shows an old address because its copy is refreshed by an overnight message that failed on Tuesday; another shows the new one. Both are reading their own system correctly, and neither can see the other’s in order to work out which of them is behind.

The same seam produces the experience of being told something is complete and then being asked for it again by somebody else a fortnight later. Completion was recorded where the work happened. Whether that fact travelled depends on whether a link exists, whether it ran that night, and whether the receiving system had somewhere to put the information when it arrived.

Standing on a seam, and how to get off it

It helps to establish which department owns the item you care about, because ownership decides who can change it while everybody else can only report on it. Asking who holds the master version of a piece of information is an unusual question, which is exactly why it is so often answered properly.

It also helps to treat each department as a separate correspondent rather than as a branch of one organisation. Quote the reference that they use, not the first one you were given. Ask directly whether an update needs making in more than one place, since the honest answer is sometimes yes. And where two records disagree, say so plainly and early — a mismatch reported by the person it describes is frequently the only way anybody discovers that a link between two systems quietly stopped running.