Back to help center

    Diagnostics

    Schedule diagnostics

    How Caire connects schedule health to missing data, bottlenecks, scenarios, and the next best action.

    Diagnostics are the next onboarding step

    Once a schedule has run, diagnostics show what the result says about the data. Each recommendation is classified as completing data, running a profile, staging a scenario, or re-running optimization.

    Diagnostic summary showing bottlenecks and recommended next steps.
    The diagnostic summary shows bottlenecks and the next safe action after a solution.

    From bottleneck to action

    Diagnostics read the schedule, solution, clients, employees, shifts, and visits together. That lets Caire separate missing foundation data from a real capacity bottleneck and from a controlled improvement proposal that needs a new solution.

    • Complete missing data by updating a specific client, employee, district, or visit field.
    • Run a planning profile that matches the goal.
    • Prepare a reviewable scenario before standing data changes.
    • Run a new ESS/FSR solution when the input is ready.
    Demand view and calendar show visits, time windows, and care minutes in the CAIRE solution.
    Demand next to the calendar makes it clear whether the issue is data, capacity, or timing.
    Action ledger shows which improvements and decisions follow from diagnostics.
    The ledger shows which actions and decisions follow from diagnostics.

    Data limitation or real bottleneck

    Caire separates problems caused by limited information from problems that remain despite good data. That makes actions more concrete and reduces the risk of tuning the wrong thing.

    Direct links back

    Every data-related recommendation should link to the exact client, employee, district, or visit and open the right help content in context.