Case Study

Case Study: Care Home Admissions & Staffing Automation

We built a connected set of automations for a residential and nursing care home: an admissions pipeline for family enquiries, short-notice rota gap filling, a live staff training matrix, family updates with online visit booking and incident follow-up with notification prompts. The manager now runs the home from one set of lists, and caregivers take fewer calls during rounds.

Home type
Residential and nursing care home
Team involved
Registered manager, deputy manager, nurses, senior caregivers, office administrator
Systems connected
Care platform, rota tool, CRM, phone system, Twilio, n8n
Delivery
Scrum, 1-week sprints, about 8 weeks to full launch

The challenge

Where the practice started

Family enquiries were written in a notebook by whoever answered the phone. Some waited a day for a call back, and nobody could say which sources led to move-ins.

Sickness calls started a chain of texts and agency phone calls run by the shift lead, who was also running the floor.

The training matrix was a spreadsheet updated before inspections. Agency profiles arrived by email and were checked in a rush.

Families called during medication rounds for updates and visits, and incident follow-up depended on handover notes and memory.

Goals

What the project had to change

  • Every family enquiry gets a reply and tour options the same day.
  • Short-notice gaps are offered fairly and quickly, with the manager approving each fill.
  • Training and recruitment records are always current and inspection-ready.
  • Families get timely updates written by staff and can book visits online.
  • Every incident has follow-up actions and a recorded notification decision.

What we built

What we built, as one connected system.

01

Admissions pipeline

We connected calls, web forms, directory leads and discharge referrals to one CRM pipeline with tour booking, gentle follow-ups, a waiting list and a weekly occupancy report.

Service details
02

Rota gap filling

Open shifts are offered to suitable bank staff in an agreed order, with training checks, agency drafts at the cut-off and one-tap manager approval.

Service details
03

Training matrix

A live matrix from HR and training records, expiry reminders, new-starter checklists, agency profile checks and an evidence pack on request.

Service details
04

Family updates and visits

Family messages are sorted, routine updates drafted for seniors to approve, visits booked online and concerns routed to the manager.

Service details
05

Incident follow-up

Incidents create follow-up actions by type, possible notifiable incidents are flagged to the manager, and decisions are logged with monthly themes.

Service details

Architecture

How the home's workflows connect

Family enquiries Calls, web, refs Rota tool Open shifts Care platform Notes, incidents n8n Five workflows Drafting step Family updates CRM and matrix Pipeline, training Texts and emails Twilio, email Office and seniors Approve, verify Manager Decides Logs and reports Weekly summary
  • Input
  • Logic and services
  • AI step
  • Data
  • Output
  • People

How it flows

  1. 1 Family enquiries, open shifts and care platform records feed one n8n instance.
  2. 2 Five workflows update the CRM and training matrix, send offers and reminders, and draft family updates.
  3. 3 Seniors approve updates, the office verifies records and the manager decides fills, admissions and notifications.
  4. 4 Every step is logged and a weekly summary shows the measures the home agreed to track.

How it behaves

How the system behaves day to day

What each person sees and what runs in the background, including what happens when something goes wrong.

What families see

  • A same-day reply and tour options when they enquire
  • Updates written by staff they know
  • Online visit booking with reminders

What staff see

  • Shift offers they can accept with one tap
  • Reminders before training expires
  • Short action lists after incidents

What the automation does

  • Captures, offers, reminds and chases on schedule
  • Checks sharing rules and training before acting
  • Logs every step and alerts the manager if anything fails

Edge cases and fallbacks

An urgent discharge referral arrives
The admissions lead gets an immediate task for a same-day call.
Nobody accepts an open shift
The manager gets the agency draft and the gap stays visible.
A family message hints at a safeguarding concern
It goes straight to the manager under the safeguarding process.
An incident may be notifiable
The manager is prompted and records the decision; nothing is submitted automatically.
The care platform or n8n is down
Backup forms and phone lists are used and the office is alerted.

Integrations

What we connected

All integrations

PointClickCare

Care platform (US and Canada)

Resident census, incidents and notes for family updates and incident follow-up.

PointClickCare developer programme: Cures Act FHIR APIs, or proprietary APIs through its Marketplace partner route, confirmed per project.

WelcomeHome

Senior living CRM

Enquiries, tours and move-in pipeline.

WelcomeHome's API and listed integrations, confirmed per project.

Deputy

Rota and workforce

Open shifts, availability and approvals.

Deputy API.

Twilio

SMS and voice

Shift offers, family messages and the assistant's phone line.

Twilio Messaging and Voice APIs, with Twilio's BAA where resident data is involved.

Google Business Profile

Local search

Listing details and review requests to families.

Google Business Profile settings and APIs.

n8n

Automation platform

Runs the workflows, self-hosted or on n8n Cloud.

Your own n8n instance; we hand over every workflow.

How we delivered it

Week by week, one workflow at a time.

