A pension fund has two kinds of missing document, and most organisations treat them as one.
The first never arrived. A survivor's pension claim with no dependency certificate. That one is visible: somebody opens the file, sees the gap, makes the call. It is work, but it is work you can see.
The second arrived, was filed, and stopped being true. The proof of life from fourteen months ago. The medical report on a disability that was due for review. The power of attorney that expired. That one is not visible at all — it is there, it is scanned, it opens without error. It just no longer proves anything.
It is the second that costs money, and the reason is that nobody is looking at it.
What a folder can and cannot tell you
A network folder answers one question: does this file exist? It answers it well and it answers it fast.
It answers none of these:
- Is this document still in force?
- How many members have a proof of life lapsing in the next thirty days?
- On the day this benefit was granted, what did we hold, and was it valid?
And the third is the one that turns up in an inspection.
The spreadsheet is the wrong answer for a specific reason
Almost every fund ends up with a validity-tracking spreadsheet. That is not carelessness — it is the only tool that answers the question.
The problem is not that the spreadsheet is fragile. It is that the spreadsheet is a second copy of the truth. The document is in the file; the expiry date is in the sheet. From the moment both exist, there are two possible answers to the same question and nothing guarantees they agree. The document is replaced and the sheet is not updated. The sheet is updated and the new file is never uploaded.
There is a quieter consequence too: the sheet knows what is lapsing, but not what was valid in the past. In an audit, the question is almost always about a date that has already gone.
What changes when validity belongs to the document
The alternative is not a better reminder. It is putting the validity where the document is.
When a claim template declares "proof of life — has an expiry date", three things become true without anybody maintaining them:
The document has a status of its own. Not "exists / does not exist", but missing, partial, uploaded, validated, needs correction, expired. A file store has only the first two, and the other four are the ones that describe the actual operation.
What is lapsing is a query, not a sheet. Everything expired or about to expire, across the whole book, in one list — one row per document, because the document is what expires, not the member.
The date stays with the case. A year later, "was it valid when we granted this?" has an answer inside the case itself, with nothing to reconstruct.
Three windows, not one number
One detail that looks cosmetic and is not.
"Documents expiring: 47" is a number that tells nobody what to do. It merges three different problems:
| Already expired | A problem you already have. Replace now. It carries a compliance consequence. |
| Expiring within 30 days | This month's work. |
| Expiring in 31 to 90 days | A planning number for the quarter. |
Adding them turns an emergency and a diary entry into the same figure. Separating them is the difference between a dashboard that informs and one people learn to ignore.
The piece nobody builds until an auditor asks
There is a fourth thing, and it is the hardest to add afterwards.
Granting a benefit is a decision taken against a state. The analyst approved what was in the file that day. If the file keeps changing afterwards — and it always does, with replaced documents, extensions, corrections — the record of that approval only stays true if something kept what they saw.
There are two defensible resolutions: invalidate the approval on any change, or invalidate only on a material change — which obliges you to define "material", and that is real work worth doing.
The third resolution is to leave the approval standing and hope nobody edits anything. That is not a policy; it is the absence of one. And it is what most document archives have by default, without ever having chosen it.
What to ask whoever is selling you a system
Three questions, all answerable in a ten-minute demonstration:
- Show me an expired document. Not a file list with a date column — the document itself, in the case, marked expired, with the case knowing it is incomplete because of it.
- Block a submission and read me the message. If it says "case incomplete", the control is decorative. It has to name the document.
- Tell me what this case required a year ago. If the answer comes from the current template, the system does not keep the past — it keeps the present and calls it history.
If you run a pension fund and recognised the spreadsheet, the problem is not the spreadsheet. It is that validity was never a property of the document — and until it is, somebody will always have to remember.