Staff utilisation report built on Harvest time data
A staff utilisation report that reads Harvest time entries and shows billable hours against available hours by person and team.
Updated 2026-06-12
Staff utilisation report with Harvest
Harvest already holds the hours that a utilisation report needs, but they sit in individual time entries, and someone has to gather them before any comparison means anything. For a firm that bills by the hour, the working question is plain: of the time each person was available, how much went to client work? A report built on Harvest answers that from the entries your team logs day to day, rather than from a spreadsheet refreshed at month end. The build reads the hours and the billable split on each entry, sets them against the working hours each person is expected to give, and shows a utilisation rate by person and by team. Gaps in logging then show up in the report itself. A team leader can use the same view to judge whether a group can take on another commission, and an owner can test whether a hire is justified by the numbers.
How it works
Confirm with the owner which hours count as available for each person, such as a standard working week minus approved leave.
Connect to Harvest's REST API with the account's access credentials, limited to what that account is allowed to read.
Pull the hours and billable split for each person on a fixed schedule, then store one row per person per week in a shared table.
Calculate billable hours as a share of available hours, by person and by team, and check the totals against the Harvest web app for one sample week.
Send the summary to the owner or team lead as a shared spreadsheet, and have a named person review the figures before anyone acts on them.
Retest the connection after any change to Harvest's API or exports, since a vendor update can change what the report receives.
Frequently asked questions
- How does a staff utilisation report connect to Harvest?
- The report connects through Harvest's REST API, which lets an approved tool read time entries, projects and clients with the account's access credentials. A scheduled job pulls the hours for each period and passes them to a calculation step. If a field cannot be reached through the API, the same data can be exported from the Harvest web app as a spreadsheet and loaded on a schedule.
- Do I need a developer to connect a staff utilisation report to Harvest?
- Usually, yes, for the first connection. Someone needs to create the access token in Harvest, set up the scheduled pull, and check that the figures match the web app for a sample week. A developer or an experienced admin can also set up the calculation and shared spreadsheet. Once the connection is working, the owner or team lead should only need to review the output.
- How does a staff utilisation report stay in step with Harvest?
- The report stays current by re-running its pull on a fixed schedule. Late edits in Harvest, such as entries changed after a run, show up the next time the period is pulled, so a fresh pull just before you close the month gives you the final picture. If Harvest ever updates its API or export format, a run against a sample week shows the figures still line up.
- How do I know a staff utilisation report works with Harvest?
- Test it against a week you already know. Choose a week with known totals, compare the billable and available hours the report shows for each person with the entries in Harvest's web app, and note any difference. Differences usually point to missing projects, untagged entries or a wrong working-hours figure, so fix the source before changing the formula.
- Can I start with a part of a staff utilisation report on Harvest?
- Yes. A sensible first stage is the import of hours from Harvest for each person, with the billable split and a single summary for the owner. Utilisation by team, alerts when a team moves outside an agreed range and a comparison with earlier periods can follow once the first summary has been checked. Starting small keeps the number of moving parts low while the team learns what the figures mean.
Related
read these nextUp a level
More with Harvest
- Invoice chasing automation for Harvest: how the build works
- Job profitability report built on Harvest time and invoice records
- Harvest owner dashboard: one reviewed view of hours and invoices
- Timesheet automation for Harvest: entry checks, reminders and reviewer flags
- AI adoption for Harvest time tracking and invoicing teams
- AI strategy for Harvest time tracking and invoicing
- Custom development for Harvest: bespoke systems for time and billing
- Product idea for Harvest: shaping a first version
- Workflow automation for Harvest time tracking and invoicing
