Staff utilisation report for Deputy rosters and timesheets
How a staff utilisation report can draw hours from Deputy timesheets and rosters into one regular view for owners and team leads.
Updated 2026-08-18
Staff utilisation report with Deputy
A staff utilisation report shows how paid hours divide between delivery work and everything else. In Deputy, the raw material already exists: who was rostered, when people clocked on and off, and how leave affected availability. The difficulty is interpretation. A timesheet can show a full day without saying whether it went to client work, training, cleaning or waiting for a job to start. Deputy also organises records around shifts, whereas a utilisation view usually treats a person or team as the unit. Building the report means agreeing that mapping first, choosing which export or API route supplies the hours, and deciding where the owner checks the figures before they inform rostering or pricing. The report then guides planning conversations, while pay figures stay with the payroll process.
How it works
Agree the unit of measure with the owner or team lead, such as each person or each team, and the split between billable and non-billable time.
Confirm which Deputy export or API route the account permits, and which timesheet and roster fields it returns for the agreed period.
Pull hours from Deputy into a staging table, matching each record to a person and a category, and flag any shift that cannot be classified.
Calculate utilisation as worked delivery hours divided by available hours for each person, then roll the results up by team.
Send the summary to a shared spreadsheet on the agreed schedule, and have the owner review the figures before they are used for rostering or pricing decisions.
Frequently asked questions
- Can I start with a part of a staff utilisation report on Deputy?
- Yes. A common first step is a report for one team, using one agreed export from Deputy and one agreed period of records. That shows whether the hours are complete and whether the categories make sense before anything is extended. Adding more teams, comparisons with earlier periods or client breakdowns can follow once the first view has been checked by the owner or team lead. A narrow start also keeps access to Deputy limited to the data that the report actually needs.
- How does MILabs test a staff utilisation report against Deputy?
- MILabs compares the report with figures the owner already trusts. That usually means choosing a period where the team's hours are known, rebuilding the totals from the Deputy export, and checking that each person appears once, that leave and public holidays are handled as agreed, and that the utilisation rate matches a hand calculation for a sample of staff. Any gap is traced back to its source record in Deputy, and the rules are adjusted until the numbers agree.
- What does MILabs do after delivering a staff utilisation report for Deputy?
- After handover, MILabs documents how the report gets its data, which Deputy route it uses, who holds the access token, and how the calculation rules are set out. The owner or team lead gets notes on how to check the output and how to raise a question when a figure looks wrong. Any change to the Deputy permissions or to the categories is recorded so that later figures can be explained. Further support is discussed through the enquiry form.
- Can a staff utilisation report work with Deputy?
- It can, provided Deputy's API or an export gives the report the timesheet and roster records it needs, and the account permissions allow that access. An outside tool cannot read Deputy records without such a route. Where only an export is permitted, the file is saved to a shared spreadsheet on a set cycle and the utilisation view reads from that file. Because access depends on the plan and permissions, the route is confirmed for each account before the build begins.
- What does a staff utilisation report write to Deputy?
- In the standard build it writes nothing to Deputy. The report reads timesheet and roster records, calculates hours in a separate store, and presents the result to the owner or team lead. Any write-back, such as correcting a timesheet or changing a roster, is a separate decision with its own permissions and review step, and it is excluded from this build by default.
Related
read these nextUp a level
More with Deputy
- Onboarding assistant for Deputy: starter checklists and first-week schedules
- Payroll preparation automation for Deputy timesheets and rosters
- Staff roster planner for Deputy: how the build works
- Timesheet automation with Deputy
- AI adoption for Deputy teams: training staff on rosters, timesheets and leave
- AI strategy for Deputy businesses: rosters, timesheets and payroll prep
- Custom development for Deputy: bespoke tools for shift-based workforce teams
- Deputy product idea for shift-based teams
- Workflow automation for Deputy: shift, timesheet and payroll tasks
