Scheduling for personal assistance – which system is suitable?

Short answer: A standard HR system can work when you primarily need to schedule shifts and cover staffing needs. For personal assistance and LSS (Swedish law for support to people with disabilities), more is often required: shifts linked to clients, monitoring against granted hours, working time regulations, substitute workflows, time reporting, payroll documentation, and documentation within the same workflow chain.

Short answer: assistance scheduling requires more than department-based staffing

A standard HR system may be enough for simple staffing planning, but assistance often requires client-linked shifts and verification before payroll processing.

The practical rule of thumb is simple: if the schedule only needs to show who is working in a department, a store, an office, or a general staffing group, a standard HR system may be sufficient. General working time planning is often described as covering the business's needs with available resources and appropriate scheduling of working hours, which is a reasonable core logic in many organizations (SKR).

However, personal assistance rarely functions like standard department staffing. There, every shift normally needs to be understood from two perspectives simultaneously: the client's granted assistance and the assistant's working hours. Försäkringskassan describes assistance compensation as an assessment of individual help needs that leads to a granted number of hours (Försäkringskassan). This means the scheduling question is not just "who can work?", but also "is the shift assigned to the right client, within the right decision framework, and with the correct underlying data moving forward?".

The difference between workplace schedules and client schedules

The major difference is that the assistance schedule follows the individual's decision and service, not just the business's opening hours.

In a standard HR system, the base object is often the workplace, department, or team. You plan the number of people per time slot, competencies, absences, and costs. This is important, but it doesn't always say enough in personal assistance.

In assistance, the base object is often the client or the service. A work shift needs to be linked to the correct person entitled to assistance, the correct time, the correct assistant, and the correct assignment. This affects the decision balance, time reporting, compensation documentation, and in many cases, documentation. Since assistance compensation is based on granted hours, hour consumption and the decision balance become relevant as early as when the schedule is created, not just at the end of the month (Försäkringskassan).

This is where many general systems become blunt. They can show that a person works 08:00–16:00, but often lack the assistance logic regarding who the shift concerns, how the shift affects granted hours, and what data should later be passed on. An industry-specific system should therefore be evaluated not just based on calendar functions, but on the entire flow from planning to follow-up.

Working time regulations need to be checked directly in the schedule

The right system should warn when a shift creates regulatory problems before the error moves further down the line.

ATL (Swedish Working Hours Act, Arbetstidslagen) generally applies to activities where employees perform work on behalf of an employer (Sveriges riksdag). At the same time, collective agreements can affect application, as the law allows for deviations through collective agreements concluded or approved by a central employee organization (Sveriges riksdag).

In addition to Swedish regulations, there are EU working time frameworks, where employers must ensure, among other things, that staff do not work more than 48 hours per week on average and that employees receive at least 11 hours of continuous daily rest (Your Europe).

For assistance providers, this is not just an HR issue. Försäkringskassan states that the employer is responsible for following working time regulations and that assistance compensation is not paid for assistance exceeding permitted working hours (Försäkringskassan). Therefore, it is a clear advantage if the system checks daily rest, weekly rest, and the 48-hour rule directly when the schedule is changed, rather than in a post-check.

Tidvis, for example, describes its scheduling support as built for personal assistance and LSS, with real-time ATL control and warnings before a shift is saved if it creates a violation (Tidvis). The point is not just to find errors, but to prevent them from becoming part of the payroll and compensation flow.

Substitutes, absence, and shift swaps are core flows

In assistance, absence quickly becomes both a staffing problem and a documentation problem.

In many businesses, absence can be handled by someone else in the workgroup covering. In personal assistance, this is often more sensitive. The client still needs support, the right person must be able to work, working time regulations must hold, and the change must later appear correctly in time reporting.

Therefore, you should look closely at how the system handles:

absence on already scheduled shifts
requests to available substitutes
shift swaps between assistants
changes affecting daily or weekly rest
traceability regarding who changed what
updating time reports and payroll data

Tidvis states that substitute management with SMS, shift swaps, and absence compensation is included directly in the scheduling module (Tidvis). It is this type of functionality that distinguishes an assistance schedule from a regular calendar: the change should not just be visible visually, it should work operationally all the way.

The schedule is the beginning of time reports, payroll, and agency documentation

A good assistance schedule should reduce double work between planning, reporting, compensation, and payroll.

In personal assistance, time reporting is not just internal follow-up. Försäkringskassan states that personal assistants must report performed assistance time every month, certify the information, and submit it to the employer, who then passes the time report on (Försäkringskassan). Private assistance providers are also responsible for ensuring that necessary and correctly completed documentation is sent to Försäkringskassan (Försäkringskassan).

This makes the choice of system more significant. If the schedule is in one system, the time report in another, payroll in a third, and the follow-up of granted hours in Excel, several handovers occur. Every handover entails a risk of errors, double registration, and late reconciliation.

An industry-specific system should therefore support the continued flow after the schedule: time reports, control, signing, payroll data, and follow-up. Tidvis, for example, describes an integrated way of working where the schedule, time reporting, payroll, and documentation are all in one system, featuring BankID signing, FK documentation, and payroll flows without manual file imports (Tidvis).

Don't forget documentation and traceability

When the schedule and service are linked, documentation also needs to be correctly connected.

In assistance and LSS, the schedule is often closely linked to what actually happened during execution. Who worked? At which client's home? During which shift? Does something need to be documented, followed up on, or handled as a deviation?

This doesn't mean all documentation issues are solved in the schedule. But system support should make it easy to link the right information to the right client and the right work shift. Tidvis states that daily notes, implementation plans, and deviations can be linked to the correct client and shift (Tidvis). For operations managers, quality, and compliance, this is an important difference compared to a system that primarily shows staffing time.

When is a standard HR system enough?

A standard HR system is best when the scheduling issue is simple and few specialized flows need to be followed up.

It may be a reasonable choice if you:

only need to assign staff to times and workplaces
do not need to track granted hours per client
have few urgent substitute flows
handle working time control, time reporting, and payroll securely in another way
do not need to link the schedule to assistance-specific documentation

However, if you regularly need to check client decisions, ATL, collective agreements, substitutes, shift swaps, time reporting, payroll, and documentation, you should evaluate the system based on the assistance process, not just the calendar.

Conclusion: choose based on the workflow, not the calendar

The best system is the one that supports the entire assistance flow with the least possible double work.

A standard HR system may be perfectly sufficient for simpler staffing. But personal assistance and LSS often require a different level of control, as every shift can affect the client's granted hours, the assistant's working time, agency documentation, and payroll processing.

The most important question is therefore not which system can create a shift. The question is which system helps you schedule the right shift, for the right client, within the right rules – and carries that information forward to time reports, payroll, and follow-up without unnecessary manual handling.

Scheduling for Personal Assistance or a Regular HR System – Which Is Best?