Resource Capacity Plannin
Allocate people to projects, track utilisation %, flag over-allocation
Planning who works on what in spreadsheets means nobody really knows who is over-booked until a deadline slips. This board allocates named hr.employees to projects (and tasks) for a date range at a percentage of their capacity, computes available and allocated hours straight from each person's working calendar, and flags over-allocation the moment overlapping confirmed bookings exceed 100%. Bulk-assign a whole team, rebalance an over-booked resource by trimming or scaling, and read an eight-week heat board — all on Community Project and HR, a real alternative to Enterprise Planning for PMOs, agencies and professional-services firms.
Key Features
Resource allocations with lifecycle
gb.resource.allocation books an hr.employee onto a project.project (and optional project.task) for a date range at a chosen capacity_percent. It runs draft to confirmed to done/cancelled via action_confirm, action_done and action_cancel, with every change tracked on mail.thread chatter.
Calendar-accurate hours
_compute_hours_per_day reads each employee's resource_calendar_id, and _compute_period_hours counts only weekday working days in the period. available_hours and allocated_hours (available × capacity_percent) reflect real availability, not a flat 8-hour assumption.
Real over-allocation detection
_committed_percent_on_period sums the capacity_percent of every confirmed/done allocation of that employee whose dates overlap, exposing overlap_percent and the is_over_allocated flag. _recompute_peers re-runs on every create/write so sibling flags stay consistent, and confirming an over-booked allocation posts an alert.
Colour-coded board and overlap drill-down
_compute_color paints each allocation red (over), yellow (90%+) or green so the kanban reads at a glance. action_view_overlaps opens exactly the confirmed allocations clashing with the selected one, so a planner sees who else holds the resource.
Bulk allocate a whole team
gb.bulk.allocation.wizard assigns many hr.employee records to one project for a window at a per-person capacity_percent, optionally auto-confirming. Tick 'skip if it would over-allocate' and it checks committed capacity per resource and posts the skipped names to the project chatter.
Rebalance an over-booked resource
gb.rebalance.wizard pulls a person back to a target_percent using two strategies: trim_latest cancels or trims the most recent allocations until the excess is gone, while scale_down proportionally shrinks every active allocation. The result is logged on the employee.
Weekly capacity board with heat
gb.capacity.week.generate_board materialises per-employee, per-week lines, pro-rating each allocation's hours into the weeks it spans via _hours_in_week. committed_percent drives a heat flag (cold/ok/hot/burn) for a list-and-pivot board spanning eight weeks ahead.
Utilisation snapshots and cron alerts
gb.capacity.snapshot.build_for_employee rolls a 28-day window into available, allocated, free hours and a utilisation status (under/healthy/full/over). The weekly cron_build_snapshots job rebuilds snapshots for actively-booked staff, while hr.employee gains current_utilisation and is_over_allocated_now fields.
Use Cases
Screenshots
Bulk Allocate Team
Utilisation Board
Weekly Capacity Board
Rebalance Resource
Allocations
Why Choose This Module
Resourcing in spreadsheets means nobody really knows who is overbooked until it's too late. This module allocates named employees to projects for a date range at a percentage of their capacity, computes utilisation from each person's working calendar, and raises over-allocation alerts when committed capacity exceeds 100% — a Community alternative to Enterprise Planning.
Specifications
- Compatible: Odoo 18.0 / 19.0
- License: OPL-1
- Languages: English
- Author: Pokutsoft
- Dependencies: project, hr
- Support: support@pokutsoft.com
Update date: 2026-07-02