Onboarding in Caire — from standing data to the first schedule

Onboarding happens in the app: Control Center and Datahub hold organization, unit, employees, clients, and care plans. This page links to the Help Center and the dashboard tour.

Try Caire for freeBook a walkthrough

Your organisation's permissions and rules govern who sees and changes the plan. Review trust and data protection

Visit requirements with allowed times and flexibility
Care needs and allowed visit times inform the planning.Visit requirements describe time windows and which visits may move. Changes follow organisational rules and permissions.

Current page

Onboarding

Rollout, training, and a controlled product launch.

In-app onboarding

Caire onboarding is not a connector catalogue or data migration product page. You build standing data in Control Center / Datahub, create a first schedule, and improve the solution step by step — with planner approval before publishing.

How Caire works before the first schedule

Data order in Control Center / Datahub: organization, unit, employees, clients, and care plans before you freeze a schedule.

From first schedule to a better solution

Start AI scheduling, compare the schedule proposals side by side and choose before you publish.

Dashboard tour

See Control Center, Datahub, and the planning surface in the product flow — the same surfaces you use during onboarding.

Standing data in Control Center / Datahub

The first schedule needs active demand and capacity. These resource surfaces are the foundation — field details live in the Help Center.

Organization

Base settings, timezone, and operational defaults that apply across the organization.

Unit

The planning boundary that connects clients, employees, districts, and schedules.

Employees

Capacity, skills, and shift inputs needed for the first solution.

Clients and care plans

Demand and visit inputs that become dated visits when the schedule is created.

Caire Core

Caire Core uses the resource model to decide which visits are possible, which are good, and which need planner review. When outcomes show better buffers, areas or skills, the resource data is updated for the next plan.

Employees and shifts

Availability, skills, working time, breaks, preferences, and historical client relationships.

Clients and service areas

Address, time windows, services, needs, contact paths, and local area rules.

Skills and roles

Match visits against delegations, language, experience, onboarding needs, and role-specific routines.

Travel buffers

Plan with realistic travel, movement, margins, and variation between areas.

Cost models

Make overtime, travel, utilization, and economic impact visible without hiding care quality.

Geography and coverage

See where resources are missing, where routes become too difficult, and how service areas should change.

Comprehensive resource hub

Resource hierarchy architecture

Organization, service area, employee, and client settings cascade into the planning model. Schedule travel buffers, skills, hourly rate, monthly salary, billing, and continuity caregiver limit stay visible instead of becoming hidden assumptions.

Unit overview with employees, clients, districts and visit hours
The overview summarises the unit's employees, clients, districts, shift templates and visit hours per day.The unit's standing data is summarised before the planner moves on to the schedule.
Unit shift templates
The view shows the unit’s applicable shift templates and their local or inherited values.This help image shows where these details are reviewed in the actual view. No changes have been saved.

Employee Compensation Settings

Settings that make cost calculation possible without hiding working time, travel time, or break rules in spreadsheets.

SettingDescriptionConfiguration Levels
Monthly SalaryFixed monthly compensation for full-time/part-time employeesIndividual Employee
Hourly RateHourly compensation for flexible/temporary employeesIndividual Employee, Service Area, Organization
Payment ModelHow hours are calculated (A=Service, B=Service+Travel, C=Shift to Last, D=Full Shift)Organization (applies to all hourly employees)
Break PolicyPAID or UNPAID breaksOrganization, Service Area, Individual Employee
Break DurationStandard break length (e.g., 30 or 60 minutes)Organization, Service Area

Client Configuration Settings

Client data connects allocation, billing, continuity, and responsible caregiver ownership to the same planning model.

SettingDescriptionConfiguration LevelsExample
Monthly Allocation HoursMunicipality-approved service hours per monthIndividual Client100h/month for Anna
Billing RateRevenue per service hour for financial trackingIndividual Client, Service Area, Organization500 SEK/hour municipality contract
Continuity Caregiver LimitMaximum number of distinct caregivers allowed per client within a rolling period (default 14 days)Individual Client, Service Area, Organization10 caregivers per 14 days (tighten to 6-8 for dementia or palliative care)
Responsible CaregiverPrimary caregiver (contact person) for clientIndividual ClientLisa assigned to Anna (lead caregiver designation)
Minimum Lead VisitsMinimum number of visits the responsible caregiver must complete per periodIndividual ClientLisa: >=18 of Anna's 60 monthly visits
Time Window FlexibilityAllowed time buffer for visit start timesIndividual Client, Service Area, Organization+/-5 min (strict) vs +/-30 min (flexible)

