Care App for Spitex Switzerland: 9 Features to Test

Quick answer: Which Spitex app is right for a Swiss team?

A Spitex app in Switzerland should connect operational workforce processes from availability to payroll export. The essentials are qualifications, assignment and shift planning, an intuitive employee app, notifications, mobile time tracking, digital confirmations and employee self-service.

job.rocks is a strong fit for Spitex organisations that want to manage these workforce operations centrally. It does not automatically optimise driving routes, and it does not replace clinical care documentation, the patient record or health-insurance billing. Those functions remain in specialised care and billing systems.

Decision table: Which type of solution do you need?

The practical rule is simple: do not buy a supposed all-in-one system before checking its boundaries. A reliable connection between workforce operations and specialist care software is often better than an overloaded application that handles neither side well.

10-minute field test: Does the mobile care app work for Spitex?

Test the app with a planner and a care professional during a simulated last-minute absence. Both sides should always see the same confirmed status.

The test passes when a change completes the full workflow without a phone chain: selection → mobile invitation → confirmation → time entry → review. Also test the essential views on iPhone and Android without zooming or navigating wide tables.

Why Excel, phone calls and private chats fail during a normal day

A spreadsheet can show a rota, but it rarely reflects the full situation at 06:45 when an employee reports sick. The planner must establish who is actually available, who has the required qualification, which assignment is affected and whether the replacement has received the change. If availability sits in one file, qualifications in another and confirmations in a chat, every answer must be reconstructed by hand. Copies are sent, cells are overwritten and nobody knows with certainty which version is current.

Phone calls create a second bottleneck. The first suitable person may not answer, so the office works down a list while other changes arrive. A verbal agreement then has to be entered into the plan and communicated again. Paper notes and messages make the process look flexible, but they move the reconciliation work to the evening: missing working times, unclear breaks, an unconfirmed reassignment or a supplement without context.

The effects differ by workplace. In the office, planners lose time searching, calling, copying and checking. Team leaders have little overview of open responses, while payroll preparation receives avoidable corrections. In the field, employees may start with an obsolete screenshot, overlook a change or call the office because they cannot see the latest operational details. Neither side lacks commitment; the process lacks one controlled source for workforce information.

A useful app therefore closes the loop: an employee submits availability, the planner assigns a qualified person, the change reaches the employee, working time is recorded and deviations are reviewed. It does not turn job.rocks into a care system. Automatic route optimisation, patient records, clinical care documentation and insurer billing remain outside job.rocks and belong in the relevant specialist applications.

Swiss privacy, access and secure operational communication

Swiss organisations should turn broad promises such as “data-protection compliant” into concrete operating questions. Which roles can see employee contact data, contracts, availability and assignment details? Can a planner, team leader, payroll administrator and employee each receive only the access needed for their task? Who grants and removes rights when someone changes team or leaves? Are important actions traceable, and how are exported files controlled once they leave the platform?

Devices deserve the same attention. Decide whether the organisation supplies managed phones or allows private devices, which screen lock and update rules apply, and how access is revoked after loss or theft. Test session expiry, sign-out and the offboarding process instead of relying on a policy document. Data minimisation matters too: the employee app should expose only the operational information required for the assignment. Patient records and clinical care documentation should remain in the designated care system rather than being copied into workforce messages.

Secure communication is a process, not simply a chat feature. Define which operational changes may be sent through the employee app, who may address a group and when an acknowledgement is required. Avoid sending sensitive information through private messengers, SMS chains or screenshots. A sick-call replacement can be communicated with assignment time, location and workforce instructions while clinical content stays in the clinical system. This separation gives employees a clear channel and reduces uncontrolled copies.

Ask the vendor where data is processed, which subcontractors are involved, what contractual safeguards apply, how backups and deletion work and what support personnel can access. Also ask for an example of a controlled export and an access report. The aim is not a generic legal badge but a defensible combination of roles, devices, procedures and contracts under Swiss requirements.

9 essential features for Spitex workforce operations

1. Capture availability centrally

Part-time schedules, preferred working times, absences and last-minute changes need one current source. Employees should be able to submit availability themselves while planners retain control. This removes phone chains and outdated spreadsheets from the start of the process.

2. Consider qualifications in every assignment

An open time slot does not make someone suitable for a visit. Store training, skills, permits and internal approvals, and display them during planning. This reduces unsuitable assignments and speeds up replacement searches.

3. Plan assignments and shifts in one view

Good Spitex staff planning connects demand, person, time, location and qualification. Recurring shifts, open assignments and urgent replacements should be manageable without a parallel spreadsheet. job.rocks supports this allocation, but it does not automatically optimise routes.

