Evidence check · July 2026Current rules and proposals, kept separate. View sources
WELLDASH

The grammar of what happened.

Fifty years ago the field learned that behaviour has a function. The unfinished chapter is making function-finding continuous — computed from a person’s own ordinary record instead of scheduled, expensive and stale. This is the map of how WellDash closes that chapter: four pillars, in the words the system actually uses.

Four pillarsCode-true namesCitations attachedBoundaries stated

Fifty years to find the function. One problem left.

The discovery that the right question is not “what is wrong with this behaviour” but “what is this behaviour for” took half a century. Every stage below is inherited in WellDash’s design — including the stage that has not been finished.

1913–1957

The behaviourist foundation

Watson’s manifesto, then Skinner’s operant analysis: behaviour is shaped by its consequences. The seed of everything after — if consequences select behaviour, behaviour serves them.

1968

Applied behaviour analysis is founded

Baer, Wolf and Risley’s founding statement gives the discipline its name and its standards.

1977

Behaviour works for the person

Carr reframes self-injury as operant, not pathology: the question is not what is wrong with the behaviour but what the behaviour is for.

1982/1994

Function becomes measurable

Iwata and colleagues build the functional analysis — controlled conditions that let a behaviour’s function reveal itself empirically.

1985

The replacement era begins

Carr and Durand’s functional communication training: teach an easier ask that earns the same outcome.

1992–2013

The aggregation correction

Researchers measure identical-looking behaviours serving different functions in the same person. Treating behaviour by its appearance is established as an error; function is the unit.

1999–2015

Positive behaviour support matures

Multi-element models, proactive-first practice, restraint reduction, and the UK PBS competence framework: quality of life becomes the outcome.

The open chapter

Function-finding that never goes stale

Formal functional analysis is powerful and expensive — specialist time, controlled conditions, and a report that ages as the person’s life moves. The unfinished chapter is making function-finding continuous, from the person’s own ordinary record. That is the problem WellDash is built to close.

Pillar 1 · Independence NICE NG74

The fade: support that plans its own exit

Every response in a WellDash plan step is a configuration — four dials recorded together: strategy, cue, assistance, manner. Independence work is the discipline of moving two of those dials one rung at a time, on evidence.

  • The assistance ladder, faded downwards: hand_over_handpartial_physicalsupervisionnone. A permanent floor where safety requires it is legitimate — floor is not failure.
  • The cue ladder: none · environmental · gestural · modelled · verbal_enabling · verbal_direct. modelled is the demonstration rung — show the person first, hands off entirely. A demonstration is a teaching dose, never doing-for.
  • Who did the doing, every time: performed_byperson, shared or carer_did_for. Doing the task for someone is a different kind of record, never a heavier rung of assistance. The doing-for → shared → person curve is the reablement line, dated, computed from the same rows.
  • What the hands did, when hands were on: touch_kindbearing (taking the weight) and/or guiding (directing the movement). Most real hands-on care is both at once, and the record says so.
  • The working rules: one axis per revision — change the physical rung or the cue, never both, so the record can attribute what worked. Struggle steps support up now; success steps it down next time. Acquisition runs most-to-least; maintenance runs least-to-most. Never fade past the authored floor. Consent rides every touch.

The evidence behind the shape: scoring physical assistance and cognitive prompting concurrently, as two rails, is warranted by the performance-assessment literature (PCPT-ALF, Bowen 2017; PASS’s nine-level assist hierarchy, Chisholm 2014). The fade mechanics are classical: graduated guidance fades touch (Foxx & Azrin 1973); time delay fades the cue (Touchette 1971); support shifts contingently with success and struggle (Wood & Middleton 1975); fading direction differs between acquisition and maintenance (Demchak 1990; Libby et al. 2008). Over-helping is iatrogenic — prompt dependence and learned non-use are the recorded harms of helping too much. And UK reablement carries the same posture at guideline level: NICE NG74 tells practitioners to observe and guide rather than automatically intervene, the SPRU evaluation names the practice “standing and watching”, and SCIE contrasts reablement’s doing-with against traditional care’s doing-for.

