What to track when you have chronic pain — and what not to obsess over
AI helps you design a tracking plan matched to your pain type, your life, and your capacity — starting with the minimum that gives useful data.
What to track when you have chronic pain — and what not to obsess over
Pain tracking has a specific purpose: to make patterns visible that you can't see from inside the experience. Not to create a complete record of every sensation. Not to document your suffering. To find the signals in the noise — which factors predict your flares, which protect against them, and where the leverage points are.
The difference between useful tracking and obsessive monitoring matters enormously for chronic pain. Research on hypervigilance in Pain found that excessive attention to pain sensations amplifies them — the nervous system interprets your monitoring as evidence that the threat is real and important. Track enough to find patterns. Don't track so much that tracking becomes the problem.
The core metric: pain as a daily snapshot
Rate your pain once or twice a day. Not in the moment of a flare (that's reactive monitoring). At a set time — evening is often best, because you're summarizing the day rather than reporting a momentary spike.
A simple 0-10 scale works. So does a word: mild, moderate, severe. The goal is consistency over precision — the same scale applied the same way over weeks. Individual numbers don't matter. The trend matters. The correlations matter.
If your pain varies dramatically throughout the day, two ratings help: morning (captures overnight recovery and sleep quality) and evening (captures the day's cumulative load). More than that and you're monitoring, not tracking.
What to note alongside the number. Location if it shifts. Character if it changes (aching versus sharp versus burning — different types suggest different mechanisms). What you were doing when it was worst. What helped. Keep this brief — a sentence, not a paragraph. If you can leave a voice note at the end of the day, just ramble through what you remember. Iris can extract the structure later.
The six parallel variables
Pain doesn't happen in isolation. These are the factors that research consistently shows interact with chronic pain. You don't need to track all six from day one — start with pain plus the one or two you suspect matter most, then expand.
Sleep. Duration and quality — both matter, and they're different things. Eight hours of fragmented sleep is not the same as eight hours of solid sleep. Did you wake during the night? Did you wake feeling rested? Research in Sleep Medicine Reviews found that sleep quality predicts next-day pain intensity more strongly than pain predicts next-night sleep quality — making sleep one of the most important variables to capture.
Stress. A simple daily rating: low, moderate, high. Note the source if it's obvious (work deadline, argument, financial worry). The relationship between stress and pain operates through multiple pathways — muscle tension, cortisol elevation, sleep disruption, reduced pain inhibition. Sometimes the stress-pain connection has a time lag: stressful day today, pain flare tomorrow.
Activity and movement. What did you do physically today? Not just formal exercise — general movement level. Did you walk? Sit at a desk for 8 hours? Lift something? Avoid an activity because you were afraid it would hurt? The avoidance is as important to capture as the activity. If you notice yourself skipping things because of fear rather than current pain, note that — it's data about the fear-avoidance cycle.
Mood. Brief and honest. Anxious? Frustrated? Low? Okay? Good days? The mood-pain relationship is bidirectional and often more powerful than people expect. Research in The Lancet Psychiatry found chronic pain patients are two to three times more likely to develop depression, and depression independently amplifies pain perception.
Medications and supplements. Everything you take, every day. Prescription medications, over-the-counter painkillers, supplements, cannabis if applicable. Dose and timing. This matters for two reasons: identifying which medications actually affect your pain (some may not be helping), and tracking medication patterns that could be creating problems — particularly analgesic overuse, where frequent pain medication can paradoxically increase pain sensitivity over time.
Food and caffeine. Less critical for most pain types than for headaches or fatigue, but worth noting if you suspect a connection. Some inflammatory pain responds to dietary factors. Caffeine timing affects sleep quality, which affects pain. Alcohol affects sleep architecture. If these seem irrelevant to your pain, skip them initially and add later if the primary analysis doesn't explain enough.
When a tracking sprint makes sense
You don't need to track your pain forever. Most of the time, you and Iris are just talking — about what's going on, what your physio said, what you're afraid of, what you're trying. Tracking enters the picture when there's a real question worth answering: is the new medication actually doing anything? Is sleep the lever, or is it stress? Is the flare pattern weekly or random?
That's when Iris may suggest a tracking sprint — a focused stretch of consistent logging for a week or two, aimed at the question on the table. A sprint runs through conversation: at the time you've agreed on (evening works well for most people, because you're reviewing the day rather than reporting a moment), Iris asks the few things the investigation needs — pain summary, sleep last night, stress, what you did physically, what you took. You answer in a sentence or two. If you want to add nuance, a voice note captures it without requiring you to type through pain.
Consistency beats completeness. Five days of simple data is more useful than two days of exhaustive documentation followed by three days of nothing. If a day is too bad to track, skip it and note "bad day, couldn't track" the next day. That gap is itself data. When the sprint ends, the daily logging ends with it.
What not to track
Don't track pain in real time. Rating your pain every hour keeps your attention locked on it. The nervous system interprets this as "pain is the most important thing happening right now" and amplifies the signal. Track the summary, not the moment.
Don't track every sensation. Twinges, aches, minor shifts — these are noise, not signal. If you find yourself cataloging every physical sensation, you've crossed from tracking into hypervigilance. The goal is the daily pattern, not the minute-by-minute experience.
Don't compare days obsessively. "Yesterday was a 4, today is a 5 — I'm getting worse." No. Day-to-day fluctuation is normal. Week-to-week trends are meaningful. Let Iris handle the pattern analysis over time rather than interpreting each data point yourself.
Medications deserve special attention
If you're taking pain medication regularly, tracking when you take it and what happens is one of the most valuable things you can do.
Effectiveness tracking. Does the medication actually reduce your pain? By how much? For how long? Many people take medications out of habit without knowing whether they're still helping. Two weeks of tracking "took medication at X time, pain before, pain after" gives you concrete evidence.
Frequency tracking. How many days per month are you taking pain medication? This matters because medication overuse headache and opioid-induced hyperalgesia are real phenomena — frequent analgesic use can paradoxically increase pain sensitivity. If you're taking over-the-counter painkillers more than 10-15 days per month, that's worth discussing with your provider.
Supplement review. If you're taking supplements for pain (turmeric, omega-3, magnesium, CBD), discuss them with Iris. Some have reasonable evidence; others don't. Some interact with medications. Tracking whether a supplement actually correlates with better days — rather than assuming it helps because it should — turns hope into data.
When to start the analysis
Two weeks of consistent tracking across pain plus two or three parallel variables gives enough data for initial pattern detection. Three to four weeks is better. The analysis looks for which factors most strongly predict your pain levels, whether there are time lags, and whether factors interact (poor sleep alone is manageable, but poor sleep plus high stress reliably produces flares).
Don't try to analyze the data yourself by scrolling through entries. That's what AI is for. Your job is to capture the information consistently. Iris's job is to find the patterns you can't see from inside the experience.
References
- Hypervigilance and pain amplification — Pain, 2004. Attention to pain increasing pain perception.
- The reciprocal relationship between pain and sleep — Sleep Medicine Reviews, 2019. Sleep quality as primary predictor of pain.
- Chronic pain and depression — The Lancet Psychiatry, 2016. Bidirectional mood-pain relationship.
- Fear-avoidance and its consequences in chronic musculoskeletal pain — Pain, 2000. Avoidance as maintaining factor.
- Medication overuse headache and chronic pain — The Lancet Neurology, 2018. Analgesic overuse and pain sensitization.
- Patient self-monitoring of chronic pain — Pain Medicine, 2019. Ecological momentary assessment in pain tracking.
AI helps you design a tracking plan matched to your pain type, your life, and your capacity — starting with the minimum that gives useful data.