MILabs
Integrations

Staff utilisation report with Karbon data

Staff utilisation report from Karbon data, with billable hours and utilisation by person and team, exported on a schedule.

Updated 2026-02-06

Staff utilisation report with Karbon

Karbon keeps the working record for many professional service teams. A staff utilisation report reads that record and turns it into a regular view of how much paid time goes to billable work and how much goes to admin, training and idle capacity. For a team lead, the value is a figure that updates on a schedule instead of one assembled by hand before a meeting. The report changes no Karbon records. It reads what the connected user can see and writes a summary to a location the owner chooses. Decisions about which hours count as billable, which count as available and how rosters are treated come first, and the build follows those definitions. Any gap caused by permissions should be treated as a data question before it is read as a result.

How it works

  1. Agree the definitions of billable, non-billable and available hours with the owner or team lead before any data is pulled.

  2. Connect through Karbon's API using a user whose permissions cover the time and roster records the report needs.

  3. Pull time entries and roster details on a fixed schedule, and match each entry to the person and team it belongs to.

  4. Calculate billable and non-billable hours per person, then roll utilisation rates up by team against available hours.

  5. Write the summary to a shared spreadsheet and keep a record of each export so the figures can be checked later.

good questions, straight answers

Frequently asked questions

Can a staff utilisation report work with Karbon data exports?
Yes, provided the export includes the person, team and hours fields the report needs. Check which export formats your Karbon plan offers before building, because a missing column will leave a gap in the figures rather than a guess. Keep a copy of each export so any figure can be traced back to its source later.
What should I back up in Karbon first?
Before any build touches Karbon, export a copy of the time and roster records the report will read, and store it apart from the live system. Note the export date so later figures can be compared with it. Also record which user account the connection will use, since that account sets what the report can see.
How does a staff utilisation report connect to Karbon?
There are two good routes. Where the official API offers read access to the needed records, a custom service can request them on a schedule, using a user whose permissions cover the time and roster data. A scheduled export to a file works as well, and it is a quick way to get the first report in front of the team. MILabs picks the route that fits your account at the start of the build.
Do I need a developer to connect a staff utilisation report to Karbon?
Usually, yes, because a scheduled pull through an API needs someone to write and maintain the connection, along with the calculation and spreadsheet output. A team that only needs a periodic export and a formula-based sheet may manage without custom code, depending on the data available. Either way, the connected user's permissions and the report's definitions should be agreed with the owner before any work begins.
How does a staff utilisation report stay in step with Karbon?
It stays in step by re-reading the source on a fixed schedule, so each cycle reflects the latest time and roster entries rather than the previous summary. Edits made in Karbon appear in the report at the next scheduled pull. Confirm how edits made through an outside service are logged in the Karbon activity history, because that history is the reference for review.
let's make something happen

Custom development: how we can help

Choose how you want to work on this with MILabs. Both options start with an enquiry.

Discovery is free, no obligation from the first chat.

Let us build it for you

We build it and look after it.

Build it yourself, we'll help

You build it with our direction, teaching and a weekly check-in.