Skip to content

Shiftbase Power BI dashboard

We bring staff rotas, approved hours and leave from Shiftbase into Power BI, broken down by department. For Fokker Services, we built a planning tool for work orders and capacity.

Our planning tool helps Fokker Services planners schedule work orders, parts and capacity in advance

Fokker wanted to make maintenance predictable and coordinate the use of staff, parts and hangar capacity as effectively as possible. Working closely with maintenance engineers, we developed a planning tool that combines historical maintenance data, sensor data and operational data.

Read the case study

Does our rota match the hours actually worked at every location?

Shiftbase compares scheduled hours with approved hours for each department. If you want to compare locations, periods and till revenue, you need to export the data to Excel. A Power BI model retrieves the data automatically and retains the history.

Book a meeting

Shiftbase schedules, hours worked, leave and payroll costs side by side for each team

Discuss your scheduling figures

Scheduled versus worked hours

Scheduled hours alongside approved timesheets by department and day, as Shiftbase compares them, but across all locations and periods.

Leave and absence by team

Holiday, sickness and other types of leave by team, even when leave is recorded by day rather than by hour.

Payroll costs versus revenue

Staff costs based on approved hours alongside revenue from your till or accounting system, by location and period.

Match staffing to the work

Staffing levels alongside activity or workload, as our planning tool helps Fokker Services’ planners plan capacity ahead.

We agree what counts as an hour worked and which department bears the costs before loading the data

  1. Departments and definitions

    How locations, departments and teams are named, which hours count as worked and how leave is counted.

  2. Token and initial model

    An API token from the App center, then a single view comparing scheduled hours with hours worked, checked against Shiftbase reports.

  3. Adding revenue and history

    We add revenue from the till or accounting records, and a fixed snapshot preserves the history. We assign ownership of access permissions and data refreshes.

Are the reports in Shiftbase enough, or is it worth building your own Power BI model?

Talk it through with us

A good fit if

You have several locations or departments, want to see schedules and hours alongside revenue, till or payroll data, or want to track longer-term trends without exporting each period.

Not a good fit if

You have one location, and the reporting dashboard and scheduled reports in Shiftbase answer your questions. In that case, maintaining your own model would take more effort than it is worth.

What determines the scope

How many locations and departments are involved, whether teams have the same names everywhere, which other sources you add, such as till, payroll or accounting data, how much historical data you want, and who will take over management.

Will every manager be able to see everyone’s pay?

No. In Power BI, row-level security limits what someone can see. For example, a location manager can see only their own location. We show individual employees’ pay only to people who are also allowed to see it in Shiftbase.

Shiftbase exports, the Public API or a data warehouse that also includes your POS and payroll data?

Exports and scheduled reports

Choose this if you have one location and a standard overview is enough. Shiftbase schedules reports and exports them to Excel or CSV, but every combination still requires manual work.

The Public API

Choose this if you have multiple locations and manage hours and costs on a weekly basis. Our advice: use an ingestion step that retrieves the data and retains the historical records.

A data warehouse

Choose this if Shiftbase is one of several sources, alongside your POS, payroll and accounting systems. See how to have a data warehouse built.

We’ve brought planning, capacity and staff allocation together in one view before

Data Science Lab has worked with data and AI since 2016 and is a Microsoft Partner for Fabric. We built a planning tool for work orders and capacity for Fokker Services, and Power BI dashboards covering planning and other areas for Ammega.

Book an introductory meeting

Your locations, Shiftbase reports and the figures you currently combine in Excel: that’s where the first conversation starts

Stef Stoelwinder

Stef Stoelwinder

Business Development

Stef is your first point of contact. In our first conversation, we’ll discuss your locations, your Shiftbase setup and the summaries you’re missing.

Which locations and departments from Shiftbase would you like to see side by side?

Tell us how many locations you have and which POS or payroll system you use alongside Shiftbase. We’ll reply by email or suggest an initial meeting.

Enter a valid email address.

Let us know how we can help you.

Frequently asked questions

Through Shiftbase’s Public API. According to its help centre, the API is designed for exchanging data between systems and for retrieving data with a BI tool. You can request a token in Shiftbase under Settings, App center, Public API. We load the data and build the Power BI model on top of it.

To find out why we start with the decision you need to make rather than the charts, see Power BI dashboards.

Shiftbase lists employee data (contracts, absence and leave, overtime), schedules (shifts, staffing, open shifts, forecasts and budgets), timesheets, clock-in and clock-out times, and reports as examples.

For a dashboard, you’ll usually need schedules and approved hours by department and team, leave and sickness absence, contracted hours, and the labour costs Shiftbase calculates from hours and contracts.

Shiftbase has a Schedule vs. timesheets report for this. It shows scheduled hours alongside approved recorded hours by day and department, including the difference. The smaller that difference, the better the schedule matches the hours worked.

In Power BI, we use the same definition — approved hours only — and compare the difference across locations, teams and periods. This turns a Shiftbase report into a trend.

Shiftbase calculates labour costs as a percentage of revenue in its reporting dashboard, but only if revenue data is available in Shiftbase. You can enter it yourself or bring it in through a point-of-sale integration; according to the help centre, the Lightspeed Retail integration retrieves revenue every night.

In Power BI, we prefer to retrieve revenue directly from the point-of-sale or accounting system, as we do for the Lightspeed Retail Power BI dashboard.

Shiftbase calculates the absence rate based on contracted hours and only counts absence marked as leave. Leave types such as holiday, sickness, special leave, care leave, parental leave and unpaid leave each have their own column.

To find out which other absence figures HR needs, regardless of the system, see the HR dashboard in Power BI.

Because Shiftbase distinguishes between an employee’s team and their contract department. An employee can work in teams across several departments but always has one contract department. Shiftbase assigns absence costs to that contract department.

In the model, we specify which of the two to use for each metric: hours worked by the team where they were worked, and contracted hours and absence by contract department.

In Shiftbase, permissions determine who can view reports. In Power BI, row-level security limits what someone can see: for example, a site manager may see only their own location. We keep the token used to load the data outside the report.

For how we set up workspaces, permissions and refreshes, see Power BI consultant.

If you have one location and Shiftbase’s reports answer your questions. Or if hours aren’t approved consistently: in that case, start with data quality, because the model counts what’s recorded.

If you run payroll in AFAS, read about the AFAS Payroll Power BI dashboard too. If a simpler solution is a better fit, we’ll say so.