Documenting a condition that changes day to day

There is a particular kind of unfairness in fluctuating conditions.

You wait months for the appointment. It lands on a reasonable day: not a good day, but one of the days you can get dressed, drive, and hold a conversation. You do what people do in front of a clinician, which is present as competently as you can manage. The assessment records what it sees.

The next day you cannot get out of bed. It is four days before you can, and none of it appears in your file.

That pattern shows up in endometriosis, migraine, complex regional pain syndrome, inflammatory arthritis, fibromyalgia and most of the conditions I read files about. The record ends up built from the days you were well enough to attend appointments, which is a systematically unrepresentative sample of your life.

The provision most people do not know exists

There is a widespread assumption that a condition which comes and goes cannot be permanent, and therefore cannot meet the access criteria. People with cyclical or episodic conditions often talk themselves out of applying on exactly that basis.

The Act deals with this expressly. Section 24(2) provides that impairments which are episodic or fluctuating may be taken to be permanent, and that a person may be taken to be likely to require support for their lifetime despite that episodic or fluctuating nature.

In other words, the intermittent character of your condition is not the obstacle. Parliament anticipated it and wrote it in.

What defeats these applications is almost never the fluctuation itself. It is that the file describes the fluctuation impressionistically ("symptoms wax and wane", "good days and bad days") while the decision requires something specific enough to be reasoned from.

Why a single appointment cannot answer the question

A snapshot assessment has a structural limit, and it is worth being clear about it because it is nobody's fault.

An assessment establishes what happened on one day. If the question is whether you can walk two hundred metres, an assessment can answer it for that day. If the question is whether you can walk two hundred metres reliably, on consecutive days, without losing the following afternoon to recovery, one appointment cannot answer it at all. Not because the assessor was careless, but because the question is about a pattern and the method captures a point.

This is why a file can contain several competent assessments and still leave the central question open. Each one is accurate. Collectively they describe a person on their better days, because those are the days people attend appointments.

What has to be documented instead

Four things, and they are all specific.

Frequency. How often, in a defined period, using numbers. Not "frequently". Three to four days a week, or eight to ten days a month, or the first four days of every cycle. A decision-maker can reason from a number and cannot reason from an adverb.

Duration. How long an episode lasts once it begins, and how long the aftermath runs. These are different, and the aftermath is usually longer and almost never recorded.

Predictability. This needs recording in two directions, because they are different facts and they fail in different ways.

The first is whether you can know in advance how a given day will go. Capacity that fails predictably can be planned around; capacity that fails without warning cannot, and that unpredictability is itself a functional limitation. If you cannot commit to anything ahead of time because you do not know which version of yourself will arrive, that belongs in the record as a finding, not as an apology.

The second is whether the cost of a particular activity can be foreseen. Where something reliably takes two days back, every time, that is not unpredictability; it is a known price. The activity is rationed rather than unavailable, and you manage it by deciding in advance what to give up for it. Where the cost varies without pattern, you cannot even do that, because nothing can be budgeted for. How large the cost is comes next; this is whether you can see it coming.

Recovery. What the days after cost. This is where most files go silent. If attending a family event means two days in bed afterwards, the event is not evidence that you can attend family events. It is evidence of what attending one costs.

Reliability and cost, as separate questions

When I assess a task I score reliability and after-effect separately from difficulty, because they are separate facts and they fail in different ways.

Reliability asks whether something can be done consistently, safely, and repeatedly over time. A person who can prepare a meal once, on a good day, does not have meal preparation capacity in any sense that matters to how they actually live. Capacity that cannot be repeated is not capacity, and a file that records only the successful attempt has recorded the exception.

After-effect asks what performing the task costs. Some tasks are completed at no meaningful price. Others are completed by borrowing from the rest of the day, or the rest of the week, and the borrowing never appears in the notes. The person managed the shower. What is missing is that the shower was the only thing they managed.

Together these two questions describe something a single rating cannot: not what you can do, but what you can do and keep doing.

The good-day record, and why it happens

It is worth naming why files skew this way, because the reasons are human and none of them are your fault.

Appointments are attended on functional days by definition. People present well in front of clinicians, partly from courtesy, partly from a lifetime of learning that visible distress is read badly, partly because being believed feels safer when you seem credible rather than desperate. Clinical notes record the consultation, not the fortnight around it. And most people underreport, because describing your worst days to someone who has only seen your better ones feels like exaggeration.

The consequence is a record that reads as more capable than the life it describes. Correcting it does not require anyone to have done anything differently. It requires documenting the pattern deliberately, rather than hoping it emerges from a series of appointments that were never designed to capture it.

What this changes

If your condition fluctuates, the work is not to prove that your bad days are bad. It is to establish the shape of the cycle: how often, how long, how predictably, and what each episode costs on the other side.

That is a documentation problem rather than a treatment problem, which is usually good news. It means the evidence is available. It has simply never been gathered in a form the decision can use.

---

Where this leaves your file

If your condition is well documented but the variability is described impressionistically, the gap is in functional evidence. What is missing can be assessed and documented, and this is among the more fixable findings I make.

If your file contains assessments that all happened to fall on better days, that is the same finding arriving from a different direction, and it is worth knowing before another assessment is added to the pile.

If the detail is already there and the decision still says insufficient information, the problem is more likely to be translation than evidence.

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.