Shift scheduling
Preferences are collected into a draft, and working-hour limits and labour cost can both be checked before the schedule is published.
Common problems
Building a schedule tends to depend on one person, because it has to satisfy several conditions at once: the headcount needed, employee preferences, working-hour limits, and labour cost. WorkVell brings everything from collecting preferences to publishing into one screen, and shows working-hour overruns and the estimated labour cost while the draft is still being built.
Only a few people can build the schedule
When the schedule can only be built by someone who knows who is available in each time slot and how far the law allows them to be scheduled, work stops whenever that person is away.
Swap requests arrive one by one after publishing
When swaps and cover are arranged through individual messages, it stops being clear which version of the schedule is current, and a gap opens up against the hours actually worked.
Labour cost is only known after the closing
Without cost visible at the point the schedule is built, a budget overrun is noticed only after payroll has run.
What WorkVell does
Preferences are collected into a draft, and working-hour limits and labour cost can both be checked before the schedule is published.
Collecting preferences through to publishing happens in one screen
Preferences are collected from employees, a draft is built, and the schedule is published, all on the same screen. Published shifts can also be viewed on employees' own screens.
Working-hour overruns are shown while the draft is built
If an assignment would take an employee over the working-hour limit, a warning appears during creation. That keeps a schedule with an overrun from being published.
The labour cost estimate is shown while the draft is built
Labour cost for the draft is estimated from the hourly rates on file, so it can be compared against the budget and adjusted before the schedule is published.
Swaps are handled as requests, with a record
A swap between employees is handled as a request, and the approval is kept as a record. Swaps that meet the conditions set can be approved automatically.
From setup to daily use
- 1
Register required headcount and skills
Set the headcount needed for each time slot, together with any qualifications or skills that slot requires.
- 2
Collect preferences
Collect work preferences from employees. What is collected is referenced when the draft is built.
- 3
Build a draft and adjust it
Build the draft and adjust it while watching the working-hour warnings and the cost estimate. AI suggestions are available as an aid at this step.
- 4
Publish and run the schedule
Publish the confirmed schedule. Swaps after publication are processed as requests, and the record is kept.
Built to be relied on
Beyond the feature itself, the groundwork for running and governing it every day.
Built for local rules
Handles the calculations and statutory forms Japanese HR and payroll actually need.
Works in many languages
Employee screens in 9 languages; the time-clock kiosk in 26.
Roles and audit logs
Role-based permissions and activity logs show who saw and changed what.
One connected system
HR, labor, payroll and accounting connect, cutting hand-offs between tools.
Frequently asked questions
Does AI decide the schedule automatically?
No. AI proposes a draft, and the person in charge confirms it. What is proposed is checked in the same way, and warnings appear where working hours would be exceeded or the required headcount is not met.
Can several sites be managed together?
They can. The required headcount is set per site, and employees can also be assigned to cover at another site.
Can the schedule be displayed in different ways?
A timeline view and a calendar view can be switched between. A year and month can also be selected to view past or future schedules.
Does the schedule connect to attendance?
It does. A published shift is treated as the plan, and the difference against the actual clock-in can be reviewed.