Expected revenue
Forecast values give you a sense of how much staffing makes sense per day and location.
Scheduling
The scheduler plans shifts against availability, revenue forecast and staff cost limits.
The scheduler reads availability, contract hours, expected revenue and labour-law limits from the same data model. Staff cost ratio and forecast appear inside the plan.
Plan against revenue, not just against availability.
Expected revenue
18,400 €
Forecast · week 16
Planned staff cost
5,120 €
47 shifts
Staff cost ratio
27.8 %
Target ≤ 30 %
Productivity · Planned
€85 / h
Actual last week · €78 / h
Open shifts
3
this week
Forecast deviation
+4 %
vs. plan
Staffing against expected revenueIllustrative example
- Mon · Lena R. · 16–22 · Service
- Tue · Marko K. · Off
- Wed · Anna M. · 10–14 · Brunch
- Thu · 2 open shifts
Employee
Mo
Di
Mi
Do
Fr
Sa
So
Lena R.
Service · Full-time
10–14
—
10–14
12–18
—
16–22
—
Marko K.
Bar · Part-time
—
12–18
—
10–14
10–14
16–22
—
Anna B.
Kitchen · Full-time
12–18
12–18
16–22
—
12–18
12–18
—
Pia S.
Service · Mini-job
—
—
10–14
10–14
—
16–22
—
Tom F.
Service · Werkstudent
—
10–14
—
—
16–22
—
—
Early shiftMid shiftLate shift
Σ 84 h · labour-law conflicts: 0Forecast values and staff cost ratio appear in the plan before it is published.
Forecast values and staff cost ratio appear directly in the schedule. The result: schedules that work operationally and keep staff cost in range.
Staff cost ratio
ONA shows whether the planned hours match the expected revenue.
Productivity
Productivity shows how much revenue is planned and actually achieved per labor hour.
Targeted staffing
Forecast deviations are shown per day and location. Staffing decisions remain with the manager.
Forecast values support planning; the final staffing decision stays with you. Numbers in the cards are illustrative.
What the scheduler checks during planning.
Everything you need for a published weekly plan — and nothing you would never use.
Shift templates
- Reads
- Role × location × day pattern
- Rule
- Minimum staffing per time block
✓ Template applied⚠ Review manually
Preferred days
- Reads
- Employee availability profile
- Rule
- Preferred days against open shifts
✓ Considered⚠ Deviation flagged
Shift swap
- Reads
- Swap request + role
- Rule
- Labor-law limits for both employees
✓ Approved⚠ Conflict
Mobile publish
- Reads
- Published plan
- Rule
- Team visibility active
✓ Visible to team⚠ Draft
Drag-and-drop
- Reads
- Shift action (move / duplicate)
- Rule
- Labor-law preserved on move
✓ Applied⚠ Conflict
Calendar + employee view
- Reads
- Plan data
- Rule
- Same data model, different view
✓ In sync
Punched times live in the same data model as the shift plan. Deviations between planned shifts and actual punch times — via tablet or mobile app — are visible in the target/actual comparison.
Book a demo
One payroll run. Your setup. 30 minutes.
No generic demo. We configure ONA around your locations, contracts and POS connection — and run trial payroll in the system.
- Locations and contract types as input
- Trial payroll live in the system
- Response within one business day
- No contract commitment