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

Transparent platform. Editable assumptions.

Pay for the person-specific care platform. Enter expected AI usage separately. Build the operational case from your own workforce, workflows and measured pilot data.

£7.50 platform feeAI usage separateNo hidden time assumptionsEvery formula visible

The platform is the shared care foundation. AI usage stays visible.

The platform connects person-specific plans, identity, permissions, structured records, provenance, sign-off, audit and useful views for each role.

Visible and controllable.

Usage varies with capture volume, model choice, context size and the workflows a provider enables. Enter an expected amount so the business case reflects your own operating model.

  • Measured separately from the platform fee
  • Model and runtime assumptions remain inspectable
  • Pilot usage should replace estimates before procurement
  • Actual usage should be reviewed before any scale decision

Build a case care teams can challenge.

Open only the workflows relevant to you. The defaults are illustrative starting assumptions, including 20 seconds to capture, 60 seconds to structure and 10 seconds to review.

Open each part of the workflow.

Every default is editable. Use observed workflow data before presenting the result as a business case.

Organisation and pricePeople supported, operating days and visible model usage
Formula
Annual cost = people × 12 × (£7.50 platform + entered AI usage)
AI usage is set to £0 until you enter an estimate; replace it with observed pilot usage before relying on the result.
Frontline captureCurrent note time compared with speak, structure and confirm
Formula and current result
WellDash flow = (20s + 60s + 10s) ÷ 60 = 1.5 minutes
Eligible annual records = people × records/day × care days × eligible %
Returned time = max(0, current minutes − WellDash flow) × eligible records
Current model: 2,920 hours · £37,960
Manager reconstructionSearching, collating and rewriting daily evidence
What belongs here?
Include time spent searching daily notes, assembling routine reports, checking handover evidence and rewriting the same source material. Do not include work that remains a necessary professional judgement.
Formula and current result
people × annual hours/person × reducible % × manager hourly cost
Current model: 180 hours · £3,600
Reviews and plan upkeepEvidence search, separate documents and controlled rewriting
Boundary
This model values reduced search and duplicate rewriting only. It does not assume less professional thinking, fewer person-centred conversations or automatic approval of plan changes.
Formula and current result
Review return = people × reviews × hours × reducible %
Plan return = people × other annual upkeep × reducible %
Current model: 350 hours · £14,000
Incident and governance assemblySource-bundle preparation, not investigation avoidance
Boundary
This includes assembling timestamps, linked observations, actions, notifications and review evidence. It does not value avoiding safeguarding work, candour, investigation or statutory notification duties.
Formula and current result
Annual incidents = (people ÷ 100) × incidents/month × 12
Return = incidents × assembly hours × reducible % × manager rate
Current model: 27 hours · £540

A pilot should turn assumptions into evidence.

Some value is cashable. Some is released capacity. Some is improved evidence quality. They should not be collapsed into one inflated saving.

01 · Baseline

Observe the current workflow

Sample note time, searching, report preparation, review evidence gathering and incident assembly using consistent definitions.

02 · Instrument

Measure the new loop

Record capture time, processing wait, adjustment time, successful ratification, repeat entry and actual model usage.

03 · Separate

Cash, capacity and quality

Label reduced paid hours separately from time returned to care, better traceability and risk that was made visible.

04 · Decide

Use observed adoption

Replace eligible-record percentages and reduction assumptions with actual site-level results before scaling.

Use your plans, your staff and your numbers.

The useful business case is the one your team can reproduce and challenge.