The person is not a risk profile.
Relationships, sensory experiences, communication, identity, health, goals and choices belong in the care model because they shape what support means.
Why WellDash
Care, connected in the moment.
WellDash helps teams use the approved plan, connect what happens next and build person-centred evidence as care is delivered. “Dash” means care information in motion, not a dashboard inspected after the event.
The north star
The approved plan, useful in the moment.
Ordinary care becomes useful information that can improve the plan. Everything else supports that loop.
The value is in keeping person-specific detail connected.
Moment, person, plan step, phase, setting event, action, assistance and outcome stay distinct enough to review safely.
A map is not a GPS.
Frameworks and plans are vital, but staff need the relevant approved instruction when a particular departure from baseline occurs.
AI drafts and structures. People decide.
The care worker owns what they observed. The provider owns policy. The authorised practitioner owns plan approval. The person’s wishes remain central.
One capture should have many consequences.
The same ratified moment can support continuity, an action, a review, family participation and assurance without becoming five contradictory copies.
The system should help a team act earlier, more precisely and less restrictively by turning what they learn into useful, reusable care information.What WellDash is designed to support
Important distinctions we preserve
Useful care software should keep different responsibilities clear.
Many unsafe shortcuts begin by turning two different responsibilities into one convenient output.
A record of what happened does not silently change the plan.
Frontline evidence can create a review proposal. Only an authorised role can promote it into guidance.
Retrieving an approved response is not autonomous care.
The worker retains professional responsibility, judgement and the duty to escalate when the plan does not fit.
A pattern is a question before it is an answer.
Cross-thread views can reveal relationships worth clinical review without turning retrospective association into diagnosis.
Participation does not require indiscriminate access.
Consent, capacity, relationship, purpose and the person’s own wishes shape each permissioned projection.
Every restriction needs person-specific context.
Purpose, implementation, effect, objection or acceptance, authority and review should remain visible.
Working proof should be labelled honestly.
The current frontend is an interactive product demonstration. Production identity, security, live integrations and assurance remain delivery work.
The product test
If it creates another place to document, it has missed the point.
Care workers get one natural entry. The complexity belongs in the hidden architecture and the governed views that follow.
1frontline care entryMany useful outcomes
Build from the care
Help us test the loop against real practice.
We are looking for conversations with providers, practitioners, care workers, people and families who can tell us what would help, confuse or fail in real care.