Back to help center

    Onboarding

    From first schedule to better solution

    Follow the full loop from first schedule to stronger operations: create a solution, read the recommendations, complete the data, and run again.

    Why the first solution can be weak

    The first schedule does not need to be perfect. It should prove that the foundation data can create a solution and show which fields limit quality.

    Once Caire has run a first solution, missing data becomes concrete: service area, districts, designated caregivers, shifts, skills, cost assumptions, and visit timing appear as recommendations.

    The loop

    Start in onboarding and fill only blocking foundation data. The service area is the planning boundary: clients, care plans, and visit templates become demand, while employees, shifts, skills, costs, and availability become supply. Then create a first planning period, materialize visits and shifts, and run a solution even if readiness is incomplete.

    • Read the first solution as a baseline, not as the final result.
    • Open Diagnostics and choose one or two recommended data improvements.
    • Update client, employee, district, or visit-template data.
    • Run a new solution and compare it with the baseline.
    Solution entry point where the planner creates or reruns a solution.
    Start a new solution from the schedule once foundation data and the period are in place.
    Comparison between baseline and CAIRE solution with metrics.
    The comparison shows what changes between the baseline and the CAIRE solution.

    What should improve

    After the data update, at least one important metric should move in the right direction: fewer unassigned visits, higher paid-shift efficiency, less unexplained wait or idle, better continuity, or lower travel/cost. When the data foundation is complete, the workflow becomes low-touch and planner-approved: Caire can propose the next schedule and the next replan, but changes are reviewed before they are used.