Boundary. The components carry their citations; the exact token matrix — six cues by four assistance rungs, scored concurrently — is WellDash’s own, stated plainly as ours-to-test. It is validated continuously against each person’s accumulated record, not by a one-off norming study.
Pillar 2 · Equivalence NICE NG11

The easier ask: same wage, not same shape

Functional communication training (Carr & Durand 1985) is among the best-evidenced behavioural interventions, and it is a recommendation of NICE NG11: develop an alternative behaviour that achieves the same function. In WellDash the replacement is a first-class plan step, not a note in a document.

  • The ask is taught as its own step (behaviour_response) with strategy teach_fct, paired with reinforce_success — honour the ask the moment it lands on first uses, or the teaching loop breaks. Thin the acknowledgement as the ask becomes habitual.
  • The height of the arc is the ask the person starts themselves, unprompted — visible in the live record as the cue rung falling to none on dated rows for the taught step.
  • The law: equivalence means the same wage, not the same shape. The record checks it as same occasion, different form, same settle — the index holds each form’s settle record under the same function, so an equivalence claim can be examined against the person’s own rows rather than believed.
  • At the pre-verbal end, the lineage runs through Intensive Interaction (Nind & Hewett): the ask does not have to be a word to earn its wage.
  • Behind the palette sits an evidence-attached strategy library — forty authored entries covering ten functions across four kinds of response, each carrying its example, its non-example and its citations, so the same equivalents can be offered consistently across shifts rather than reinvented on each one.
Direction. Two pieces here are designed rather than shipped: a dedicated dated self-initiation mark, so “the first time he asked unprompted” is a typed event rather than an inference from the cue rung; and serving the strategy library’s rows directly into the authoring picker at the moment a step is written. Both are described in full in the easier ask.
Boundaries. Not every behaviour has a teachable equivalent, and the body-first override outranks equivalence work whenever anything is unexplained. An equivalence claim is clinical judgement the record supports — never machine output.
Pillar 3 · Context

The context pieces: an ABC whose A can be counted

An ABC record is only as useful as its antecedent limb, and in most software the A is prose. In WellDash the context is typed at capture, so it computes.

  • Setting events are recorded as typed tokens across five classes — physiological, sensory and environmental, social and relational, routine and temporal, emotional — beside typed physical rule-outs.
  • Each episode carries a ctx_key — its first setting token — and the empty value is itself meaningful: a recorded “nothing unusual” is information, not absence.
  • Three body clocks run continuously from the person’s own recorded numbers — night_wakings, days_since_last_movement, refusal_day_count — and annotate every episode when it is read. The bands on those clocks are declared reading conventions on the person’s own history, never clinical thresholds, and never part of a key: annotation is joined at read.
  • The differentiation law: which background state loads which behaviour — whether a shut bowel loads tapping while broken sleep loads hitting out — is learned from the person’s own co-occurrence counts, never decided by a taxonomy. Distal and proximate layers are recorded for honesty but are never load-bearing.
  • Flag, never force: when the vocabulary has no token for what the carer said, the gap is flagged so the vocabulary can grow. Nothing is squeezed into a wrong token or abandoned to prose.
Direction. A set of ten named antecedent pieces — slept-badly, unwarned-transition, demand-placed and their kin, with the body pieces carrying their band automatically — is designed so that “episodes preceded by X” becomes a deterministic join on typed data. Designed, not yet shipped.
Pillar 4 · Body first NHS LeDeR

Body first: the safety spine the mortality reviews demanded

