Logging a behaviour incident

Behaviour logs in Blumi are designed to be useful for future support — not a record of "bad behaviour".

What to capture

• Antecedent — what was happening just before.
• Behaviour — describe what you saw, not what you assumed.
• Consequence — what happened next, including what helped.
• Duration — a rough estimate is fine.

Tone matters

Write as if the participant might read it one day — because they might. Avoid words like "tantrum", "manipulative", "non-compliant". Stick to behaviour you observed.

After the log

Blumi suggests related strategies from the team's library and flags any patterns (time of day, environment, trigger).