This template applies the four-block method — THE THINGS, THE LINKS, THE STATES, THE NUMBERS — to a small home-care agency. It's filled in for a team of eight carers: the example shows how to describe the visit mechanics, from the weekly schedule to tomorrow morning's replacement, without ever describing a screen.
The trade rests on one constraint: a visit without a carer isn't a delay, it's an elderly person without help that day. The STATES block therefore distinguishes "planned", "done" and "to cover" — and the NUMBERS block puts the replacement alert first.
Filled with your vocabulary, this text briefs a developer — or is submitted as-is to Blueprint Maker, which turns it into an application plan you validate, then a generated application: database, screens, dashboard and demo data.
The template to copy
My business: home-care service, eight carers, one area manager running the schedule. THINGS tracked: - Clients (name, address, family contact, specifics — key, door code, dog) - Carers (name, phone, available days) - Visits (client, carer, day, time, duration, nature — cleaning, meals, companionship) - Absences (carer, dates, reason) - Monthly hours (carer, month, total done) LINKS: - A visit links a client and a carer. - A carer's absence turns her visits "to cover". - Monthly hours compute from completed visits. STATES of a visit: planned, done, cancelled by the client, to cover. NUMBERS to see every morning: - Today's visits per carer - "To cover" visits without a solution - Hours done per carer this month - Clients with no visit planned over 7 days
Adapting this template to your agency
- Replacement: it's the scenario that justifies the tool. A recorded absence flips all affected visits "to cover" — the morning list becomes your action plan, not a memory reconstruction.
- Home specifics (key at the neighbour's, door code, habits): note them on the client — that's what lets a substitute deliver a proper visit first time.
- Monthly hours: the per-carer total feeds payroll preparation and schedule fairness — computed from completed visits, never typed separately.
- Recurrence: describe your visits as a weekly pattern (Monday 9 am at Mrs A's) — weeks generate from that model and adjust by exception.
- Regulatory tele-monitoring and funder invoicing stay on dedicated tools: this register is your internal coordination — the code being exportable, a developer can connect the rest if needed.