Behaviors
Tap a chip when a pattern happens. See 25 days of taps as a heatmap.
When to use this
Use Behaviors when you want a no-friction way to log moments you'd otherwise forget by tomorrow: meltdowns, stims, aggression, elopement, anything else you're watching. One tap per event. No form to fill. The heatmap shows you what your week, fortnight, and month actually looked like, which is the answer to most school and therapist questions.
How it works
Track a behavior
Tap a chip (Meltdown, Aggression, Stimming, anything you set up) and Beacon logs the moment with a timestamp. One tap. No notes form to fill in. Track up to 8 patterns at once.
See the 25-day picture
Every tap fills a cell on the heatmap. Five weeks of days at a glance, darker means more logs. The pattern is easier to read than 25 days of memory.
Tap a day for the detail
Any cell shows the count and date when tapped. Useful when the teacher asks 'was Tuesday a hard day?' and you want a real answer.
Ask Beacon what it sees
Discuss with Beacon attaches the last 25 days to your chat. Ask 'what pattern do you see?' or 'help me write the teacher email about this' and Beacon answers using these specific days.
What Beacon stores when you use it
behavior_logs: Each tap creates one row. Behaviors themselves live in a separate tracked_behaviors table (the chip names + emojis you set up). The log row only stores when a tap happened.
| Column | Type | Example |
|---|---|---|
| id | UUID | 9a5f... Auto-generated. |
| user_id | UUID | your-user-id RLS-locked to you. Nobody else can read it. |
| behavior_id | UUID | → Meltdown Foreign key to the tracked_behaviors row (chip name + emoji). |
| antecedent | TEXT, nullable | (blank from tap path) Set only when you log from the longer form path. Tap-only entries leave it null. |
| note | TEXT, nullable | (blank from tap path) Same as antecedent. Tap-only entries leave it null. |
| logged_at | TIMESTAMPTZ | 2026-05-15 09:42:11 EDT The moment you tapped. This is what the heatmap reads. |
A real example
Sarah tracks her 6-year-old's meltdowns and aggression for the first week of May. She taps the chip each time it happens; no notes, no commentary. By end of week, the data tells the story:
| when | chip | notes |
|---|---|---|
| Mon May 5, 7:12 AM | 🤯 Meltdown | (none) |
| Mon May 5, 6:55 PM | 🤯 Meltdown | (none) |
| Tue May 6, 7:08 AM | 🤯 Meltdown | (none) |
| Wed May 7, 4:30 PM | 😤 Aggression | (none) |
| Thu May 8, 7:20 AM | 🤯 Meltdown | (none) |
| Fri May 9, 7:05 AM | 🤯 Meltdown | (none) |
What Beacon auto-knows
- The chip names and emojis you set up.
- The timestamp of every tap.
- The 25-day heatmap shape (which days had taps, which were quiet).
- Today's tap count for each chip (the chip shows a +N badge on its tile).
What Discuss with Beacon adds
- A summary of the last 25 days framed as context for whatever you're chatting about.
- Beacon can spot patterns across days you'd miss: 'meltdowns cluster on Mondays', '7am is the spike hour'.
- Beacon can use the data to draft a teacher email, an IEP talking point, or a doctor's-visit summary.
Try these with Beacon
“What pattern do you see in the last 25 days of meltdowns?”
Beacon scans your logs grouped by day-of-week and hour. If a cluster shows up (e.g., Monday mornings), it names the cluster and asks what the trigger could be. If there's no obvious cluster, it says so plainly instead of inventing one.
“Help me write an email to my child's teacher about this week's meltdowns.”
Beacon drafts a parent-voiced email referencing the specific days and counts from your logs. No therapy jargon unless you ask. Editable in your reply.
“We're heading into an IEP meeting next week. What talking points should I bring from the behavior data?”
Beacon picks 2-3 patterns it can defend with the data (timestamps + counts) and frames each as a one-sentence talking point, plus the data point to cite if the school pushes back.
“Is 3 meltdowns this week unusual for us?”
Beacon compares this week's count to the prior 3-4 weeks in your data and tells you whether 3 is the high end, the low end, or normal for your child. Honest answer over a soothing answer.
“What single change could I try next week to see if it shifts the pattern?”
Beacon proposes one small change tied to the pattern (e.g., 'try moving morning routine 15 minutes earlier on weekdays when you see the 7am cluster') and reminds you to keep tracking so you'll know whether it worked.