Diagnostics

    Unassigned home-care visits: causes, actions, and follow-up

    An unassigned visit is not always a sign of too little staff. It can also come from a narrow time window, a skill requirement, a geographic limit, or inputs that do not describe reality well enough.

    2026-08-037 min

    Start with why, not only how many

    The count shows that something needs review, but not what. Each group should reveal which constraint prevented a suitable resource from being found.

    That distinction determines the next action. A capacity gap needs a staffing discussion, while wrong time windows or skills need data correction.

    Four common causes

    The first is real capacity shortage at the required time. The second is that too few staff meet the visit requirements. The third is an unrealistic time window or duration. The fourth is geography and travel making an allocation infeasible.

    Analyze causes separately. Treating every issue as staffing shortage can add staff when the real fix is better data or planning rules.

    • Check duration and allowed times.
    • Check skills, double staffing, and continuity requirements.
    • Compare capacity with travel and service area.

    Make actions traceable

    When a visit is assigned after a change, record what changed: a shift, time window, skill, route, or visit input. That shows whether the root problem was solved or only moved.

    Planners also need to make a manual decision when necessary. Traceability does not mean automating every decision; it means making the decision understandable later.

    Follow up over time

    Track unassigned visits by area, time of day, skill, and weekday. Repeated patterns can reveal a structural staffing or scheduling gap, while isolated exceptions often need local handling.

    When diagnosis and follow-up are combined, unassigned visits become an improvement signal. The goal is realistic plans and a clearer next decision, not only fewer red rows.

    Three things to take away

    • An unassigned visit is a signal that needs a cause.
    • Separate capacity gaps from constraints and poor inputs.
    • Record what changed and check whether the problem returns.