Each workflow went live on its own after a shadow run and a sprint demo, so the team got used to one change before the next.

Delivery timeline

Typical time to launch: about 8 weeks, then support

  1. 01

    Discovery

    Week 1

    We spent time with the manager, office and night staff, mapped enquiries, rotas, training, family contact and incidents, and the home signed vendor agreements.

  2. 02

    Design and access

    Week 2

    Wording approved by the manager, pipeline stages, offer order, sharing rules, notifiable type list, platform and rota access.

  3. 03

    Sprint 1: admissions

    Week 3

    Built and shadow-ran the enquiry pipeline and tour booking; demo and sign-off.

  4. 04

    Sprint 2: rota gaps

    Week 4

    The pipeline went live. Built shift offers, training checks and agency drafts.

  5. 05

    Sprint 3: training matrix

    Week 5

    Gap filling went live for one unit. Built the matrix, reminders and checklists.

  6. 06

    Sprint 4: families

    Week 6

    The matrix replaced the spreadsheet. Built message sorting, drafts and visit booking.

  7. 07

    Sprint 5: incidents

    Week 7

    Visit booking went live. Built incident actions, prompts and the decision log.

  8. 08

    UAT and handover

    Week 8

    Staff ran acceptance tests on every workflow, then we switched everything on, handed over the run book and trained the team.

  9. 09

    Support

    Ongoing

    Weekly check-ins during stabilisation, then monthly care.

Who does what

What the team does, and what automation does.

Automation does

  • Captures enquiries and books tours
  • Offers open shifts to suitable staff in order
  • Keeps the training matrix current and sends reminders
  • Sorts family messages and drafts routine updates
  • Creates incident actions and raises notification prompts

The team does

  • Call families and run tours
  • Confirm skill mix and send agency requests
  • Verify recruitment documents
  • Approve and send family updates
  • Complete incident follow-up actions

Registered manager or nurse decides

  • Decides whether the home can meet a person's needs
  • Approves every shift fill and staffing level
  • Decides on regulator notifications and safeguarding referrals
  • Makes calls to families about changes in condition

Compliance handled

Privacy, consent and safety, built in.

Notifications stay with the manager

Possible notifiable incidents are flagged; the registered manager decides and submits.

Source: www.legislation.gov.uk

Recruitment records

The checklist follows the Schedule 3 information for each person employed.

Source: www.legislation.gov.uk

Sharing with families

Contacts and sharing preferences are checked before any update is drafted.

Source: www.law.cornell.edu

Health data minimised

Drafts use only the notes each update needs and processors are under contract.

Source: gdpr-info.eu

No automated news of changes

Accidents and changes in condition are communicated by nurses or the manager, never by the workflow.

Outcomes

What changed for the practice

  • Family enquiries get a reply and tour options the same day.
  • Short-notice gaps are offered within minutes, and the manager approves each fill from their phone.
  • The training matrix is current every morning instead of before inspections.
  • Caregivers take fewer family calls during rounds, and families book visits online.
  • Every incident has actions, owners and a recorded notification decision.

What we track

The measures the practice watches.

Enquiry response

Time to first reply and tours booked per enquiry.

Admissions

Move-ins by source and days from enquiry to move-in.

Gap filling

Time from gap to fill and share filled by bank staff.

Training in date

Share of staff fully in date each month.

Incident actions

Actions completed on time and decisions recorded.

Cost estimate

What a project like this costs

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Process mapping, data flows, wording and the backlog for all five workflows.

    $1,000 – $2,000

  • Admissions pipeline module

    Sources, stages, tours, follow-ups and report.

    $700 – $1,600

  • Rota gap module

    Offers, training checks, agency drafts and approvals.

    $800 – $1,900

  • Training matrix module

    Matrix, reminders, checklists and evidence pack.

    $700 – $1,700

  • Family updates module

    Sorting, sharing checks, drafts and visit booking.

    $700 – $1,800

  • Incident module

    Actions, prompts, decision log and themes.

    $600 – $1,600

  • Integrations

    Care platform, rota tool, CRM and Twilio connections.

    $200 – $500

  • Testing, UAT and launch

    QA, acceptance testing, launch and training.

    $300 – $1,400

  • Total project estimate

    $5,000 – $12,500

Optional monthly care after launch is quoted with your proposal. Typical range for this scope: five workflows at our fixed per-workflow range. Every home gets its own fixed quote after a free call.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • Twilio SMS (US): About $0.0083 per message segment each way plus carrier fees (Twilio's published US pricing); other countries are priced per destination.
  • n8n: Free self-hosted Community edition on the home's or group's server, or n8n Cloud from about €20 a month (Starter) or €50 (Pro), billed annually.
  • CRM and rota tool: The vendors' own plans.
  • AI usage: Pay-per-use model fees for drafts, usually small at care home volumes.

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

Free 20-minute call

Want this built for your care home?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call