What was on file the day the benefit was granted?

A pension fund does not have a filing problem. It has a proof problem.

The member's file exists, it is scanned, it is on the server. The question that costs money is a different one, and it always arrives later: on the day this benefit was granted, what did the fund actually hold — and was it still valid?

The four questions a folder cannot answer

Is it complete? A folder holds what you put in it. It does not know the certificate is missing. The person who opened it knows, and that person changes role.

Is it current? A proof of life from fourteen months ago is a perfectly legible file saying something that is no longer true. An expired medical report takes up the same disk space as a valid one.

Who decided, and in what order? An award that passed the analyst, the manager and the board is an act with three distinct responsibilities. Three signatures collected simultaneously is an act with one.

Against what was it decided? An approval given on Tuesday was given against the file as it stood on Tuesday. If the file changed on Wednesday and the approval still shows as valid, the record now asserts that somebody approved something they never saw.

What DOK Genius changes

Each kind of claim is a template, and the template declares what the file must contain. Retirement award, survivor's pension, portability, withdrawal, enrolment — each with its own list. When a claim is opened, the expected documents are already there, listed, marked as missing. An empty folder is an empty folder; an empty dossier is the complete list of what is not there yet.

Documents that have a validity period have one in the system. Proof of life, medical report, certificate, power of attorney. One screen lists everything expired or about to expire, in three separate windows — what has already lapsed, what lapses this month, what lapses this quarter — because those are three different problems and adding them into one number tells nobody what to do.

Signatures are collected in order. One at a time, in the sequence the fund defined, and at any moment there is exactly one person the case is waiting for. "Who is this with?" becomes a question with an answer.

Nothing incomplete moves forward. A missing required document blocks submission, and the refusal names the document. "This case is incomplete" is a message people learn to ignore; "the dependency certificate is missing, and the proof of life lapsed on 14 May" is a message somebody acts on.

On data protection, and what most tools get wrong

A benefits plan handles sensitive personal data by definition — health data in a disability claim, filiation and dependency in a survivor's pension.

Two things DOK Genius does that are worth checking in any system you are evaluating:

A field can be marked sensitive, and then it stays out of the AI entirely. Not filtered from the answer — out of the context. Filtering the answer is too late: the model has already read the document and will paraphrase it.

Access is computed, not granted. Who may open a case derives from the organisational unit it belongs to and the structure the asker sits in, not from a list somebody remembered to update. A list is only correct on the day it is written.

What this gives an inspector

Not a report. A case file that opens and shows, by itself:

• which documents were required at that moment — the requirement is recorded on the case, not pointed at a template that has since changed;
• who decided what, when, in what order, and with what written reason;
• which documents were valid on the date of the decision;
• and what was returned for correction, by whom, and why.

Who this is for

Closed pension funds with more than one plan, with awards that pass through more than one level of authority, and with a proof-of-life calendar that currently lives in a spreadsheet.

If the answer to "what did we hold that day" is currently go and look, that is the problem we solve.