Loadout // KIT-04
Symptom and Functional-Impact Log
The rating schedule is not a script. Record what actually happened so you can remember the pattern and explain it accurately; this log is not a diagnosis, an official VA form, or a replacement for treatment.
01 // What to record
Use the same fields. Memory is a terrible records clerk.
Consistency makes a log easier to understand. Record entries close to the event when possible, using plain language and your own observations. Three months later, “it was pretty bad sometime last week” will not become more precise through confidence.
- Date and approximate start time
- Symptom or episode
- Duration and intensity in your own terms
- Activity interrupted or limited
- Medication, rest, treatment, or other response
- Work, sleep, mobility, concentration, or daily-living impact
02 // Accuracy controls
Real life is messy. A suspiciously perfect log is, too.
A useful log can include good days, uncertain entries, and changing patterns. Do not copy language you did not use, exaggerate frequency, or convert an estimate into a false exact measurement.
If a clinician gives you a specific tracking method, follow that clinical instruction instead of this general framework.
03 // How to use it
Summarize the pattern. Keep the receipts.
A short monthly summary can identify frequency and functional themes, while the underlying entries preserve context. Discuss relevant symptoms with your clinician and accredited representative when appropriate.
Source rack
Trust, but verify. Mostly verify.
These official sources carry the factual load. Rules and public guidance change; screenshots and confident strangers do not receive automatic grandfather status.