Resources
Spot overload early
Each resource has a capacity in percent and an hourly rate. You record the allocation per task. The sum per person is checked live against 100 % — overload appears as a visible warning before bottlenecks become a problem.
Capacity & hourly rate
Configurable per person
Every resource has a capacity (0–100 %) and an hourly rate in EUR. Part-time at 60 %? A freelancer on a specific rate? All maintained in the resource module, no custom field engineering required.
- Capacity in percent steps (10 %, 25 %, 50 %, 75 %, 100 %)
- Hourly rate in EUR — for project cost and forecast
- Optionally overridable per project (client rate ≠ internal rate)
- Role as free text plus tag — visible in the utilisation report
Overload warning
When the sum > 100 %, it lights up red
The `ResourceUtilizationView` aggregates all task allocations per person. If the sum exceeds 100 % for a week, a red warning appears with a click-through to the specific tasks.
- Weekly aggregation — more precise than a plain “capacity × days” calculation
- Drill-down: which tasks in which week cause the overload
- Simulation: add a resource to task X and see the live effect
- Export utilisation history as CSV for HR conversations
View per role
What each role sees
Project lead
Full resource view including hourly rates, overload warnings, allocation history.
Team member
Own utilisation, own tasks. No hourly rates of others, no cross-project overview.
Administrator
Everything. Plus billing context: resource cost flows into the project forecast.
Demo
Team utilisation at a glance
In the demo we set up your team structure with three real projects and show the utilisation report. Afterwards you know whether the team can really take on another project in six weeks.