b2KIT

Resource Allocation Planner

Plan resource allocation across projects with capacity heatmaps, over-allocation alerts, and utilization dashboards.

Tested tool guide Tested browser tools Checked August 16, 2026

What Resource Allocation Planner does, with a checked example

You enter each team member's weekly capacity (full-time hours, part-time, or reduced for time off), plus the hours assigned to each project, and the planner sums those assignments per person per week, compares them to capacity, and renders the result as a capacity heatmap, over-allocation alerts, and utilization dashboards. The number people most often misread is utilization: it is assigned hours divided by capacity, so it can exceed 100 percent, and a person sitting at 100 percent has no hours left for anything new.

Worked example

A concrete input and expected output from the current implementation.

Input

Team member: Maya Chen. Capacity: 40 h/week. Assignments for the week of 2026-08-17: Project Atlas 20 h, Project Beacon 15 h, Project Cirrus 10 h.

Expected output

Assigned 45 h vs 40 h capacity: over-allocated by 5 h; utilization 45/40 = 112.5%. An over-allocation alert is raised for Maya Chen, week of 2026-08-17, and her heatmap cell is marked as over capacity.

Utilization is assigned hours divided by capacity (45 / 40 = 1.125), so it can exceed 100 percent. The alert reports the 5-hour excess (45 - 40), which is the amount to move elsewhere when rebalancing.

How the result is produced

1

Capacity versus demand per person per week

Every team member has a weekly capacity you set, usually hours per week, reduced for part-time schedules or time off. The planner sums the hours assigned to projects for each person in each week and compares the total to capacity. Any week where assignments exceed capacity is over-allocated and generates an alert; utilization is assignments divided by capacity, so it can read above 100 percent.

2

Heatmap and utilization dashboard

The heatmap lays people and weeks out as a grid of cells colored by utilization, with over-allocated cells visually distinct from at-capacity and under-utilized ones, so overload weeks are visible at a glance. The dashboard rolls the same numbers up into per-person, per-project, and per-week utilization percentages, which is what you take into planning meetings.

Good uses

  • Before accepting a new project, checking which team members still have capacity this quarter and who would tip past 40 hours.
  • When a project slips by two weeks, scanning the heatmap of the coming weeks for anyone over-allocated so work can be shifted before overtime builds up.
  • Building a monthly per-person utilization view for a staffing review, to spot people running well under target who could take on more work.

Limits and checks

  • The results are only as accurate as the hours entered. Unlogged work, meetings, and admin time that never become assignments do not show in the heatmap, so real load can sit well above the utilization number.
  • A cell at 100 percent is not a good result; it means zero slack for unplanned work or slippage. Anything above 100 percent is over-allocation, flagged by the tool rather than celebrated as efficiency.
  • Weekly granularity cannot see day-level conflicts. Two 20-hour assignments in one week pass the capacity check at exactly 40 hours but may be needed on the same days, which hours alone cannot reveal.

Common questions

What utilization should I plan people at?

There is no universal number. 100 percent leaves no slack for unplanned work or slippage, so many teams plan below it and treat the heatmap's over-capacity cells as a hard stop rather than a suggestion. The tool computes and flags; the target percentage is a policy decision you make per team or per project.

Does the planner move work automatically when someone is over-allocated?

No. Its job is to surface the over-allocation and show where spare capacity exists; moving hours is your decision. Before reassigning, confirm the person has the needed skills and that the receiving week still respects their other commitments, since the tool works only from the hours you enter.

References and verification

The example and behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.

Related Tools