Skip to content

Built by a Board Certified Behavior Analyst

The behavior data, the service minutes and the plan — in one place.

Beehave is practice management for ABA in schools. Technicians collect data on a phone in the room. Supervisors see the caseload, the fidelity and the trend. Districts see whether the minutes a child is owed were actually delivered — this month, while there is still time to do something about it.

30-day free trial · no credit card · accounts are invitation-only during the pilot

Session in progress
24:11

Requesting with a full sentence

Intervention

Communication › Expressive Language

100500Sessions% independentBaselineInterventionMastery 80%

Trial by trial

12/ 15 trials

IndGestPartialFull

Saved

Data collection methods
6Data collection methods
Role-based views
9Role-based views
District, agency, platform
3-tierDistrict, agency, platform
Free trial, no card
30 daysFree trial, no card

Why Beehave

Three costs, and they compound

Every ABA provider working in a school setting is paying all three at once. Most software addresses one of them.

  1. 01

    Documentation eats the clinical hour

    Data gets taken on paper, then typed up after the session, then typed again into a progress report. Three passes over the same information, and the third one is written from memory at nine at night.

    • On paper

    • Typed up

    • From memory, 9 p.m.

    One session. Three passes over the same information.
  2. 02

    Turnover resets everything

    Annual turnover among behavior technicians runs between 77% and 103% industry-wide. When the person leaves, so does the context — unless the plan, the data and the reasoning live somewhere other than their head.

    Published industry figure, not a Beehave measurement.

    77103%

    Annual turnover, behavior technicians

    0100% = one whole team
  3. 03

    Nobody knows if the minutes were delivered

    An IEP mandates minutes. Whether they were actually delivered is usually answered by a spreadsheet somebody rebuilds each month — and answered too late to fix.

    • Mandated

    • Delivered

    Reconciled next month, if at all — too late to fix.

How it works

One record, three vantage points

The datum a technician taps in a classroom is the one a supervisor graphs and the one a district counts against the mandate. It is entered once and it is never retyped.

01

In the room

The technician records on a phone while the session runs. Six recorders, one per method, with tap targets sized for a hand that is also doing something else — and a queue that holds the data when the signal does not.

02

At the desk

The supervisor opens the same goal and sees a graph, not a pile of paper: phase lines where conditions changed, a trend line through the current phase, and fidelity scores for the person collecting it.

03

At the district

Delivered minutes are checked against what the IEP mandates while the month is still open. Compliance stops being a document written in June about something that went wrong in October.

Features

Everything the work actually needs

Not a general practice-management tool with an ABA skin. Every screen below exists because somebody doing this job needed it.

Data collection that matches the method

Trial-by-trial, frequency, duration, interval, task analysis and ABC — each with a recorder built for it, not a text box. Large tap targets, an offline queue, and auto-save between taps.

  • Trial-by-trial
  • Frequency
  • Duration
  • Interval
  • Task analysis
  • ABC

Service minutes against the mandate

Delivered time is its own record with a named practitioner, so a full day beside a child is never silently counted as a delivered service minute. Overlap is derived, never guessed.

New

A watch list that can actually be overdue

The children you are worried about who are not yet receiving services. Who is on it, who put them there and why, who observes, at what cadence — and what took them off.

FBAs and behavior plans, drafted

Upload the IEP and get structured sections back. QABF and FAST compiled in, convergent scoring, and a district report that declares a missing section rather than dropping it.

Fidelity you can evidence

Observation checklists with yes/no/NA or 5-point scoring, scored against a snapshot of the template as it stood on the day. Trends per staff member over time.

Schedules, timesheets and countersignature

Recurring sessions, weekly timesheets, and per-day supervisor countersignature — because presence is a daily fact and nobody is present for somebody else's whole week.

Mileage and deployment

Trip logging with automatic distance, saved daily routes, and a live map of where staff actually are against where they were scheduled to be.

Reports that reconcile

Service delivery, utilization, compliance and cross-agency comparison — plus a mileage-against-timesheet check that surfaces the days that disagree.

Permissions as verbs, not pages

One catalogue of what a person may do, resolved by one engine, with default-deny at the bottom. Change what a whole role can do, or grant one person one capability with a reason and an expiry date.

Who it’s for

Two sides of the same contract

Districts and the agencies they contract see different things, on purpose. Neither one sees another agency’s data.

For school districts

See every provider working in your schools

  • Every student, every school and every contracted agency on one roster
  • Compliance against IEP mandates, per student and district-wide
  • Compare one agency against another — vendors you can actually manage
  • FBA and behavior-plan review queues for program specialists
  • Staff reach your campuses only after your district approves them
See district plans

For ABA agencies

Run the clinical work and the operation together

  • Caseloads, supervision, and a network view of who covers whom
  • Staffing requests, callouts and coverage on one board
  • Credential tracking with expiry, before it becomes a compliance event
  • Timesheets, mileage and reconciliation without a spreadsheet
  • Your data isolated from every other agency on the platform
See agency plans

Who built it

Written by someone who has to use it on Monday

Beehave is built by a Board Certified Behavior Analyst who runs ABA programs in California school districts. The reason the data-collection screens have large tap targets and an offline queue is that they get used standing up, in a classroom, on a phone with one bar of signal.

It is honest about what it is: a young product in pilot with districts, not a decade-old incumbent. What it will not do is guess at clinical content, or quietly change a number a funder relies on.

Built for records that get audited

Full-history models rather than overwritten fields: plans version rather than update, entries are retracted rather than deleted, and every read of a clinical narrative is logged with who read it.

Tenant isolation, and it is tested

Every list query is organization-scoped, and an automated suite proves one organization cannot read, edit or deactivate another's student records across the boundary.

The clinical judgement stays yours

Plans, reports and the questions families read go into student files. Where a rule is a clinical decision, the software asks rather than inventing one.

Pricing

Per seat, per month. No setup fee.

Students and parents never count as seats. Two months free on annual billing.

Districts

from $29 / seat / mo

Oversight · Command · Enterprise

Agencies

from $39 / seat / mo

Clinical · Operations · Enterprise

See it against your own caseload

Thirty minutes, a real district scenario, and honest answers about what is built and what is still coming. Accounts are invitation-only during the pilot, so a walkthrough is how you get one.

  • No credit card, and no contract to start
  • Your data stays isolated from every other organization
  • Bring your roster; we do not need your whole student system
  • Export what you have entered at any time