4. Give employees a mobile daily overview

The employee app should show planned shifts, operational assignment details and changes clearly. Everyone works from the latest plan and calls the office less often. Sensitive clinical and patient information should continue to be handled by the designated care system.

5. Deliver changes and notifications reliably

Speed matters when somebody calls in sick. Planners should be able to communicate open assignments, send changes and follow responses. A defined operational channel is more reliable than information scattered across private chats.

6. Track working time on mobile devices

Employees should record start, end and breaks directly on mobile. A time-tracking app for employees links actual time to the planned assignment and makes deviations reviewable. It records working time; it is not a clinical proof-of-service system.

7. Handle contracts and confirmations digitally

Digital assignment confirmations, agreements and contracts reduce administrative work. Clear versions, traceable acceptance and controlled access matter. The organisation should separately determine which documents require a specific form of legally valid signature.

8. Enable employee self-service

Where appropriate, employees should maintain profiles, availability, documents and responses themselves. Self-service reduces administrative effort when responsibilities and approval rules are explicit.

9. Simplify payroll preparation and exports

Approved working time and supplements should pass to payroll in a structured format. job.rocks supports payroll preparation and exports; final payroll accounting and insurer billing take place in the connected target systems.

What job.rocks covers – and what remains separate

This separation is deliberate. job.rocks is positioned as an operational workforce solution: schedule the right qualified person at the right time, keep them informed and capture their working time correctly.

Check data flows and interfaces before selecting a vendor

A polished mobile screen says little about the complete process. Draw a simple data-flow map before the demo: employee master data and qualifications enter the workforce platform; availability and absences feed planning; assignments reach the employee app; recorded working time returns for review; approved values leave in a defined format for payroll preparation. Alongside that flow, the care system retains patient records, clinical care documentation and insurer billing. A routing product, if used, retains automatic route optimisation.

For every handoff, name the source, owner, frequency, format and error process. Ask whether an interface is real-time, scheduled or a manual export. What happens when an employee identifier is missing, a correction arrives after approval or the target system rejects a row? Can the organisation retrieve its data in a usable format, and are exports logged and access-controlled? “We have an API” is not an answer until the vendor demonstrates the required fields, authentication, monitoring and responsibility for maintenance.

Avoid copying all data between every system. Exchange only what the target process needs and decide which application is authoritative for each field. Duplicate ownership creates silent conflicts: a qualification updated in one place but not another can lead planners to trust stale information. Reconcile totals and exceptions during the pilot, and have both the vendor and the internal process owner sign off the handoff.

Test vendors with real work, not a presentation

Give each shortlisted vendor the same scenario and let the people who will use the system operate it. Start with a part-time employee changing availability, then report a sickness shortly before the first assignment. Ask a planner to identify eligible replacements, assign one, send the update and see the response. Let a field employee open the changed day, record start, end and break, and flag a working-time deviation. Finally, let an administrator review the deviation and produce a payroll-preparation export.

Add friction deliberately: poor connectivity, an expired qualification, two employees with similar names, a missed notification, a lost-device report and a correction after approval. Measure clicks and elapsed time, but also note uncertainty: when did the tester need help, switch to a spreadsheet or call the vendor? Confirm accessibility on the actual phone models and browsers your workforce uses. Ask to see permissions from several roles rather than through an all-powerful demo account.

Use a scorecard with weighted criteria: everyday usability, exception handling, permissions and security, data exchange, implementation effort, support and total cost. Record evidence and open questions. Reference calls with comparable Swiss organisations can validate support quality, but they do not replace your own test. The winning product should complete the target workflow cleanly while respecting boundaries—not merely offer the longest feature list.

Implementation checklist for Spitex organisations

1. Define the target workflow: Decide whether to launch availability, planning, time tracking or the complete process first.
2. Document system boundaries: Specify which data belongs in job.rocks and which remains in the care or billing system.
3. Clean master data: Review employees, roles, qualifications, locations and contract information.
4. Design permissions: Planners, team leaders, administrators and employees need different access.
5. Test real exceptions: Simulate sickness, urgent replacement, additional time and a missing confirmation.
6. Verify exports: Test the payroll-preparation format before the pilot begins.
7. Choose a realistic pilot: Include ordinary part-time and last-minute changes, not only the easiest workflow.
8. Measure success: Compare calls, planning time, missing entries and corrections before and after launch.

From implementation to stable operation

Treat implementation as an operating change, not an IT installation. A small core team should include a planner with decision authority, a representative from the field, an administrator responsible for working-time review and payroll preparation, and a sponsor who can resolve priorities. The team first writes the target process on one page: who maintains availability and qualifications, who may reassign work, how an employee confirms a change, when time is complete, who reviews deviations and how approved data moves onward.

