Deciding to roll out remote care technology in a municipality sounds like a big project. Procurement, technical specs, training, GDPR, budget approval. In practice — if you approach it as a pilot rather than a revolution — you can start within a week with minimal risk and budget.

Step 1: Pilot — 10 seniors, 1 worker, 3 months

Don't start with 200 service users. Start with 10 — and one worker who will own the pilot.

Who to select?

The best pilot candidates are seniors who:

  • Live alone — that's where monitoring adds the most value
  • Have a smartphone — or are open to receiving a simple Android phone
  • Are already supported by social services — the worker knows them and can compare "before and after"
  • Give informed consent — this is a requirement, not a formality

What you need to get started

  • Smartphones: if the senior doesn't have one, a budget Android (Samsung Galaxy A05s, Xiaomi Redmi 13C) costs GBP 80-150. Many councils fund this from existing care budgets or digital inclusion grants
  • App accounts: set up via the admin panel, 5-10 minutes per senior
  • GDPR documents: privacy notice + consent form — Lovivo provides ready-made templates

Installation at the senior's home

The worker visits, installs the app (5 minutes), enables the necessary permissions, and shows the only interaction — the daily wellbeing question with large buttons. From that point, the phone runs on its own.

Tip: combine the installation with a scheduled home visit — no extra trip needed.

Step 2: Daily work with the dashboard

After a week, the worker has a baseline picture of each senior's activity. The caregiver dashboard shows:

Overview — all service users at a glance

  • Green — activity is normal; senior is using their phone, leaving home
  • Amber — minor deviation; fewer calls than usual, shorter active periods
  • Red — no activity for X hours, no contact, sudden drop in indicators

The worker doesn't need to check each senior individually. A glance at the dashboard shows where attention is needed.

Automatic alerts

The system sends a push notification to the worker's phone when:

  • The senior hasn't unlocked their phone for X hours (configurable threshold)
  • No home departure for 2+ days
  • Sudden drop in social contacts
  • Senior hasn't responded to the wellbeing check for 3 days

This means the worker doesn't need to actively monitor — the system tells them when something needs attention.

Weekly reports

Every week the dashboard generates a summary:

  • How many seniors were active vs inactive
  • How many alerts were generated and how quickly they were handled
  • Trends — is senior activity rising, falling, or stable?

This data is invaluable when evaluating the pilot and making the case for expanding the programme.

Step 3: Evaluation and scaling

After 3 months, you have hard data to inform the decision:

What to measure

Metric How to measure Target
Crisis response time From alert to contact with senior < 2 hours
Detected critical situations Times the system flagged a problem that would otherwise have been missed > 0
Senior satisfaction Brief survey after 3 months > 70% positive
Worker satisfaction Does the dashboard improve their workflow? Yes
Time saved Check-in calls avoided > 30% reduction

How to make the budget case

For council decision-makers, the strongest arguments are:

  1. Service user safety — objective data rather than self-reported "I'm fine"
  2. Staff efficiency — the same team covers more seniors without compromising quality
  3. Auditable data — measurable KPIs for elected members and oversight bodies
  4. Low entry cost — a 10-person pilot costs roughly GBP 70-120/month

Scaling up

If the pilot succeeds, expansion is a configuration task — not a new procurement. Adding more seniors takes minutes, not weeks. The dashboard handles 10 to 500 service users with no infrastructure changes.

Ready to plan a pilot in your municipality? Contact us — we'll help select the group, prepare GDPR documents, and run the staff training.