Pain scores establish nothing. Here is what does.

Almost every pain file I read contains a number. Eight out of ten. Seven at best, ten at worst. Sometimes it appears hundreds of times across years of notes, tracked faithfully, recorded by people who were paying close attention.

It establishes nothing.

That is not a comment on whether the number is accurate or whether anyone doubts it. It is a statement about what the decision being made actually asks, and the number is not an answer to it. Understanding why is the difference between a file that documents suffering and a file that establishes a case.

Pain is not one of the six

Access and funding decisions turn on functional capacity, and functional capacity is assessed against six named activities: communication, social interaction, learning, mobility, self-care, and self-management.

Pain is not among them.

This is not an oversight and it is not hostility toward people in pain. The six activities are the framework the decision is made in, and they are all about what a person does. Pain is not something you do. It is something that happens to you, and the decision has no place to put it.

So pain has to be evidenced through its consequences, or it cannot be evidenced at all. Severity is not a route to the answer, however much of it you record. The number tells a decision-maker that you are in pain, which was never in dispute, and nothing about which of the six activities is affected or by how much.

What a pain diary proves

I am not against pain diaries. They are useful clinically, they help people see patterns, and they can be genuinely revealing about triggers and cycles.

What they do not do is carry an access or funding argument. A twelve-month diary of daily scores proves the pain is present and persistent. Every practitioner who has seen you already accepts that. The diary answers a question nobody was asking, at length, and it can sit in a file for years looking like strong evidence while contributing nothing to the test being applied.

The same is true of most of what people arrive with. Imaging that confirms a finding. Letters that confirm a diagnosis. Records of a long treatment history. All real, all relevant to your care, and none of it addressed to the question of what your day now costs you.

Consequence, not sensation

A usable functional statement does four things. It names the activity, states the limitation specifically, says how often and how reliably, and shows what happens as a result.

Here is what that looks like in practice. Compare:

with:

The first is a summary of distress. The second is evidence. It names the activity: self-care. It states the limitation with enough specificity that it can be pictured and, if necessary, tested. It gives frequency. And it shows the consequence, including the informal support that is currently absorbing the shortfall.

Note what the second version does not contain. No pain score. No adjectives about severity. The severity is implied by the consequence, which is the direction the reasoning has to run.

Where measures help, and where they do not

Standardised functional measures matter, and I use them. Their value is that they turn a description into something comparable: a result that can be set against a population, repeated later, and read the same way by someone who has never met you.

Without something like that, a report is asking a decision-maker to take a practitioner's word for it. Clinicians are trustworthy, but "in my opinion her function is substantially reduced" is an assertion, and an assertion is the weakest thing a file can contain.

The opposite failure is just as common. A file that holds a stack of instrument scores and no narrative is also thin, because a score describes a level without describing a life. What a decision-maker needs is both: the measure that establishes the level, and the description that shows what that level means on an ordinary Tuesday.

Five questions, not one

Function does not reduce to one rating. When I assess a task, I record five separate things: how difficult it is under the best conditions, how much help from another person it takes, what equipment or workaround it requires, whether it can be done reliably and repeatedly, and what performing it costs afterwards.

Those last two are almost always missing. A report can establish that showering is difficult and still say nothing about whether it can be done two days running, or what the rest of the day looks like once it has been done. For a fluctuating condition that is the whole question, and a file that cannot answer it will read as though capacity is intact on the good days it happened to record.

Self-management: the domain nobody documents

Of the six activities, self-management is the one most consistently absent from pain files, and it is very often the strongest argument available.

Self-management is the capacity to organise, plan and run your own life safely and independently. Managing appointments. Managing medication. Household organisation. Budgeting and financial decisions. Recognising risk and responding to it.

Persistent pain interferes with all of it, through mechanisms that are well recognised clinically and almost never written down. Disrupted sleep degrades attention and working memory. Sustained pain consumes cognitive capacity that would otherwise be available for planning. Medication affects concentration. Fatigue reduces the ability to hold a sequence of steps in mind.

The practical result is the person who cannot reliably track which medication was taken when, who misses appointments they very much wanted to attend, who cannot follow a set of instructions through to the end without prompting, and who has handed the household administration to a partner without either of them ever describing it as a support need.

None of that appears in a file that documents pain intensity. All of it is directly relevant to a named activity, and it is usually happening in plain sight.

If you recognise yourself in that paragraph, it is worth knowing that the thing you have been treating as disorganisation is more likely to be evidence.

The reframe

The instinct, entirely understandable, is to prove the pain. Years of being disbelieved make that instinct stronger, and the file grows accordingly: more confirmation of the condition, more documentation of severity, more voices agreeing that it is real.

The decision was never asking that. It asks what the pain has done to six specific areas of your life, and it can only work from what the record says about them.

The shift is from proving that you are in pain to establishing what the pain costs you. Same life, same condition, entirely different file.

---

Where this leaves your file

If your condition is thoroughly documented and its day-to-day consequences barely appear, the gap is in functional evidence. This is the most common finding I make, and it is fixable: what is missing can be assessed and documented.

If the functional detail is there but the decision still says insufficient information, the problem is more likely to be translation. The material may already be present in terms that do not match the test being applied.

If reading the self-management section described your household, that is worth taking seriously. It is frequently the clearest available evidence and almost never on file.

An Evidence Audit identifies which of these applies to you, in writing, with the reasoning set out. If you would rather work out whether that fits your situation by talking it through first, the introductory call is free.

Observations drawn from published Tribunal and Court reasons, current as at the compilations cited. Nothing here is legal advice, and nothing here predicts an outcome. Every file turns on its own facts.