The chasing, the reminders and the filing, handled around you.
Most of what goes wrong in a service is not a failure of care, it is a handover nobody wrote down and a deadline nobody was reminded of. ELSA carries the work around the work: tasks with owners and dates, a calendar that matches the one you already use, and alerts that arrive once rather than five times.
What this replaces today
- A task agreed in a meeting, written on a whiteboard, and remembered by nobody on Thursday.
- Two calendars, the one in Outlook and the one in the care system, that disagree about when the review is.
- Documents saved to somebody's desktop because putting them in the shared drive was three more clicks.
- Either no reminders at all, or so many that everybody has learned to ignore them.
How it works
Work becomes a task with an owner
Ten categories, each prefilling a sensible title and notes so a task takes seconds rather than a paragraph: policy generation, document review, bid preparation, compliance reminders and the rest. A task created without an assignee goes to whoever created it rather than quietly belonging to nobody.
It lands where your team already works
Connect Microsoft or Google and ELSA writes to the calendar you already keep, saves to the drive you already use, and drafts into the mailbox you already read. Nothing asks your staff to check a second place.
You are told once, at the right time
Overdue reviews, approaching deadlines and records needing attention all surface in one place. Urgent things email immediately; everything else arrives in a single digest at seven in the morning.
What you get
ELSA can raise the task itself
Ask it to chase something and it creates the task, categorises it and assigns it, rather than telling you what you should go and do. A category it does not recognise is dropped rather than stored, so the list cannot fill with invented types.
Microsoft, properly
Outlook mail and calendar, OneDrive, Word, Teams and SharePoint are each connected separately, so you grant only what you want used. Teams meeting transcripts need your tenant administrator's consent, which is stated up front rather than discovered halfway through.
Google, properly
Drive, Docs, Sheets, Forms, Gmail and Calendar. A policy exported to Google Docs carries your registered name and address in a real page footer, and that footer follows it into the PDF and Word exports too.
One notification system, not two
Care plan reviews, policy reviews, task deadlines, tender dates, social value milestones and supported living records all feed the same bell, and each person chooses which of those they want to hear about.
Reports you can hand over
Activity across the service, filtered by date, exportable as CSV or PDF for a board paper, a commissioner or a quality meeting.
A daily summary in Teams
One card each morning into the channel your managers already have open, rather than another dashboard somebody has to remember to open.
What stops it going wrong
An alert fires once
Every notification carries a key that stops the same one being raised twice, with monthly alerts deliberately keyed to re-fire each month. An alert emailed urgently today cannot reappear in tomorrow's digest.
The digest is one email, not forty
Only genuinely urgent items email on the spot. Everything else waits for the morning digest. A system that sends eight emails a minute apart is one people filter away, and then the urgent one goes with it.
A connection covers only what you connected
ELSA reads the services you granted and nothing else: no access to mail, files or meetings outside them. Connecting is owner-level, so a member of staff cannot attach your Microsoft tenancy on your behalf.
Nothing is filed without you
ELSA drafts emails rather than sending them, and proposes calendar entries rather than committing them. The last click stays yours.
Who it is for
Every plan
For registered managers and administrators: the people who spend their week making sure things that were agreed actually happened.
Integrations are optional. Tasks, the calendar and notifications all work without connecting anything; connecting simply stops your team keeping the same information in two places.