Como criar um relatório de utilização no Jira?

What is resource utilization?

A utilização de recursos é definida como a medida em que uma organização usa seu pessoal disponível e

Here’s the distinction most guides skip, and the one that causes most of the spreadsheet arguments: utilization has two directions.

‍Looking backward, utilization is logged hours divided by available hours. It tells you whether the time you had actually went into the work. This is the number finance asks about.

‍Looking forward, utilization is scheduled hours divided by available capacity. It tells you whether you’re about to run out of people three weeks from now, while you can still do something about it.

Both are legitimately called “utilization.” They answer different questions, they come from different data (worklogs vs. estimates and bookings), and they should be tracked separately. When two people quote different utilization numbers for the same team, this split is usually why. From there, the rest is deciding what a good utilization rate looks like, how billable utilization differs from overall utilization, where Jira’s native reporting falls short, how to measure both views with ActivityTimeline, and what to change to improve the number without breaking the team.

Relatório de utilização de recursos no Jira

Com o tom dos projetos e tarefas do Jira e das dezenas de equipes do Jira, é vital coletar os dados para medir o desempenho geral. A chave para o sucesso não é apenas coletar os dados, mas também analisá-los para obter melhores insights e métricas.resource utilization = (hours worked ÷ available hours) × 100. A developer who logs 32 hours of project work in a week where they had 40 available hours is at 32 ÷ 40 × 100 = 80% utilization. For forecasting, the same formula uses scheduled hours instead of logged ones: scheduled hours ÷ available capacity × 100.

The formula is the easy part. Two refinements decide whether your number means anything.

‍First: available hours are not contract hours. A 40-hour contract with one public holiday in the week means 32 available hours, not 40. Subtract vacations, holidays, sick leave, and part-time schedules before you divide. This is where most homemade spreadsheets quietly break: they divide by 40 for everyone, every week, and then nobody understands why the numbers never reconcile with reality. The person who took Friday off didn't have 40 hours. Pretending they did makes them look underutilized when they were actually fully booked.

‍Second: decide what counts as the "work" on top. If you count every logged hour, you get overall utilization. If you count only client-facing, chargeable hours, you get billable utilization: billable hours ÷ available hours × 100. Internal meetings, training, admin, and the weekly all-hands are real work, but they're non-billable, and for a services business the billable number is the one that connects to revenue. A consultant with 34 billable hours out of 40 available is at 85% billable utilization, even if their overall utilization is closer to 100%.

Get those two things right (honest availability on the bottom, a clear definition on top) and the rest is arithmetic.

What is a good resource utilization rate?

Os relatórios desempenham um papel importante na análise. O gerente de projeto ou gerente de recursos pode pesquisar e encontrar uma variedade de relatórios. Dois deles podem fazer um esforço real. O Jira fornece relatórios de utilização padrão que podem cobrir algumas necessidades básicas no planejamento de projetos. É um relatório de controle de tempo e carga de trabalho do usuário. É possível encontrá-los na lista de relatórios de cada projeto no Jira.

Why not 100%? Because a Jira team's week contains work nobody scheduled: the production bug, the support escalation, the estimate that was off by a day, the meeting that appeared on Tuesday. A plan with zero slack doesn't absorb any of that; it just converts it into overtime. And people who run at 100% for months ship worse work and eventually leave, which is the most expensive utilization problem there is.

Why not relax at 60%? Because at that point you're paying for hours that go nowhere in particular, and you usually can't say where. That's not a people problem, it's a visibility problem, and it's fixable (more on that below).For honest context, industry benchmark research from SPI, reported by Deltek, found that professional-services firms averaged 68.9% utilization in 2024, after three straight years of decline. So if your first real measurement lands below 70%, you're not an outlier. You're average. The interesting question isn't "why is it low?" but "where do the missing hours actually go?" And you can't answer that until you categorize non-billable time.

One more nuance, because this trips up teams comparing numbers across tools: the right target depends on which utilization you're looking at. A scheduled-capacity target can sit higher than a billable target, because scheduled utilization includes legitimate non-billable work. In our own planning guidance we suggest scheduling toward roughly 90% of a team's capacity, keeping about a 10% buffer for the unplanned. That 90% is a scheduling target. It doesn't contradict the ~80% billable target; they're measuring different things. Put them side by side as if they were the same metric and you'll conclude your team is simultaneously overbooked and underperforming, which helps nobody.

Can Jira measure resource utilization on its own?

How do you improve a low utilization number?

• Fix the availability data first. If holidays, vacations, and part-time schedules aren't in the system, every utilization number downstream is fiction. This one step alone usually moves the reported number several points, because people who were "underutilized" turn out to have been on leave.
• Categorize before you cut. A team at 65% isn't lazy; its hours are going somewhere you can't see. Mark non-billable work honestly for a month before deciding anything. Tracking non billable utilization separately from revenue generating work is what reveals where time really goes. Often the finding is 20% of capacity going to internal ceremonies, and that's a calendar decision, not a performance one.
• Rebalance across teams, not within them. The overloaded team and the underutilized one usually exist in the same company at the same time. Cross-team visibility is what lets you move work sideways instead of pressuring the busy team to somehow log more, which leads to more efficient resource allocation, better workload distribution, and more proper utilization.
• Use the forecast to fill gaps ahead, not to punish gaps behind. Last month's 68% already happened. Next month's 68% is still negotiable, if you can see it coming.
• Set the target per metric. ~80% billable, up to ~90% scheduled, and say so out loud, so nobody quietly chases 100% of anything. Resource utilization vs capacity utilization is a useful distinction here, because they are related metrics but not interchangeable.