Built by operators who ran ABA clinics.

Six minutes to a signed note. Not an hour after hours.

Wilma® drafts the session note from the data your RBT already collected — payer-aware and goal-linked. The BCBA reviews and signs. AI drafts; humans decide, on every note.

from session end to signed note
6 min
drafted from real session data
Data-grounded
checked before claims ship
Payer-aware
human approval on every note
BCBA-signed

What is ABA session notes software?

The documentation layer that pays — drafted from data, signed by a clinician.

ABA session notes software is how clinicians document Applied Behavior Analysis sessions: what was worked on, the data collected, progress toward goals, and the specific elements payers require to reimburse. Modern systems draft the note with AI from session data — but the BCBA reviews and signs.

The whole industry has converged on "AI session notes." What separates the tools now is the workflow around the AI: per-field accept/reject instead of all-or-nothing, an audit trail of what the AI contributed, payer-specific completeness checks, and a submission-time gate that won’t let an unsigned note be billed. Wilma drafts from your own collected data and keeps the signed note on one record with billing and progress reporting — so it’s written once, compliant, and reused everywhere.

The note writes its first draft from the data you already collected.

With the AI add-on (+$20/user/mo, layered on Core), Wilma drafts the session note from the trial-by-trial and behavior data the RBT captured in-session — goals linked, progress summarized, payer-aware language. The clinician reviews, edits, and signs. Six minutes, not an hour after hours.

Grounded in real data

Drafts come from collected session data, not free-text recall.

Goal-linked

Each note ties to the treatment-plan goals the session targeted.

Edit before sign

Clinicians refine the draft; nothing is auto-finalized.

No after-hours pile-up

Notes close same-day instead of becoming a weekend backlog.

AI drafts. The BCBA decides. Every note, every time.

No note is finalized or submitted without clinician sign-off. Per-field accept/reject on AI suggestions, a clear audit trail of what AI contributed, and submission-time lockouts mean you stay in control — and stay defensible if an auditor ever asks.

Per-field accept/reject

Approve or rewrite each AI suggestion individually — never all-or-nothing.

AI-involvement audit trail

A record of what the AI drafted vs. what the clinician changed.

Submission-time gate

Notes can’t ship unsigned; lockouts enforce review before billing.

Clinician ownership

The signed note is the clinician’s clinical judgment, not the model’s.

Notes that match what your specific funder requires.

Denials and clawbacks come down to whether the note matches the payer’s rules. Wilma checks completeness against payer-specific requirements before the claim ships — medical-necessity language, required elements, signatures — so gaps are caught in minutes, not in a 90-day clawback.

Payer-specific checks

Medicaid, commercial, TPA — required note elements encoded per payer.

Gap detection pre-claim

Missing signatures, language, or data flagged before submission.

Medical-necessity language

Prompts toward the documentation auditors and funders expect.

Audit-ready trail

Timestamped, attributed notes with a defensible edit history.

Your note formats, your rules — not a generic medical template.

Session-note templates for assessment, treatment, supervision, and parent training, configurable to your practice and per-payer requirements. Per-field admin direction guides the AI toward how your clinicians actually document.

ABA-native templates

Assessment, treatment, supervision, and parent-training note types.

Per-payer formats

Required fields and structure adapt to each payer’s rules.

Admin AI direction

Guide the draft per field to match your documentation standards.

Verbatim prior-note reuse

One-click carry-forward of standing context where appropriate.

Captured once. Note, billing, and progress report all flow from it.

Because notes live on the same record as data collection, scheduling, and billing, a signed note feeds the claim and the progress report automatically. No copy-paste between systems, no reconciling a clinical tool against a billing tool.

Note → claim

Signed session data converts directly to billing entries.

Note → progress report

Authorization-renewal prep assembled from signed notes and data.

No duplicate entry

Clinical, documentation, and billing share one source of truth.

Real-time status

See which notes are drafted, signed, and billed at a glance.

Buyer's Checklist

Evaluating ABA session notes software? Demand every line.

FAQ

Questions clinicians ask about ABA session notes.

