COMPARISONS

    Carefox and Caire — complete planning beside the journal

    Caire is a complete AI planning system. Carefox can remain for documentation and journal; where an API exists, Caire can fetch planning data one-way.

    Caire schedule and map view; Carefox can remain for journal
    Back to Resources
    Jul 25, 2026
    6 min read
    Caire Team

    Caire is a complete standalone planning system: standing data, schedules, AI optimization, and publishing live in Caire. Carefox may remain for documentation and journal. Where a Carefox API is configured, Caire can fetch planning data one-way (GET) — there is no automatic write-back. The planner reviews and approves in Caire before publish.

    How Carefox and Caire can work together

    Plan in Caire; journal can stay in Carefox

    Caire owns the planning role end to end. If you already use Carefox, documentation and journal can stay there. Optional one-way GET seeds planning data where an API is configured — the planner publishes approved schedules in Caire; automatic write-back to Carefox does not exist.

    What Caire provides as the planning system

    Schedule optimization

    AI-generated schedule proposals that increase client-facing time and protect continuity — the planner reviews and approves every proposal in Caire before publish.

    Route optimization

    Route proposals can free time for care while planning and publishing stay in Caire.

    Continuity tracking

    Fewer different caregivers per client over time, tracked and surfaced so the planner can weigh continuity against travel time and staffing.

    What can stay in Carefox

    • Care documentation and journals
    • Compliance and regulatory records
    • Care history and client records
    • Day-to-day check-in/check-out for staff

    Frequently asked questions

    Does Caire replace Carefox?

    No. Caire is a complete planning system for standing data, schedules, routes, and publishing. Carefox can remain for documentation and journal — Caire does not replace those functions.

    Who approves schedule changes?

    The planner always reviews and approves every AI-generated schedule proposal in Caire before it is published. Caire never publishes changes automatically.

    How does data move between Carefox and Caire?

    Standing data lives in Caire. Where a Carefox API is configured, Caire can fetch planning data one-way (GET). There is no automatic write-back of schedules to Carefox.

    Do we need to migrate out of Carefox?

    Not for documentation and journal — those can stay in Carefox. Planning runs in Caire. Optional one-way GET can seed planning data where an API is configured; other external coupling is custom at onboarding.

    Start with your Carefox exports

    Keep your current system and analyse one selected period. Upload visit history and a client/address register from Carefox; the result shows a baseline and areas to investigate, not a guaranteed saving.

    You need an account, an organisation and two Excel reports: visit history and a client/address register from Carefox or Welfare/eCare. Employee and shift data are optional.

    One analysis per organisation. A paid pilot and subscription are separate decisions.

    Key metrics

    • One-way GETOptional Carefox fetch; no write-back
    • ReviewedEvery proposal approved by the planner in Caire

    Already using Carefox?

    Talk to us about planning in Caire while Carefox stays for documentation and journal.