1
Needs analysis
We map current workflows, rules, roles, data, and scheduling goals.
AI planning with Carefox
Complete planning system — Carefox can remain for the journal; planners publish in Caire
Current page
Carefox AI scheduling
More efficient planning with Carefox and Caire.
Answer first
Caire is a complete planning system — Carefox can remain for records
Caire owns standing data, schedules, AI optimization, and publishing. Carefox can stay for documentation and journal. Where a Carefox API is configured, Caire can fetch planning data one-way (GET) — there is no automatic write-back to Carefox. Planners review and publish in Caire.
| Question | Carefox | Caire |
|---|---|---|
| Primary role | Operations, documentation, and records/journal | Complete AI planning (standing data, schedule, routes) |
| Data between systems | Source for journal/documentation | Optional one-way GET of planning data where API is configured; no write-back |
| Publishing | Not replaced as the records system | Planner reviews and publishes in Caire |
| Replacement? | No — journal and documentation can remain | Does not replace Carefox journal; owns the planning role |
How Caire and Carefox can work together
Caire stands alone. If you already use Carefox, documentation and journal can stay there. External coupling is custom per customer — not a public product catalogue. Where a Carefox API is configured, Caire fetches planning data one-way.
One-way fetch where API exists
When a Carefox API is configured, Caire can fetch planning data (GET) into the planning system. There is no automatic write-back of schedules to Carefox.
Custom per customer
We do not market a public list of connections to other planning systems. Any external link is set up with you at onboarding — based on what your installation allows.
How the flow works
1
Standing data in Caire
Clients, employees, care plans, and service areas live in Caire. Where a Carefox API exists, planning data can be fetched one-way in.
2
AI optimization
Caire creates scored schedule and route candidates for planner review using configured inputs, rules, and priorities.
3
Review and approval
Planners review the proposal and must approve it before it is published.
4
Publishing in Caire
The completed schedule is published in Caire and in the caregiver app. It is not written back automatically to Carefox.
Implementation
Launch Caire without ripping out the Carefox journal
You do not have to choose between documentation and better planning. Caire takes the planning role; Carefox can remain for journal and documentation. Any API fetch is set up per customer.
Proven process
Implementation follows a clear path: needs analysis, configuration, testing, training, and follow-up. Planners know what happens before the first live schedule.
Minimal operational disruption
Journal and documentation can continue in Carefox while planning is built in Caire. The goal is clear control before publishing — without double-administering the same schedule.
The onboarding process
2
Configuration
Standing data and rules are set up in Caire. Where a Carefox API exists, one-way fetch is configured with your IT team.
3
Training & testing
Key users test the flow and learn how to review, adjust, and publish in Caire.
4
Launch & follow-up
First live schedules are followed up so the impact is measurable in practice.
Why Carefox customers can move quickly
Focused onboarding
A focused rollout lets you test real schedules, compare outcomes, and start reducing manual planning quickly.
Keeps Carefox for the journal
The team can keep using Carefox for documentation and journal, while Caire owns planning, optimization, and publishing.
Training for the right roles
Planners, administrators, and leaders get role-specific sessions so each role understands its decisions, controls, and KPIs.
Support after the first schedule
We follow up quality, travel time, continuity, and workflows once recommendations meet live operations.
Technical details
Carefox: one-way GET
Where a Carefox API is configured, Caire fetches planning data one-way. Automatic write-back to Carefox does not exist. Other external coupling is custom per customer.
Security
All data communication is encrypted according to industry standards. CAIRE is developed with GDPR and Swedish Social Services Act requirements for data security in mind.
Guided onboarding
We set up standing data, train planners, and follow up on the first schedules together — at the pace that fits your organization.
Standalone planning
Caire is a complete planning system. Carefox is a complement for journal/documentation — not a public list of ready-made system connectors.
Related features
Route Optimization for Home Care – compare planner-reviewed trade-offs
More client-facing time, protected continuity, and fewer unassigned visits — planners review every proposal
Carefox and Caire — how they complement each other
A deeper guide to Caire as the planning system and what can remain in Carefox for journal and documentation.
See how Caire plans alongside Carefox
Book a demo and we will show Caire as a complete planning system — with Carefox kept for the journal if you want, and planner-controlled publishing in Caire.
Book a demoMeasures and business-case inputs
See how ai planning with carefox supports run-specific comparison
Optimized schedules
AI-driven scheduling that maximizes resource utilization
Time Savings
Reduce manual analysis through diagnostics, scenarios, and recommended next actions
Carefox can remain
Documentation and journal in Carefox; planning in Caire. Where API exists: one-way fetch of planning data.