Learning path
Step 5 of 5 in Learning path: Manage skills, people and capacity, leg 3 of 3: Read the load. That completes Get going: back to the path page for what comes next.
Applies to
| Property | Value |
|---|---|
| Product | LYNX-X |
| Version | 28.10.9800.0 |
| Required permissions | None (read access to the portfolio) |
| Last updated | 2026-09-01 |
| Owner | Support |
Overview
The resource load view in Project Portfolio gives a cross-project picture of demand on a skill: how loaded it is on average, which projects are driving that load, and, when unfolded, which individual resources are carrying it.
Open it from Portfolio, then Res. load in the left rail. Each skill gets a row: its figures on the left, its load over time on the right.
Before reading any of the graphs, open Options and check Scaling. Each skill's vertical axis runs to its own maximum, so two graphs that look similar are not comparable until you know what the percentages are a percentage of.
Fields
| Field | What it shows |
|---|---|
| Average, Working hours, Unallocated | The skill's totals for the period shown. Unallocated goes negative when the skill is committed beyond its availability. |
| Avg. load | The skill's average load across the window, as a percentage of whatever Scaling is set to. |
| Per-project breakdown | The info control on the skill's header row opens a table of work and average load per project. The next click closes it. |
| Drill-down (people icon) | Opens the skill into the individual resources behind it. Skills with no resources behind them (Virtual skills) have no people icon. |
| Non-working periods | Drawn as a hatched band over the affected weeks, on the resource's row only. |
| Red line | The line on top: the assignments on critical tasks in that period. |
| Blue line | The thicker line: the capacity. It sits at a different percentage on each skill because each skill's capacity differs. |
| Hard assignments (toolbar) | Shows only committed (hard) assignments, not the resources LYNX-X suggests. Use it to check what a specific resource is really committed to, now and in future periods. A suggestion stays until someone changes it or the task is started; once the task starts, the resource is hard-assigned. |
The per-project breakdown
A skill can look comfortable in aggregate and still be over-committed on one project. Designer below averages 96% on T1 alone, before D1 and D2 are counted at all.
Drilling into the resources
Selecting the people icon beside a skill replaces the list with that skill and the resources behind it. This is where a resource's non-working periods appear.
Note
The band is drawn on the resource's row, never on the skill's row above it, even when the skill has exactly one resource, as Designer does here.
Notes
Use this view to see how one skill is loaded across everything currently planned, and which resources and projects carry that load.
See also
- Setting a resource's non-availability period
- How non-working periods affect the critical chain
Revision history
| Version | Date | Author | Changes |
|---|---|---|---|
| 1.0 | 2026-09-01 | Support | New article. |
| 1.1 | 2026-10-01 | Support | Explains the red line, the blue line and the Hard assignments mode. |
Comments
0 comments
Please sign in to leave a comment.