What is ABA session notes software?

How does Wilma draft session notes?

Is the AI making clinical decisions?

How does this prevent denials and clawbacks?

Can I customize note templates?

What safeguards protect against bad AI output?

Do notes connect to billing automatically?

How much does it cost?

Can I migrate historical notes?

How does Wilma compare to standalone AI note tools?

Is Wilma HIPAA compliant?

Customer Story · Clinical

Why a clinical team left "click-after-click" software behind

How fewer clicks for notes, data, and supervision gave a BCBA their day back.

See a session note drafted, checked, and signed — live.

Thirty minutes. Bring your note format and a payer that gives you trouble. We’ll show the draft from data, the payer check, and the sign-off.

Choosing a documentation system

How to evaluate ABA session note software

A session note is the clinical record and the billing justification at once. Judge a documentation system on whether it produces notes that survive an audit without asking clinicians to write them twice.

  • 1Does the note build from the data, or start blank?An RBT running six sessions a day cannot write six individualised narratives after hours. Ask them to, and you get cloned notes — which is both an audit flag and a sign nobody was really documenting. The objective section should be populated from the data already collected, so clinician effort goes into assessment and plan where judgment is actually required.Red flag: A template library presented as the answer to volume. Templates without data population are how notes become identical.
  • 2Do the times reconcile with the units billed?Times that do not match billed units are the most common technical denial and the easiest to prevent. The note's start and end times, the session record and the claim should be the same times, checked automatically rather than by a biller comparing two screens.Red flag: Session times entered separately on the note and the timesheet, with no reconciliation between them.
  • 3Can it evidence medical necessity, not just activity?Most notes describe what happened. Payers require justification for why the service remains necessary at this intensity. That means referencing the data trend rather than a single session, naming what would occur without the service, and tying the session to named treatment plan goals. A system that surfaces the trend while the clinician writes makes that a habit rather than an aspiration.Red flag: No access to prior sessions or the goal set from inside the note editor.
  • 4Is signing controlled and dated properly?Missing or late signatures invite scrutiny of everything around them, and many payers specify a signing window. You want signature capture with credential, a supervisor co-sign path where required, and visibility of what is unsigned before it ages rather than after.Red flag: Notes editable after signature with no audit trail of what changed.
  • 5If it drafts with AI, who is accountable for what it says?AI drafting is genuinely useful for the objective section, and genuinely dangerous if the draft is treated as the note. The only defensible arrangement is that the draft is generated from data actually collected, the clinician reviews and edits it, and sign-off is never automated. A note nobody read is a compliance problem however good the draft was.Red flag: Any workflow where a note can reach a claim without a human signing it, or drafting that invents content the data does not support.

Before you sign

Questions worth asking on the demo

  • Show me a note being generated from session data, and show me what the clinician can change before signing.
  • How do the note times, the session record and the billed units stay in agreement?
  • Can a clinician see the data trend and the treatment plan goals from inside the note editor?
  • What is the audit trail if a signed note is amended?
  • Is AI note drafting included, or a paid add-on, and is it built in-house or delivered by a partner?
  • Show me the unsigned-notes view an administrator would work from.

Glossary

The terms you will hear

SOAP note
Subjective, Objective, Assessment, Plan. Separating caregiver report from measured data usefully prevents parent report being recorded as though it were data.
DAP note
Data, Assessment, Plan. Combines subjective and objective into one section; shorter and better suited to high-volume direct-service documentation.
Medical necessity
The justification that a service at a given intensity is required now. A counterfactual claim — what would happen without it — supported by trend rather than a single data point.
Cloned notes
Identical or near-identical narrative repeated across sessions. A well-known audit flag, and usually a symptom of documentation being unsupported rather than clinicians being careless.
Co-signature
A supervising clinician's signature on a note authored by a technician or trainee, required by some payers and some state rules for certain services.
Documentation window
The period within which a note must be completed and signed after the session. Set by payer or accreditation standard; notes signed outside it are a denial and audit risk.

Keep reading

Related guides on running an ABA practice — the same operation, from a different angle.