Rostering
Schedule visits, allocate carers, manage rotas.
Confirmed: rostering standard.
Part A · Per-system feature inventory
Mark friction (0–5) on the rows that apply and add anything we missed. The pre-filled rows are answers you gave us on Friday. Please correct anything that's wrong.
A.1
Used at Delore Care for: rostering and care planning, industry standard.
Schedule visits, allocate carers, manage rotas.
Confirmed: rostering standard.
Per-service-user care plans.
Confirmed: switched to Birdie.
No need to rate friction for something you don't use.
In-visit notes recorded by carers.
MAR chart at point of care.
Service user risk profiling.
Where each carer's certificates are stored.
Confirmed: training matrix of record.
Carer hours recording.
Confirmed: CSV-uploaded to Employment Hero.
Invoice generation for service users / commissioners.
Confirmed on call.
No need to rate friction for something you don't use.
Standard rostering / care delivery reports.
Field-side care delivery interface.
Programmatic access to Nourish data.
We need to know your package and whether API access has been requested or enabled.
Two-way sync with Birdie.
Confirmed on call: more flows from Nourish to Birdie than the other way.
A.2
Used at Delore Care for: electronic call monitoring, and care planning UI in daily use (you preferred Birdie's care planning over Nourish's).
Geo-verified visit start/end.
Where you actually plan care, per service user.
Confirmed: primary care planning UI.
Carer notes during a visit.
Medication adherence at point of care.
Care notes visible to next-of-kin.
Families currently log in to Birdie for care notes.
Birdie's own rota module.
Confirmed: Nourish is the rostering standard.
No need to rate friction for something you don't use.
Birdie's invoicing module.
Standard Birdie reporting.
Field-side check-in app.
Bidirectional sync.
The most consequential thing we still need to understand. What syncs and what doesn't?
Programmatic access via Birdie's commercial team.
We would need a vendor conversation to scope.
A.3
Used at Delore Care for: HR records and payroll. You confirmed on the call that you are on the tier just below Platinum.
Personal details, contract data, employment history.
Generate and sign employment contracts.
Confirmed: limited to staff. Clients use PandaDoc.
New starter workflow.
UK payroll engine.
Real-time information to HMRC.
Workplace pension scheme.
Hours recording.
Confirmed: Nourish handles this.
No need to rate friction for something you don't use.
Leave requests, approvals, balance tracking.
Reviews, goals, feedback.
Vacancies, candidates, hiring pipeline.
Confirmed: not started using.
No need to rate friction for something you don't use.
DBS submission inside Employment Hero.
Worth comparing with Checks Direct for consolidation.
Confirmed: Checks Direct used instead.
No need to rate friction for something you don't use.
Employee files and certificates.
Internal comms / news for staff.
Raised on the call as possibly substituting for an intranet.
Visual reporting structure.
Native sync to QuickBooks Online.
Worked once, disconnected. Reconnection is a quick win.
Confirmed: worked once, disconnected.
OAuth 2.0 REST API.
Confirmed: tier below Platinum.
No need to rate friction for something you don't use.
A.4
Used at Delore Care for: accounts. You confirmed Online (not Desktop) on the call.
Invoice generation, sending, tracking.
Confirmed.
Match transactions to bank feed.
Accounts payable.
Staff expense submission.
Receive payroll journals.
Confirmed: not flowing from Employment Hero.
Time-on-projects.
Probably not in use given Nourish has time sheets.
UK VAT submission.
Foreign currency invoicing.
P&L, balance sheet, cash flow.
Programmatic access via OAuth 2.0.
This is the most mature API in your stack.
Native connectors to other tools.
Employment Hero connector exists, currently broken at your end.
Native PandaDoc to QuickBooks sync.
Worth confirming whether you have this enabled. Could remove the manual PandaDoc to QBO step.
A.5
Used at Delore Care for: mandatory training delivery. You confirmed on the call that you are on the Foundation tier (lowest of four).
The renewal is approaching. The Foundation-to-Pathway upgrade question is the natural moment to ask Care Tutor whether their API and HR integration land on a tier that makes sense for you.
Standard care-sector e-learning library.
Author your own.
Issued on course completion, per learner.
Confirmed: downloaded by hand and uploaded to Nourish.
Add staff to courses.
Completion rates, expiry tracking.
Bulk-enrol new starters.
A feature you asked for; you were told it was upgrade-only.
Sequenced course bundles.
Sync learners and completions to your HR.
Worth raising with Care Tutor when you discuss the renewal.
Programmatic learner / course management.
Worth asking Care Tutor whether their API is part of Pathway.
A.6
Used at Delore Care for: DBS and right-to-work checks.
Open question
Employment Hero has its own DBS check feature (see A.3). If their offering is comparable, there is a consolidation conversation here. Worth a side-by-side comparison once we understand both sides.
Submit and track enhanced disclosures.
Submit and track standard disclosures.
UK RTW verification.
Subscription-style ongoing monitoring.
Submit multiple at once.
Application status, expiry tracking.
Programmatic submission and status.
We need to know whether your contract includes this.
A.7
Used at Delore Care for: office staff productivity, document management, internal comms in transition. You confirmed Business plan on the call (~£20/user/month, office staff only).
Licensing open question: for the field staff currently on WhatsApp, the Business plan does not scale per-seat. Microsoft 365 Frontline tiers (F1 at around £2.10, F3 at around £6) are designed for non-desk staff and address the data residency and offboarding concerns that come up around WhatsApp at scale. Worth discussing with your IT lead.
Email, calendar.
Productivity suite (desktop and online).
Chat, channels, video calls.
Confirmed: office staff partially adopted, field staff still on WhatsApp.
Document libraries, sites, intranet platform.
Confirmed: meant to be the document source-of-truth.
Personal cloud storage.
Surveys, simple data capture.
Online appointment booking.
Video hosting.
Workflow automation across M365 and external systems.
The integration backbone for SharePoint document routing.
Low-code custom apps.
Internal social network.
Task management.
News, links, internal directories, brand-aligned site.
Raised on the call as a near-term goal that has not yet been built.
A.8
Used at Delore Care for: electronic signatures, particularly for service user contracts and invoicing. You confirmed on the call PandaDoc was in place before Employment Hero.
Reusable contract / invoice templates.
Send for signature, track, complete.
Who opened it, when, signed status.
Dynamic content based on inputs.
Internal approval before sending.
Collect payment alongside signature.
Sync signed invoices to QBO.
Currently a manual drag-and-drop. Worth confirming whether the native connector is in place.
File signed docs into SharePoint folders.
Currently a manual drag-and-drop.
Programmatic document generation and signing.
A.9
Used at Delore Care for: training (a second platform alongside Care Tutor for specific health and safety courses).
We have less public information on this platform. Please correct anything below that is wrong.
Open question
What courses do you take through Health and Safety Group that you cannot or do not take through Care Tutor? If they are duplicative, this is a consolidation candidate.
E-learning courses.
Issued on completion.
Same download-and-upload-to-Nourish routine as Care Tutor.
Add staff.
Completion tracking.
Admin interface.
Sync to Employment Hero or similar.
A.10
Used at Delore Care for: field staff communication and office staff group chats. You confirmed on the call you are gradually moving office staff to Teams and considering moving field staff too.
A current-state acknowledgement. We don't expect a long answer. The moments where WhatsApp earns its place are the useful detail.
That's Part A done.
Part B is where the real value is. It maps each function across all your systems in one view. Duplications and gaps become visible without anyone hunting for them.
Continue to Part B