Planworks alone
- Requests, shifts and availability
- Reports in Planworks, separate from your ATS and payroll
Planworks with Dashly
- Requested hours next to deployable hours, by region and role
- The same definitions as for your other systems
What you see with it
- Fill rateFlex workforcefilled shifts ÷ requested shifts
- Growth per clienthours this period ÷ hours in the same period last year
- Last-minute shareFlex workforcerequests less than 48 hours before start ÷ all requests
- Skills matchrequests with suitable available candidates ÷ all requests
- Expired but scheduledshifts with an expired mandatory certificate
- Rest period breachesComing soonshifts that breach the Arbeidstijdenwet
What Dashly collects
- Requests and shifts
- Scheduled deployment
- Availability
- Dropouts and no-shows
- Rosters and rest periods
How it connects
You pick Planworks from the connections and connect it yourself through the marketplace. Dashly collects the data on a schedule, with history, so you no longer need to export anything. Dashly AGI sets up the rest: the model, built on your definitions, and the checks.
For each connection you see its status and how fresh the data is. If something goes wrong, you see it.
Planworks