Why symptom “master lists” keep appearing in ADHD discussions
A question posted in an ADHD discussion forum asks whether it is normal to write a “master list” of symptoms or whether doing so is overcomplicating the situation. The post is brief and represents one person’s uncertainty, not clinical evidence or a representative survey. Still, the question captures a recurring problem in conversations about attention, executive functioning, and possible neurodivergence: people are expected to explain complicated patterns from memory, often while anxious and unsure whether their experiences count.
The verified source material here is limited to that user discussion. It does not establish a diagnosis, prevalence rate, or medical conclusion. What it does show is a practical information gap. A person may notice that functioning varies sharply by task, setting, urgency, social demand, sensory load, or available support. When asked for a summary, they may have only a vague label—“I cannot focus,” “I procrastinate,” or “I am inconsistent”—rather than examples that show the conditions around the pattern.
That gap matters because broad descriptions can invite broad moral judgments. “Inconsistent” is often treated as evidence of poor effort, even though variation may be the most important detail. Someone might complete an urgent task but stall on a routine one, follow spoken instructions in a quiet setting but lose them in a busy room, or manage a demanding day and then have no capacity left for basic domestic work. Those are not interchangeable situations.
A written record can help, but it is not automatically helpful. The useful version is an observation log, not a prosecution file. It might record the situation, what happened, the practical impact, what support was available, and the after-effect. It can also include counterexamples: when the person functions well and what conditions were present. This creates a more accurate picture than a list containing only failures.
From a TALA perspective, the key question is mismatch. Is the problem the person, or is there a poor fit between the person and the demand, environment, communication method, timing, or recovery available? That question does not eliminate personal responsibility, and it does not provide a diagnosis. It does prevent a premature conclusion that every difficulty reflects a defective character.
There is a second risk: self-tracking can become another high-effort project. A massive spreadsheet may offer the appearance of control while consuming the capacity needed to live. If maintaining the system becomes harder than noticing the pattern, the system is not serving its purpose. Three concrete examples in a phone note may be more valuable than an elaborate record that lasts two days.
For someone preparing for a clinical conversation, specific examples can make the discussion clearer: how long a pattern has existed, where it appears, how it affects daily life, and what changes it. But the person collecting the information is not responsible for proving a diagnosis. A clinician’s assessment should remain an assessment, not a contest in which the client must perform perfect certainty.
The wider issue is not whether every person should keep a symptom master list. It is whether systems give people workable ways to describe context-dependent disability and support needs. If the only accepted account is a neat, stable narrative, people whose functioning changes with environment will routinely be misunderstood.
The unresolved question is how to collect useful information without turning self-observation into surveillance. The practical answer is likely smaller and more flexible than the phrase “master list” suggests: notice a recurring pattern, test one adjustment, observe the result, and revise the support. That approach treats experience as information while leaving room for uncertainty.
Sources
- Reddit discussion: “Is it normal to write down somewhat of a ‘master list’ of my symptoms, or am I overcomplicating?” — https://www.reddit.com/r/ADHD/comments/1vhhtia/is_it_normal_to_write_down_somewhat_of_a_master/
Go deeper with the TALA knowledge base:
Read the TALA article
