Fixed quote after a free call

Care home incident reporting and follow-up, with nothing missed

Falls, skin damage, medication errors and other incidents are recorded, but follow-up actions, family calls and any required notifications depend on someone pulling it together. We build a workflow that structures incident logs, assigns and chases follow-up actions, prompts the manager when an incident may need a notification to the regulator or authorities and reports themes each month. A typical build costs $1,000 to $2,500 and takes about four weeks.

The problem

Why incident follow-up slips between shifts

An incident at 3am is recorded by the night nurse, and from then on everything depends on handover: has the GP or physician been told, has the family been called, is a body map done, is a review booked, does the regulator need to know?

Notification rules are specific. In England, registered providers must notify the CQC without delay of incidents such as serious injuries, abuse or allegations of abuse and incidents reported to the police. In US nursing homes, the resident, physician and representative must be informed of events such as an accident with injury that may need physician intervention.

What we build

What our care home incident reporting automation includes

Structured incident log

Incidents captured from the care platform or a short form, with type, time, unit and who was involved.

Follow-up actions

Actions such as physician contact, family call, review and care plan update assigned and chased.

Notification prompts

Incidents that match the home's list of notifiable types are flagged to the manager with the relevant form linked.

Manager decision log

The manager records whether a notification was made and why, with a timestamp.

Falls and themes view

Monthly themes by unit, time of day and type for the clinical governance meeting.

Overdue alerts

Any action past its due date escalates to the manager.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Incident logged

    Staff record the incident in the care platform or form.

  2. 02 Automated

    Actions created

    Follow-up actions are created and assigned by incident type.

  3. 03 Automated

    Prompt raised

    Possible notifiable incidents are flagged to the manager with the form linked.

  4. 04 Office or senior review

    Nurse completes actions

    Nurses and seniors complete and record each action.

  5. 05 Registered manager or nurse decides

    Manager decides

    The registered manager decides on notifications, safeguarding referrals and family contact.

How it behaves

How incident follow-up behaves

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

What staff see

  • A short list of actions after each incident
  • Reminders when an action is due

What managers see

  • Possible notifiable incidents flagged with the form linked
  • Overdue actions escalated
  • Monthly themes by unit

What the automation does

  • Creates actions by incident type
  • Raises prompts and records decisions
  • Never contacts regulators or families itself

Edge cases and fallbacks

Incident type unclear
Flagged to the manager for classification.
Action not completed
Escalated to the manager after the due time.
Manager is away
Prompts go to the deputy or on-call manager.
Care platform feed fails
Staff use the backup form and the office is alerted.

Architecture

Incident follow-up and notification prompts at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Incident record Care platform n8n workflow Type rules Follow-up actions Assigned, chased Notify prompt Possible types Nurse or senior Completes actions Manager Decides Decision log Themes, audit
  • Input
  • Logic and services
  • Output
  • People
  • Data

How it flows

  1. 1 An incident is recorded in the care platform or a short form.
  2. 2 Rules by incident type create follow-up actions and flag possible notifiable incidents.
  3. 3 Nurses complete actions; the manager decides on notifications and safeguarding referrals.
  4. 4 Every decision is logged and monthly themes go to the governance meeting.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Incident follow-up & notification prompts project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Incident types, current recording, follow-up practice and notification process.

  2. 02

    Design

    2 to 3 days

    Action templates, notifiable type list agreed with the manager, escalation timing.

  3. 03

    Build

    1 to 2 weeks

    Incident feed, actions, prompts, decision log and themes report.

  4. 04

    Shadow run

    About 1 week

    Prompts run beside the current process while the manager checks each one.

  5. 05

    Launch

    1 to 2 days

    Go live and train nurses and seniors.

  6. 06

    Support

    Ongoing

    Rule changes when guidance or the home's policy changes.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n Care platform incident records (API or export) Short incident form where no feed exists Microsoft Lists, Airtable or Sheets for the action tracker Teams, Slack or email alerts Monthly PDF themes report

Cost estimate

What it costs, line by line.

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

    Time with the registered manager and office team, wording, data flows and a written specification.

    $200 – $400

  • Build

    The n8n workflow, rules, drafting step where useful, logging and error handling.

    $500 – $1,300

  • Integrations

    Care platform, rota or CRM access, messaging and alert channels.

    $150 – $400

  • Testing and shadow run

    Acceptance tests and a parallel run while the team keeps its current process.

    $100 – $250

  • Launch and training

    Go-live, short staff training and a run book.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Notifications themselves are submitted by the manager through the regulator's or state's own channel.

Monthly running costs you pay directly

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

  • 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.
  • Tracker storage: Microsoft 365, Airtable or Google Workspace plans you already have.

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

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

England: CQC notifications

Regulation 18 requires registered persons to notify the CQC without delay of specified incidents, including serious injury, abuse or allegations of abuse, and incidents reported to or investigated by the police. General information, not legal advice.

Source: www.legislation.gov.uk

US: notification of changes

42 CFR 483.10(g)(14) requires nursing homes to immediately inform the resident, consult the physician and notify the representative after events such as an injury-causing accident or a significant decline.

Source: www.law.cornell.edu

People decide, not prompts

The workflow flags possible notifiable incidents; the manager decides and submits, and state rules for assisted living vary, so the type list is set per home.

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.

FAQ

Incident follow-up & notification prompts questions, answered.

No. It flags incidents that may need one and links the right form. The registered manager decides and submits.

Yes, where the platform offers an API or export. Otherwise a short form captures the incident and feeds the same workflow.

Falls get a standard action set agreed with your clinical lead, and the monthly themes view shows patterns by unit and time of day.

Yes. Assisted living is regulated by each state, so we set the notifiable type list and actions to your state's rules and your policy.

Only the people who need it, through the access your care platform and tracker already enforce.

Actions completed on time, incidents with family contact recorded, notification decisions logged and themes over time.

Free 20-minute call

Want this 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