Service Area Configuration Settings

Service areas control imports, optimization, cost levels, and whether staff can work across area boundaries.

SettingDescriptionDefaultImpact
Cross-Service Area AssignmentsAllow employees to be assigned visits across different service areasDisabledWhen enabled: Staff can work in multiple areas. When disabled: Staff only assigned to their home service area.
Include in ImportInclude this service area in automatic imports from external systemsEnabledWhen disabled: Area excluded from manual imports and optimization runs.
Include in OptimizationInclude this service area in AI optimization runsEnabledWhen disabled: Area maintains data but does not participate in scheduling.
Default Hourly RateService area-level hourly rate overrideOrganization defaultOverride for high-cost areas, for example urban vs rural compensation.

Schedule Travel Buffers

First and last visits need realistic margins so the shift starts and ends without false precision.

Area TypeFirst Visit DelayLast Visit BufferReasoning
Urban (Dense)5 minutes5 minutesShort distances, predictable traffic
Suburban10 minutes10 minutesModerate distances, variable traffic
Rural (Spread)15 minutes15 minutesLong distances, unpredictable travel
Morning Rush10 minutes5 minutesTraffic delays at shift start
Evening Shift5 minutes10 minutesReturn traffic at shift end

Hourly Payment Models for Staff Costs

The same schedule has a different cost profile depending on whether service time, travel, shift span, or breaks are counted.

ModelPAID BreaksUNPAID Breaks
Model A - Service Only6.5h x 185 = 1,203 SEK (service + breaks)6.0h x 185 = 1,110 SEK (service only)
Model B - Service + Travel7.5h x 185 = 1,388 SEK (service + travel + breaks)7.0h x 185 = 1,295 SEK (service + travel)
Model C - Shift to Last Visit8.0h x 185 = 1,480 SEK (full working time)7.5h x 185 = 1,388 SEK (working time - breaks)
Model D - Full Shift8.0h x 185 = 1,480 SEK (scheduled shift)7.5h x 185 = 1,388 SEK (shift - breaks)

Ready to get started?

Create an account and follow onboarding in Datahub, or book a demo. The dashboard tour shows the same surfaces without signing in.

What it gives your organisation

How onboarding in caire — from standing data to the first schedule helps day-to-day planning.

Standing data in Datahub

Organization, unit, employees, clients, and care plans are set up in Control Center / Datahub before the first schedule.

Guided first schedule

The Help Center shows how to bring in your data and compare the schedule proposals before anything is published.

See the product flow

The dashboard tour shows Control Center, Datahub, and the planning surface without inventing metrics.

Client basics in a read-only view
Basic details bring together the client's identity, contact, designated caregiver and address.The client view makes existing details available for review before editing.
Client list for a selected service area
The client register lists clients belonging to the selected service area.The list brings together client records for the selected service area.
Client continuity target and inherited planning settings
The advanced view brings together continuity target, priority and local overrides.The view shows the client's planning details and how local settings are presented.
Employee list for a selected service area
The employee register lists staff belonging to the selected service area.The list brings together employee records in the service area's context.
Employee standing weekly pattern and hours
The weekly schedule shows ordinary shifts and a summary of working hours.The employee's standing weekly pattern appears with its working-hours summary.
Client continuity limit and default visit settings
    Advanced client fields bring together continuity targets and defaults that new visits can inherit.The form shows where planning values are reviewed and how client values remain distinct from unit defaults.
    Visit template with recommended frequency and preferred weekdays
    Add a visit: recommended frequency sets preferred days of week.Onboarding starts with the client and visit template. Recommended frequency produces preferred weekdays before the first schedule is created.
    Competencies attached to an existing visit template
    The competency step shows selected template competencies and the available competency catalogue.Competency requirements are reviewed on the visit template where they affect who can perform the visit.
    Existing salary and hourly-cost records for an employee
      The cost table shows saved hourly rates and their effective dates.Cost details can be reviewed where they belong to the employee, subject to existing permissions.