Clean data before configuration. Remove duplicate employee profiles, align location names, check contracts and qualification validity, and assign ownership for future updates. Do not migrate every historical spreadsheet merely because it exists. Import a sample early, inspect errors and repeat the migration so that go-live is not the first full rehearsal.

Training should be role-based and practical. Planners practise sickness and replacement; employees practise receiving a change and recording working time; administrators practise corrections and exports; team leaders practise access reviews. Provide a short reference for frequent tasks and a named first line of support. A realistic pilot includes part-time patterns, weekends, ordinary absences and at least one difficult exception. Run it long enough to cover approval and payroll-preparation cycles, while keeping a single controlled fallback rather than indefinite parallel spreadsheets.

After go-live, governance prevents gradual decline. For the first month, review missing entries, late confirmations, corrections, access changes, unresolved support cases and export errors twice weekly. Then move to a monthly process review with an owner and deadlines. Review roles after organisational changes, devices after losses or replacements, qualifications on a fixed rhythm and interfaces whenever a target format changes. Automatic route optimisation, patient records, clinical documentation and insurer billing continue under the owners of their specialist systems.

ROI: measure recurring work, not marketing promises

Build the business case from a baseline. For two representative weeks, count planner hours spent calling replacements, duplicate entries, missing-time follow-ups, corrections before payroll preparation and support questions from the field. After the pilot, measure the same items. Add avoided paper handling and the value of faster availability responses, then subtract licences, implementation, devices, training, interface work and ongoing administration. Do not claim savings from clinical documentation, insurer billing or automatic routing when those processes are outside job.rocks.

A simple calculation is enough: monthly net benefit equals hours avoided multiplied by the organisation’s realistic loaded hourly cost, plus measurable avoided expenses, minus recurring platform and process costs. Also track quality indicators such as the percentage of assignments confirmed before start, working-time records complete by the deadline and replacements resolved without a phone chain. These leading indicators explain whether a financial improvement is sustainable.

Practical example 1: a small regional team

A 24-person team has stable recurring assignments but frequent short-notice absences. Before the pilot, the planner maintains a rota plus a separate availability sheet and calls six people on average for a replacement. In the target workflow, employees maintain availability, the planner filters eligible people, sends an operational request and sees responses in one place. The team does not purchase route optimisation and keeps patient and clinical data in its care system. Its measured gain comes from fewer calls, one plan and fewer evening working-time queries.

Practical example 2: a multi-location organisation

A larger organisation uses many part-time employees across three locations. Its main problem is not creating shifts but applying consistent permissions, qualification data and payroll-preparation cut-offs. It pilots one location, standardises role templates, cleans duplicate profiles and validates an export against the target payroll system. After go-live, location leads review exceptions weekly and central administration reviews access monthly. The organisation retains specialist products for automatic routing, patient records, clinical care documentation and insurer billing. Value comes from consistent workforce governance and fewer correction loops, not from claiming an all-in-one clinical platform.

Frequently asked questions about Spitex apps in Switzerland

Which care app is suitable for a Spitex organisation?

A suitable app supports the organisation’s real workforce flow: check availability and qualifications, deliver the assignment on mobile, make confirmation visible and link working time to the correct assignment. Clinical documentation, route optimisation and insurer billing can remain transparently in specialist systems.

Is job.rocks a complete Spitex clinical system?

No. job.rocks covers operational workforce processes: availability, qualifications, planning, the employee app, communication, time tracking, digital confirmations, self-service and payroll preparation. It does not replace clinical documentation, patient records or insurer billing.

Does job.rocks automatically optimise Spitex routes?

No. Assignments can be linked to people, times and locations, but automated visit sequencing and route optimisation are outside its scope. Use a specialist routing solution when this is required.

Can the app help with last-minute absences?

Yes. Current availability, qualifications, open assignments and notifications make it easier to find and inform a suitable replacement. The planner remains responsible for the final assignment.

Does mobile time tracking replace proof of clinical services?

No. It records working time and deviations for workforce and payroll processes. Clinical services and billable care items belong in the relevant specialist system.

What should we ask to see in a demo?

Request a complete operational workflow: submit availability, find a qualified employee, assign a shift, deliver a change, track time on mobile, review confirmation and export payroll-ready data.

Test your Spitex workforce workflow in a demo

If you want to evaluate planning, the employee app and time tracking in one flow, review the pricing and book a personal job.rocks demo. The public model starts at CHF 2 per assignment; prepaid volume packages are available on request. Bring a real absence or reassignment scenario so you can see how the platform fits your processes and specialist systems.