Resource allocation
KPIs at the top work as filters and every cell leads to the details.
- Views: allocation, availability, by project, by team and by resource
- Search including by skill, and saved views
- Export that respects filters and permissions
Execute
Resources and capacity: Visible capacity before overload turns into delays.
- The problem
- The same people are on several projects. The average allocation looks acceptable, but a one-week peak sinks the deadline, and the conflict only shows up when it’s too late.
- With LUWEE
- Allocation is read by person, team and project, with peaks shown beyond the average. Conflicts become units of work, resolved with the impact calculated before applying.
How it works
The flow, step by step.
- 01
Register resources
People and resources with skills, categories, organizational unit and hourly cost.
- 02
Assign to activities
Allocation percentage, including fractional values, directly in the schedule.
- 03
Read the workload
Five allocation views, by day, week or month, always with the peak next to the average.
- 04
Resolve conflicts
In leveling: delay, swap, replace using an explainable ranking, or split the allocation.
- 05
Compare consumption
Planned × actual by person, activity, company and unit.
Key features
What makes the difference day to day.
Resource leveling
A complete workspace for resolving overload with the impact in view.
- Before × after workload and impact Gantt
- Consolidated impact on finish date, milestones, critical path and cost
- Asks before publishing; never publishes on its own
Resource consumption
What was planned compared with what was actually consumed.
- By person, activity, company and unit
- Comparison with the previous period
- Actuals from time entries when the project uses Time Sheet
Cross-module integration
How it connects to the rest of the platform.
Who it’s relevant for
Functional managers
Know who is overloaded and who has room.
Project managers
Resolve conflicts with the schedule impact calculated.
PMO
Balances capacity across projects with data.
FAQ
Before the demo.
Why show the peak and not just the average?
Because a monthly average hides the week when someone is at 160%. LUWEE shows the peak next to the average at every granularity.
How does the system suggest replacements?
In the conflict resolution menu, the replace option provides an explainable ranking of people, plus suggestions for unassigned activities.
Does leveling change the schedule automatically?
No. You review the decisions before applying and, when you apply, LUWEE asks whether to publish. Nothing is published without confirmation.
Explore other modules
View the whole platformDemo
See LUWEE applied to your challenge.
Tell us how your organization works today. We’ll show you Resources and capacity with the platform’s real screens and how the module connects to the rest.
- Led by the challenge you point out
- With people who know the product inside out
- No purchase commitment