People with learning disabilities die avoidably when bodily illness is read as behaviour — diagnostic overshadowing is the standing finding of CIPOLD (2013) and the NHS LeDeR programme, and NICE NG11 puts physical causes first. WellDash builds that priority into the record’s structure, not into a training slide.

  • The override: when anything is unexplained, new or out of character, the body question outranks every behavioural reading — body_first in the record. Constipation until proven otherwise.
  • PINCH ME at capture: seven first-pass prompts — pain, infection, nutrition, constipation, hydration, medication, environment — each mapping onto typed causes in a 24-cause differential (rule_out_type). The mapping fails closed: a prompt with no authored mapping is an error, never a guess.
  • The convergence lanes: what happened now, what is different from this person’s usual, and what is known about their life are shown together for a human — never merged by the machine.
  • The dechallenge is the strongest evidence the record holds: treat, then resolve, dated. A synthetic example: laxative → bowels open → the tapping stops. When the same chain has happened before, the record shows it as n-of-n on this person’s own history.
  • A clinician-authored graph of symptom → consideration → disposition triples is used lawfully: as typed vocabulary and as authored disposition edges — human-activated only, with provenance on every row.
  • Escalation is an authored, human-activated edge armed with the evidence. The machine never routes an emergency call.
  • And medication is part of the same record: STOMP is the standing warrant that a chemical response is never the answer to a body problem.
Boundary. LeDeR’s themes are epidemiological: they shape what the clocks and rule-outs watch for, and a casebook built from real published mortality and safeguarding reviews was used to stress-test this machinery — but population findings never become per-person prediction.
The spine

The function index: what the record computes

The four pillars share one engine. Every episode is recorded as a transition — what was happening before, what was done, what happened after — and the record keeps how the person settled afterwards, read against their own baseline. The person’s history is the control; there is no population norm anywhere in the loop.

  • Evidence is filed by what the behaviour was for, and by the exact response configuration that was used — never pooled by what the behaviour looked like. That is the difference between a count and a piece of evidence.
  • Function tokens come from observations only, held in parallel until the person’s own outcomes resolve them. “Unhypothesised” is a real, recorded value — never guessed away, and never inferred backwards from the response used.
  • Responses are ranked by what the record shows settles this person. A tested configuration outranks an untested one; a brand-new plan variant starts unproven and earns its rank only as episodes accumulate. A plan change adds a variant beside the baseline — it never replaces the history the ranking needs.
  • Capture types itself: a carer speaks, and the words become a typed structured row — form, parallel function hypotheses, the four-dial response, who did it, before and after — with the carer’s own words preserved beside the tokens. The evidence was going to be spoken anyway; the record is rich without the carer paying for richness.

The indexing and the ranking are the reason the four pillars are computations here rather than paragraphs in a plan document. How they are computed is ours; what they produce belongs to the practitioner — evidence about one person, with its sources attached, arriving as the work happens rather than being assembled the night before it is needed.

Position

What is different, stated carefully

Four premises, each an objective property of the software rather than an adjective:

  • Capture fidelity is the floor of everything. A dropdown loses the sentence; a form captures what the form designer imagined. Typed narrative from speech captures what the carer actually saw.
  • Teaching already happens — the record just loses it. Staff teach behaviour swaps constantly, informally, brilliantly. The software’s job is to capture where the teaching happened, transfer it to the team as a consistent palette, and re-teach the same swap next shift. Consistency is a palette problem, not a person problem.
  • Evidence for a funding panel is computed or it is assembled by hand. A dated dechallenge, outcomes filed by function, a recorded fade and a proposed plan change carrying its sources arrive as the work happens — not the night before, from notes, at overtime rates.
  • Change management is structural. When change lands as data and the plan visibly re-orders with the reason attached, adoption stops being a training problem and becomes a by-product of use.

In an August 2026 timestamped sweep of UK care-management platforms, UK PBS-specific tools and US ABA platforms, we found no deployed system that indexes behaviour evidence by function, computes functional equivalence from outcomes, or dates the fade of assistance on real-life response configurations. Voice capture itself is commoditising quickly across the sector; the typed grammar and the function index are the parts we found nowhere else.

