MILabs
Integrations

Staff utilisation report for Asana workspaces

A staff utilisation report that draws task and project data from Asana into one view of billable and internal hours.

Updated 2026-01-01

Staff utilisation report with Asana

Asana holds much of the task-level detail a utilisation report needs, but hours are usually recorded somewhere else. A project board shows who owns a piece of work and when it is due, while time spent on it often sits in a timesheet tool or payroll roster. A useful report on this pair starts by deciding which Asana fields stand in for billable work. A custom field, project type or section name can mark whether a task is client-facing or internal admin. Once those labels are consistent, the report can group open and completed tasks by person and by team. Owners should agree the labels with the people doing the work first, since loose tagging makes the report misleading. The grouped figures can then go to a shared spreadsheet on a fixed schedule, so the owner sees capacity without asking each lead for a fresh count.

How it works

  1. Agree a tagging scheme in Asana, using a custom field or a fixed project type to mark each task as billable client work or internal admin.

  2. Connect Asana to your timesheet or roster source through the REST API, or through a connector such as Zapier, Make or n8n, so each person's logged hours can be matched to the tasks they were assigned.

  3. Read assignees, due dates and custom fields on a schedule, using an account whose workspace permissions cover the projects in scope, then total billable and internal hours for each person.

  4. Write the results to a spreadsheet or Airtable base that a dashboard tool such as Power BI or Looker Studio can chart, showing utilisation by person and by team against available hours.

  5. Review the first two cycles with project owners, correcting any task tags that were set wrongly before the figures are shared more widely.

good questions, straight answers

Frequently asked questions

Does a staff utilisation report change how my team uses Asana?
Mostly it asks for more consistent tagging. Team members set the same custom field or project type on each task, because the report can only split billable and internal work as well as those labels allow. Assignees and due dates also need to stay current. The Asana workflow itself does not have to change, and people do not need a new tool to see the report.
How do I measure a staff utilisation report on Asana?
Measure in three parts: hours by category, utilisation against available hours, and coverage of the data. Define available hours from the roster for each person, then compare billable hours to that figure for each week or month. Also check the share of tasks carrying a valid tag, since low coverage means the rate is understated. Track the trend over several cycles rather than one result, and note the method beside each figure.
What does a staff utilisation report read from Asana?
It reads task records, including assignee, due date, completion status, section, project and any custom fields used for tagging. Access runs through the REST API or a connector such as Zapier, Make or n8n, and the account used can only see projects its workspace permissions allow. Hours usually come from a separate timesheet or roster source, so Asana supplies the work context while that source supplies time.
Is a staff utilisation report safe with Asana data?
Yes, when access is set up deliberately. Create a dedicated account with read access only to the projects the report needs, rather than reusing an administrator's login. Store API tokens in a secrets manager or the connector's credential store, and avoid pasting them into shared documents. Review which people can open the output spreadsheet, because it will show individual workloads and may be sensitive to staff.
What happens if Asana changes?
The report is built to flex. It does not lean on any single field or endpoint, so updates to Asana's built-in features or API leave it steady. After a change to a plan, region or permission model, a quick test of the connection keeps everything flowing, and a connector that breaks shows up as flagged missing data instead of silent gaps.
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.