The short answer
An observation records what you saw, heard or did. An assumption adds a reason, mood or intention you did not directly witness. The fix is usually simple: describe the action, drop the guess, and let the reader draw their own conclusion.
An observation is what you directly saw, heard or did during a shift. An assumption is the story layered on top of it, the reason, mood or intention you guessed at but did not actually witness. Good shift notes lean on the first and leave the second out. Here are six common sentences, rewritten to show the difference, with no diagnosing and no guessing at why someone did something.
1. Naming a mood instead of describing it
Before: Participant was agitated all afternoon. After: Participant paced the lounge room for around 20 minutes, spoke in a raised voice twice, and declined to sit down when asked. The word agitated is a conclusion. Pacing, raised voice and declining to sit are things another reader can picture and check against their own shift.
2. Guessing a cause
Before: He was upset because he missed his medication. After: He was crying at 3pm. Medication was not given at 2pm as scheduled; this is recorded separately in the medication log. Linking the crying to the missed dose might be right, but it is a guess unless he said so. Recording both facts side by side lets the next reader connect them if it is true, without it being stated as fact.
3. Labelling behaviour as refusal
Before: Participant refused to cooperate with the shower routine. After: When offered a shower at 8am, participant said no and walked to the bedroom. Offered again at 8:30am; participant agreed. Refused to cooperate sounds like a character judgement. Saying no and walking away is what happened, and it also shows the outcome, which refused does not.
4. Assuming why someone did something
Before: She was seeking attention by calling out repeatedly. After: She called out six times between 6pm and 7pm. Each time, support worker checked in and she asked for water or a blanket. Seeking attention is an interpretation of intent. Counting the calls and noting what she asked for each time is something anyone reading the note later can rely on.
5. Using clinical-sounding shortcuts
Before: He was having an episode during dinner. After: During dinner, he stopped eating, pushed his plate away, and put his hands over his ears for about two minutes, then resumed eating without comment. Episode implies a diagnosis or pattern that a support worker is not in a position to confirm. Describing exactly what happened, and for how long, is useful to anyone reviewing the shift, including a clinician if one is involved later.
6. Vague quantity words
Before: Ate well at lunch and slept badly overnight. After: Ate all of the sandwich and half the fruit at lunch. Was awake and out of bed three times overnight, at 12:40am, 2:15am and 4:50am. Well and badly mean different things to different readers. Numbers and times mean the same thing to everyone.
A worked example
Here is a short note before and after the same edit. Before: Participant was in a bad mood after lunch, seemed anxious, and refused activities because he was probably overtired. After: After lunch, participant sat alone in his room with the door closed for about 40 minutes. When invited to join the afternoon activity, he said not now and stayed in his room. He had been awake since 5am, noted in the morning handover. The second version tells the next worker what actually happened and gives them the timing to form their own read on it, without the note doing the diagnosing for them.
The takeaway
- If a word could be argued with, it is probably an assumption. If a word could be timed, counted or quoted, it is probably an observation.
- Write down what was said, using quotation marks, rather than what you think it meant.
- Keep cause and effect as two separate facts unless the person told you the connection themselves.
- If you genuinely need to flag a concern, say what you observed and that you are flagging it for follow-up, rather than naming a cause.
- Whatever system you use to record shifts, including the shift notes and incident report fields in Sparks Provider, the same habit applies: describe the shift, not the story you have built around it.
Frequently asked questions
What is the actual difference between an observation and an interpretation?
An observation is something you directly saw, heard or were told, described in plain terms. An interpretation adds a reason, mood or motive that you inferred rather than witnessed.
Can I ever include my own impression in a shift note?
Yes, but label it as your impression rather than stating it as fact, for example: In my observation, he seemed tired, though he did not say so.
How do I record a mood without guessing at it?
Describe what you saw or heard, such as tone of voice, posture, words used or actions taken, and let the reader form their own view rather than naming the mood for them.
What if I want to flag a concern but I am not sure what caused it?
Write down exactly what you observed and note that you are flagging it for follow-up, without naming a cause you did not witness.