Boundaries

What the system never does

  • It does not diagnose, and it does not predict. It notices when this person departs from their own baseline and hands a human the evidence.
  • It never places an emergency call. Escalation edges are authored by people and activated by people; the system’s job is to arm the human with the record.
  • It never silently changes a live plan. Repeated outcomes can become a review proposal with its sources attached; only an authorised person can turn a proposal into operational guidance.
  • It never offers a restrictive configuration. The bar is structural — built into what can be served — not a preference setting.
  • It never resolves a function hypothesis by preference or protocol. Hypotheses stay multiple until the person’s own evidence resolves them.
  • Population evidence shapes what is watched, never what is concluded about one person.
  • Every worked example in this article is synthetic. No real person’s care record is quoted, here or anywhere on this site.
Go deeper

One note per pillar, and four beside them

This article is the map. Each pillar has its own note that goes a level further into the mechanism, the evidence and the boundaries — and one note explains where a service actually starts.

FAQ

Questions, answered the way we answer them

What is a behavioural function?

What the behaviour earns for the person — escape, attention, sensory regulation, communication, or a bodily need met. The founding insight of functional analysis (Carr 1977; Iwata and colleagues 1982/1994) is that behaviour works for the person, so support must serve what the behaviour serves.

Why not treat behaviour by how it looks?

Because identical-looking behaviours can serve different functions in the same person — the aggregation correction the research literature established across 1992–2013. Function is the unit of support; grouping behaviours by appearance is a measured, decades-old error.

When is functional assessment done?

Historically, when scheduled — and the report goes stale as the person’s life moves. In WellDash, function-finding is continuous: every episode carries parallel function hypotheses, and the person’s own outcomes resolve them over time.

How do you record fading support?

Each recorded response carries its cue and assistance rung, plus performed_by (person, shared or carer_did_for) and, when hands were on, touch_kind. The fade is the rung falling across dated rows, and the doing-for → shared → person curve computes from the same rows.

What is the difference between guiding and weight-bearing?

Guiding steers the movement; bearing carries the load while the person still moves. Most real hands-on care is both at once, and the record says so — which keeps reablement reporting honest about physical contact.

How does the system know a replacement behaviour is equivalent?

It never asserts equivalence. Equivalence means the same outcome, not the same shape — same occasion, different form, same settle — and that is checked against the person’s own recorded episodes rather than declared by label.

Do you label interventions as less harmful?

No. The ranking orders responses by what the person’s record shows settles them; restrictive configurations are structurally barred from being offered; and the clinical ‘why’ stays with the practitioner and the citations.

How do you tell a trigger from a setting event?

We deliberately do not force that call. The layer is recorded for honesty, and the person’s own co-occurrence counts differentiate which background state loads which behaviour — the record decides, not a taxonomy.

What happens when behaviour is actually pain?

The body-first override outranks every behavioural reading. The system surfaces the co-occurrence evidence — the bowel, sleep and intake clocks, the typed rule-outs, any prior dated dechallenge — so the human call is an informed one.

Does it call 999 automatically?

Never. Escalation is an authored, human-activated step armed with the evidence; the machine never routes an emergency call on its own.

Is your prompt hierarchy validated?

Every component carries its primary citation — the prompt-fading literature, PASS’s assist hierarchy, PCPT-ALF’s concurrent scoring, UK reablement guidance. The exact token set is WellDash’s own, stated plainly as ours-to-test, and it is validated continuously against each person’s accumulated record rather than by a one-off norming study.

How do you use LeDeR?

As the safety lens it is. LeDeR’s themes shape what the clocks and rule-outs watch for, and published reviews were used to stress-test the machinery against known failure patterns. Its limits define ours: epidemiology shapes watches — it never becomes per-person prediction.

See the four pillars working on one synthetic person.

The demonstration shows capture, the typed grammar, the body-first lens and the ranked responses on synthetic records.