To write symptom notes that separate observations from guesses, record what you directly noticed first: the date and time, what changed, where it occurred, what you were doing, and any detail you can state without explaining why it happened. Put possible causes, diagnoses, and meanings in a separate field labelled “My guess” or “Question for the visit”. Use uncertainty literally: “I noticed”, “I am not sure whether”, and “I want to ask”. Do not quietly turn a sequence—“I took X, then Y happened”—into causation. A useful note preserves both the event and the uncertainty.
This distinction does not make a personal note a medical finding. It makes the note easier to review because the reader can see which parts came from direct observation, which came from memory or context, and which are interpretations to discuss. The goal is disciplined wording, not self-diagnosis.
The OTCCQ framework: five lanes for one symptom note
A strong note can be built with five lanes. The initials form OTCCQ: Observation, Time, Countable detail, Context, Question. Each lane has a different job.
- Observation — what did you directly notice? Write the change in ordinary language. “My left hand felt shaky” is an observation about your experience. “My nerves malfunctioned” is an interpretation unless a qualified professional has already documented that conclusion and you are accurately identifying it as such.
- Time — when did it start, stop or recur? Use the most precise time you can honestly support. If you did not check the clock, write “around lunchtime” rather than inventing a minute.
- Countable detail — what could you count, time or locate? Examples include “three episodes”, “about ten minutes by the kitchen clock”, or “left wrist”. A countable detail is optional. False precision is worse than a candid approximation.
- Context — what else was happening? Record routine facts that may help you remember the event: activity, posture, food, sleep, travel, a treatment entry, or a change in routine. Context belongs in the record without being promoted to a cause.
- Question — what are you wondering? Put the suspected explanation here. “Could this be related to the schedule change?” preserves the idea without asserting that the change caused the symptom.
The framework is deliberately asymmetric: four lanes describe the record, while only one holds interpretation. That keeps a compelling theory from swallowing the details that could later challenge it.
The observation-versus-guess worksheet
Use this two-column worksheet before turning rough notes into a dated entry. A single sentence may need to be split across both columns.
| Observation or context I can report | Guess, conclusion or question to keep separate |
|---|---|
| What I saw, heard, felt or did | What I think it means |
| A date, clock time or honest approximation | A diagnosis I suspect |
| A duration I timed or clearly remember | A cause I infer from the timing |
| A count, location or directly recorded value | A prediction about what will happen next |
| A routine or treatment event recorded nearby in time | A claim that the routine or treatment produced the change |
| “I did not record the end time” | A detail filled in because it seems likely |
Run each clause through a simple test: Could another person disagree with my explanation while still accepting that I noticed this event? If yes, split it. Keep the noticed event on the left and move the explanation to the right.
This is not a test of whether a guess is sensible. A plausible guess is still a guess. Keeping it visible in the right-hand column is more useful than deleting it, because it can become a focused question.
Example: rewriting a causal-sounding note
Rough note
The new evening schedule made me dizzy all morning, so the treatment is clearly wrong for me.
The sentence contains potentially useful material, but it merges an observed experience, timing, routine context, duration, causation and a treatment conclusion. It also leaves basic uncertainties hidden.
Worksheet pass
| Observation or context I can report | Guess, conclusion or question to keep separate |
|---|---|
| “I felt dizzy” | “The evening schedule caused it” |
| It was noticed in the morning | “The treatment is wrong for me” |
| The routine was logged in the evening | “New” may need a date: when did the schedule change? |
| The exact start and end were not written down | “All morning” may overstate a duration that was not timed |
Rewritten dated note
Date: 30 July 2026 Observed change: I felt dizzy after getting out of bed and again while making breakfast. Timing: First noticed around 07:30. I noticed it twice before 09:00. I did not record when it fully stopped. Direct details: Both episodes happened while I was standing. I sat down after each one. Routine context: My journal shows the treatment routine at 20:00 the previous evening. This was the third evening on that schedule. Uncertainty: I do not know whether the schedule and the dizziness are related. Question for the visit: Could the timing of this symptom be relevant to reviewing my evening routine?
What changed in the rewrite
- Direct observation: “I felt dizzy” remains the person’s description rather than becoming a diagnosis.
- Timing: The vague phrase “all morning” becomes two bounded episodes plus an explicit missing end time.
- Routine context: The evening entry is retained because it may help with chronology.
- Uncertain interpretation: The possible relationship is neither asserted nor erased.
- Separate question: The treatment conclusion becomes something to raise, not an instruction to change treatment.
The rewrite does not prove that the episodes were unrelated to the routine. It simply prevents chronology from being presented as proof of cause.
A fill-in-the-blank dated symptom-note template
Copy this template and leave any unsupported field blank rather than reconstructing it later:
Date of entry: [date written]
Date of event: [same date / other date / unsure]
Observed change:
I noticed [plain description of what I felt, saw or could do differently].
Timing:
It began [time or honest approximation].
It [ended / changed / returned] at [time, approximation or “not recorded”].
This happened [count or “count not recorded”].
Direct details:
Location: [body area or “not sure”]
What I was doing: [activity/posture]
What I counted, timed or recorded: [detail and how it was obtained]
Routine context:
Around the same period, my recorded routine included [neutral fact].
Other context I want to remember: [neutral fact].
Uncertainty:
I am not sure whether [possible interpretation].
I may be missing [known gap in the record].
Question for the visit:
I want to ask [one specific question].The phrases in brackets are prompts, not mandatory data. “Not recorded” is valid information. It marks the boundary of the record and prevents later confidence from being mistaken for contemporaneous detail.
The claim-strength decision table
Use the table when you are unsure whether a sentence belongs in the note as written.
| If your sentence does this… | Keep it? | Rewrite action |
|---|---|---|
| Describes a sensation or visible change in your own words | Yes | Add time or location if genuinely known |
| Reports a time copied from a dated entry | Yes | Identify it as recorded context |
| Uses “always”, “never” or “all day” without a complete record | Not as written | Replace with the occasions actually noted |
| Says one event caused another because it happened first | No | Record the sequence; move causation to a question |
| Gives a diagnosis as your own conclusion | No | Record the symptom; place the suspected diagnosis under questions |
| Includes a measured value | Usually | Preserve the value, unit, date and source exactly as recorded |
| Mixes remembered and contemporaneous details | Not as written | Label what was added later and what remains uncertain |
| Recommends changing a treatment | No | Keep the note descriptive and raise the concern with an appropriate professional |
A note passes this table when every strong claim has a clear basis in the record. It does not pass merely because it sounds formal.
Implementation: turn a rough note into a usable entry
- Write the raw version without polishing it. Capture the words you naturally use while the event is still recallable.
- Underline explanation words. Look for “because”, “caused”, “means”, “must be”, “proof”, “always” and “never”. They are prompts to inspect, not automatically forbidden words.
- Split the clauses into the two-column worksheet. Put directly noticed facts and routine context on the left. Put causes, diagnoses, predictions and recommendations on the right.
- Build the OTCCQ note. Transfer Observation, Time, Countable detail and Context. Convert the right-hand column into one or more Questions.
- Mark the gaps. Use “approximately”, “not timed”, “not recorded” or “added from memory on [date]”. Do not use a precise placeholder where the detail is unknown.
- Read only the observation lanes. Ask whether they still make sense if your current theory turns out to be wrong. If not, interpretation has probably leaked back in.
- Keep the relevant date range narrow when preparing to review. Select entries that help show the event and its immediate context rather than exporting an entire journal by default.
- Review before sharing. Check names, dates, units, private context and unanswered assumptions. A clean layout cannot correct an inaccurate entry.
If you use an app, preserve the same lane boundaries rather than compressing everything into a polished narrative. Genetiqo Vault’s Journal can hold dated treatments, routine logs and symptoms; a Visit Brief can organise entries from dates you select for review before export. The Genetiqo Vault guides explain the current non-diagnostic journal and report workflows. Longer report ranges and PDF or CSV exports are optional Pro capabilities, so check the app’s current limits rather than assuming a feature is included.
A quick pre-visit quality check
Before using a note in an appointment, ask:
- [ ] Does the event have a date, or is the date uncertainty visible?
- [ ] Are the symptom words my direct description rather than a diagnosis?
- [ ] Did I distinguish exact times from approximations?
- [ ] Are counts, units and locations copied accurately?
- [ ] Is nearby routine or treatment information labelled as context rather than cause?
- [ ] Have I avoided “always” and “never” unless the record supports them?
- [ ] Are details added later labelled as later recollection?
- [ ] Is each suspected explanation in the uncertainty or question field?
- [ ] Is there one clear question I want answered?
- [ ] Have I reviewed what I intend to share and removed unrelated private material?
Do not “improve” a note by making it more certain. Improve it by making the limits of certainty easier to see.
Limitations
This method organises wording; it does not determine whether an observation is medically significant, whether two events are causally related, or whether a suspected diagnosis is correct. A personal record can be incomplete, affected by recall, or based on an imprecise description even when every field is filled.
Countable detail is not automatically better evidence. Timing an episode after repeatedly checking a clock may still produce an approximate account; a manually entered value may contain a transcription error. Preserve how a detail was obtained and avoid treating the template as validation.
The framework can also become burdensome. For frequent events, a short consistent record may be more sustainable than a detailed narrative. Choose the smallest set of fields that captures the change, timing, context and uncertainty. Do not delay seeking appropriate help in order to perfect a note. Genetiqo Vault records and organises information entered by the user; it does not diagnose, prescribe, calculate doses, recommend treatment or provide emergency care.
Finally, separating a guess does not make it irrelevant. Interpretations can guide useful questions. The boundary simply lets another reader assess the observation without first accepting the explanation.
FAQ
Is “I felt worse” an observation or a guess?
It is an observation, but it is broad. Add what “worse” meant to you at that moment: a stronger sensation, a new location, a repeated episode or an activity that felt different. Do not add detail you did not notice.
Can I mention a treatment next to a symptom?
Yes, as dated context. Write the treatment or routine event and the symptom timing separately. If you think they may be related, place that relationship under uncertainty or in a question rather than stating that one caused the other.
What if I only remember the symptom later?
Record the event date as approximately as needed and include the date you wrote the note. Label details added from memory. This is more transparent than making a retrospective note look contemporaneous.
Should I use medical terminology?
Use a term only if it accurately reflects what was documented or what you directly mean. Plain language is often better for sensations and functional changes because it does not imply an unsupported diagnosis. If a term came from an existing record, distinguish that recorded wording from your own interpretation.
What if I cannot measure duration or intensity?
Do not invent a scale or duration. State what you do know: “still present when I went to bed”, “noticed twice”, or “end time not recorded”. Honest bounds are useful even when no number is available.
Does a well-structured symptom note prove a cause?
No. Structure makes the basis and uncertainty of each statement visible. It does not establish medical causation or confirm a diagnosis.
How many questions should I add?
Start with one question tied to the specific entry. If several guesses compete, list them separately without choosing a winner. The note should help you remember what to ask, not attempt to answer it.
Keep meal evidence in its own record
If the observation may depend on what was eaten, record the symptom and the meal as separate evidence rather than turning the relationship into a conclusion. EatEasier’s guide to choosing meal-photo, label-scan or recipe-macro records can help select the food-record method while the health note remains observational.