> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sightlinebehavior.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Anecdotal Recording

> Free-form, timestamped note-taking during an observation: a chronological account of what happens, with context quantitative methods miss.

<CardGroup cols={2}>
  <Card title="When to use" icon="circle-question">
    * Early assessment, before you know which behaviors to target
    * Capturing environmental and peer context around behavior
    * Documenting qualitative clinical impressions
    * Adding contextual depth alongside a structured method
  </Card>

  <Card title="Setup" icon="sliders">
    1. Choose Anecdotal from the method picker
    2. Optional: enable activity context to tag each entry
    3. No pre-defined behaviors needed
  </Card>
</CardGroup>

Instead of counting, timing, or scoring intervals, you write a chronological account of what happens (student behavior, peer interactions, environmental factors, clinical impressions), with automatic timestamps.

Anecdotal is available standalone, and as an embedded log alongside every other method, so you can add timestamped notes during frequency, duration, interval, latency, and ABC sessions without switching. See [Anecdotal alongside other methods](#anecdotal-alongside-other-methods).

## Keyboard shortcuts

| Key     | Action                    |
| ------- | ------------------------- |
| `Enter` | Save entry with timestamp |
| `Space` | Pause / resume timer      |
| `Cmd+E` | End session               |
| `Cmd+/` | Show all shortcuts        |

## Recording notes in Sightline

A large text area is available for free-form typing. The session timer runs in parallel with your notes. Type what you see, press **Enter**, and Sightline attaches the current elapsed time. Notes appear chronologically on screen with timestamps visible, and you can scroll back to review earlier entries or fix typos without stopping the timer. If activity context is enabled, the activity bar sits at the top, and each note is tagged with the current activity, so analysis can reference "during independent work, Marcus..." or identify patterns specific to certain activity types.

<Tip>
  **Stay objective.** Report observable facts, not inferred mental states.

  * Instead of "Marcus was frustrated" → "Marcus clenched his fists and said, 'This is too hard.'"
  * Instead of "The teacher was annoyed" → "The teacher sighed and repeated the direction twice."
  * Instead of "Marcus is lazy" → "Marcus put his pencil down and stared at the window for 90 seconds without writing."
</Tip>

Objective phrasing keeps notes defensible and focused on behavior rather than interpretation.

Anecdotal recording is cognitively demanding — you watch, type, and synthesize at once — so use shorthand during the session ("indep work" instead of "independent work") and expand notes after recording ends. A practice run on a low-stakes observation helps before live use.

### What the record looks like

Entries are captured chronologically as you write them, each stamped with the session elapsed time:

```
0:00: Marcus entered the classroom and went directly to his assigned seat. He unpacked his materials without prompting.

0:45: The teacher began whole-group instruction on long division. Marcus oriented toward the teacher, made eye contact, and appeared attentive.

2:15: The teacher posed a question to the class. Marcus raised his hand before several peers and answered correctly when called on.

3:30: Transition to independent practice. Teacher distributed worksheets. Marcus picked up his pencil and began the first problem.

4:10: Marcus put his pencil down and looked at a peer across the room. The peer was also working. Marcus returned to his worksheet after about 10 seconds.

5:45: Marcus appeared to struggle with problem 5. He erased twice. He then raised his hand.
```

There is no built-in thematic grouping: Sightline stores notes in the order you write them. If you want thematic analysis, do it during the write-up stage after recording ends, using the write-up tools or your own synthesis.

### Adding contextual detail

Anecdotal recording is at its best when it captures details that structured methods can't:

* **Environmental factors**: "The fire alarm test occurred at 8:15, causing a 5-minute classroom evacuation. Upon return, Marcus appeared slightly anxious but settled within 2 minutes."
* **Peer context**: "During independent work, when peer X was seated nearby, Marcus disengaged more frequently than when that peer was absent."
* **Adult-student interaction**: "When the teacher provided specific praise ('You organized that information clearly'), Marcus smiled and continued working. Generic praise ('Good job') did not elicit visible response."
* **Sequence of events**: "The off-task period began immediately after Marcus made an error on the previous problem. The teacher did not provide error correction feedback."

## Reading the results

After recording, Sightline displays your anecdotal notes as a chronological transcript from start to finish: each entry with its elapsed time clearly marked and your complete note text. If a session mixes timed and untimed notes, a Combined / Split toggle switches between one interleaved list and separate Timed and Untimed cards.

Anecdotal interpretation has a boundary worth holding. Within a single session, you can identify the patterns you observed: what behaviors repeat, what precedes them, which contexts they're absent in. What those patterns *mean* about the student, a function, a capability, a trait that holds across settings, is a cross-session, evaluation-level conclusion built from repeated observations and other data sources. One session names the pattern; it doesn't name the cause.

## Common mistakes to avoid

Strong anecdotal recording is specific, chronological, objective, complete (antecedent, behavior, consequence), and contextual. The failures worth guarding against:

<AccordionGroup>
  <Accordion title="Over-interpreting behavior" icon="magnifying-glass">
    Report what you see, not your conclusions

    * ❌ "Marcus was frustrated and gave up."
    * ✓ "Marcus erased his answer, sighed, and put his pencil down without raising his hand."
  </Accordion>

  <Accordion title="Vague time references" icon="clock">
    Use the timer

    * ❌ "At some point later, Marcus went off-task."
    * ✓ "At 5:42, Marcus looked away from his worksheet and stared at the window."
  </Accordion>

  <Accordion title="Incomplete context" icon="layer-group">
    Always describe what prompted the behavior

    * ❌ "Marcus called out."
    * ✓ "When the teacher posed a question to the class, Marcus called out an answer without raising his hand."
  </Accordion>

  <Accordion title="Missing baseline for comparison" icon="chart-simple">
    Anecdotal recording alone doesn't answer "is this typical?" If you're unsure whether the behavior is typical, record 1–2 sessions using frequency or interval first, then add anecdotal notes for contextual depth.

    * ❌ "Marcus disengaged during independent work."
    * ✓ "Marcus disengaged during independent work. A randomly selected peer remained engaged throughout the same period."
  </Accordion>

  <Accordion title="Too much anecdotal detail, too little time" icon="filter">
    You don't need to narrate every minute. Focus on key moments, patterns, and transitions, and let the referral question guide which moments you describe in detail. If 5 minutes pass uneventfully, a simple note ("5:00–10:00: Marcus worked steadily on problems 1–5, no notable changes") is fine.
  </Accordion>

  <Accordion title="Jargon-heavy notes" icon="book">
    Your anecdotal notes will be read by teachers, families, and IEP teams. Use clear, jargon-free language where possible.
  </Accordion>

  <Accordion title="Only recording problems" icon="circle-check">
    Anecdotal recordings often focus on problem behavior, but including moments of success, engagement, and strength gives a balanced account.
  </Accordion>
</AccordionGroup>

## Anecdotal alongside other methods

You rarely need a dedicated anecdotal session to get anecdotal data. Sightline embeds a timestamped observation log in frequency, duration, interval, latency, and ABC recording screens, so you can capture context in line with quantitative scoring without switching methods.

### How it works during any structured session

* Press **N** at any point to open the observation log input
* Type your note: quick phrases and hashtags are available the same way they are in anecdotal recording
* Press **Enter** to commit the note with the current elapsed time
* The note appears in the session log alongside your scored events

Because the same log appears across methods, anecdotal is effectively a layer that sits on top of the structured data. Examples of how the paired data reads:

* **Frequency + log:** "The student called out 14 times during the 30-minute observation. Log entries show call-outs occurred almost exclusively during whole-group Q\&A moments when the student knew the answer."
* **Interval + log:** "Off-task was scored in 65% of intervals during independent work. Log entries note that off-task episodes were consistently preceded by task errors."
* **ABC + log:** "The student displayed 8 instances of work refusal. Log entries show refusal was preceded by open-ended tasks but not by choice-based tasks."

### When to use a dedicated anecdotal session instead of the embedded log

* You don't yet know which behaviors to target with a structured method
* You want a continuous written record rather than intermittent notes beside scoring
* The session's primary output is the anecdotal record itself, not quantitative data

## Example anecdotal observation

Here's an excerpt from an anecdotal recording of a student during independent math work.

<Accordion title="Show full transcript" icon="book">
  ```
  [0:00] Ms. Chen announces: "Everyone take out your math worksheet. You'll solve problems 1 through 10 independently. I'll be circulating." Marcus immediately opens his folder, finds his worksheet, and picks up his pencil.

  [0:15] Marcus reads problem 1 aloud quietly to himself: "If there are 3 groups of 5, how many total?" He writes "15" and checks his work by counting on his fingers.

  [1:30] Marcus moves to problem 2. He reads it, pauses, then begins writing. Peer seated to his left drops a pencil loudly. Marcus looks up momentarily but returns to his worksheet within 2 seconds.

  [2:45] Marcus appears to struggle with problem 4. He reads it three times, erases, reads again. He does not raise his hand. After about 45 seconds, he writes an answer.

  [3:15] The teacher approaches Marcus. "Show me what you did on problem 4." Marcus points to his work. The teacher says, "Walk me through your thinking." Marcus explains his approach. The teacher responds, "That's a good strategy. For this one, let me show you another way." They work through it together briefly.

  [4:00] The teacher leaves. Marcus returns to problem 5 and works steadily, completing problems 5–8 without pause. His posture is upright, and he appears focused.

  [5:15] At problem 9, Marcus again appears uncertain. He erases and writes a new answer. Peer across the room drops a pencil; Marcus looks but continues working.

  [5:45] Marcus finishes problem 10 and raises his hand. The teacher approaches and marks his sheet as complete.
  ```
</Accordion>

From this brief excerpt, you can observe:

* Marcus initiates work promptly and remains engaged most of the session
* He struggles with problems requiring a different approach than he's practiced
* Brief peer distractions don't derail him
* He benefits from direct teacher guidance and can apply new strategies
* He completes work when provided support and returns to independence

***

For summarizing an anecdotal session without overclaiming, see [Writing Up Observation Results](/writing-up-observation-results). For choosing and combining methods, see [Observation Methods](/observation-methods).
