Plan and manage resources
In the app: Planning → Resources (Register · Staffing) · Team → Workload
PMP ECO · Process (41%) · Task Pr4. Get the right people and physical resources, in the right quantity, at the right time, and keep each one within what it can actually do.
What it is
Resources are both human (the team, crews, subcontractors) and physical (equipment, materials, facilities). Managing them runs from planning to control:
- Plan how resources will be estimated, acquired, developed and controlled.
- Estimate what the work needs: the resource register lists each resource, its quantity, and the window it's needed in.
- Acquire them: hire, assign or contract the people; order or rent the equipment.
- Develop and manage the team (the People domain lessons cover this).
- Control: compare what is planned for each resource, week by week, with what that resource can deliver, and fix the gaps before they happen.
Over-allocation is when a resource is planned for more work in a period than it can do. It's a question about time: a crew can look comfortable over three years and still be booked at 140% for four months. Two techniques resolve it:
| Resource smoothing | Resource levelling | |
|---|---|---|
| What it does | Moves work only within its float | Adjusts start and finish dates to match the resource's availability |
| Critical path | Unchanged | Can change |
| Finish date | Never delayed | Can be delayed |
| Catch | May not resolve every clash | May cost time |
Why it matters
- Over-allocation is silent until the week it bites. The same crew booked on two jobs at once doesn't show up as a cost or a date. It shows up as a slip.
- Physical resources constrain the schedule as hard as people. Two tower cranes shared by the frame, the cores and the facade lifts can limit progress more than any crew.
- The cheapest fix is the early one. A clash found three months out can be smoothed within float. The same clash found on the day becomes a delay.
Where you do it in VanillaPM
- Planning → Resources → Register is the demand list: people, equipment and materials, each with a quantity, unit, the window it's needed in, a rate, and why it matters.
- Planning → Resources → Staffing reconciles the people part of the register with who is actually assigned.
- Team → Workload opens with Resource clashes: every member who is over capacity in some week from today on, the work in those weeks, and for each task a verdict: Smooth (it has float; move it and the finish holds) or Level (it's critical; delaying it moves the finish, so add capacity or accept the delay through change control). Below it, the heatmap shows planned hours against each member's real capacity, week by week.
- Capacity is the same everywhere: crew size, availability, leave and staffing. The heatmap, the clashes and the integrated plan's check Resource plan can staff the schedule (Pr1) all read the same numbers.
Free download: RACI matrix template (Excel, CSV).
Walked example — Coral Ridge Resort
The register holds five resources: two crews (the main contractor's ~180 people and the MEP subcontractor's ~45), two tower cranes, the piling rig and 18,000 m³ of marine-grade concrete. Each has the window it's needed in: the piling rig was released in May once the load tests passed.
Looking ahead, two crews clash with their capacity:
- The site crew, January 2027 (117% at peak for three weeks). The basement water-tightness remedial works landed in the same weeks as the RCC frame. The remedial works have 768 days of float, so they can be smoothed: move them past the frame, and the finish date holds.
- The design and fit-out crew, December 2027 to April 2028 (143% for 17 weeks). The sea-view fit-out is planned faster than the crew can work, and it's on the critical path. There's no float to smooth into, so this one is levelling: stretch it and the finish moves, or add a second fit-out crew. That decision goes to the change control board.
The workspace — the theory behind each screen
Every screenshot is the actual sample project, not a mock-up.
1 · The resource register: what, how much, and when
The theory: estimating activity resources. Every resource the work needs, of every type, with a quantity and the window it's needed in. The window is the part people skip, and it's the part that finds clashes: a resource is needed then, not just at some point.

Reading the screenshot: Equipment: one piling rig (February to May 2026, released after the load tests) and 2 tower cranes (August 2026 to December 2027), shared by three trades, so crane time is booked per week. People: the two crews, each staffed as one subcontracted unit, with a crew-day rate. Material: 18,000 m³ of marine-grade concrete from two batching plants, so one breakdown can't stop a pour. Each line says why it matters.
✅ Do give every resource a window, not just a quantity.
❌ Avoid planning only people. Equipment and materials have lead times and limits too.
2 · Resource clashes: smooth if you can, level if you must
The theory: resource optimisation. When planned demand exceeds a resource's availability in some period, adjust the schedule. Smoothing stays within float, so the critical path and finish don't change, though it may not clear every clash. Levelling adjusts dates to match availability and can move the critical path and the finish.

Reading the screenshot: two crews over capacity in coming weeks: Farah Karim's crew, 17 weeks at up to 143% (150.6 h planned against 105 h); Imran Hossain's crew, 3 weeks at up to 117%. Then the work in those weeks. Basement water-tightness remedial works: Smooth · 768 d float: move it and the finish holds. RCC frame floors 1–5 and Guest-room fit-out: Level · critical: no float, so delaying them moves the finish. Add capacity or take the delay through change control. The card only advises; it never changes dates or assignments itself.
✅ Do smooth first. It's free in time.
❌ Avoid "fixing" a clash by delaying a critical task without telling anyone. That's a
schedule change, and it needs a decision.
3 · The heatmap: capacity is per resource, per week
The theory: control resources. Compare planned (and later, actual) use against each resource's real availability over time. A crew of 180 doesn't have the capacity of one person, and someone staffed half-time here doesn't have a full week to give.

Reading the screenshot: January 2027. Imran Hossain's crew: 180.8 h planned in the weeks of 4, 11 and 18 January (red), against a capacity of 155 h. That's the remedial works stacked on the frame. From 25 January it falls back to 122 h and then 107 h (green): once the remedial works are moved, the peak disappears. Capacity here is each crew's own: crew size, availability and staffing, not a flat 40-hour week.
✅ Do look forward, week by week, at least a few months ahead.
❌ Avoid judging allocation by totals. "40% utilised over the project" can hide a month at 140%.
Best practices & pitfalls
- Do know the split: smoothing stays within float and never delays the finish; levelling can delay the finish and change the critical path.
- Do plan long-lead physical resources as early as the team. They're often the real constraint.
- Do measure each resource against its own capacity: crew size, part-time staffing, leave.
- Pitfall: over-allocation hidden in averages. Look at the peak weeks.
- Pitfall: treating a clash on the critical path as a scheduling detail. It's a decision about the finish date.
On the PMP exam
Resource levelling vs smoothing is a favourite: levelling can extend the schedule and change the critical path; smoothing works within float and doesn't. Know that resources are human and physical, the resource calendar (when a resource is available), and the acquire → develop → manage team flow. Scenarios often describe a key resource assigned to two activities at once: the best answer resolves the over-allocation, first within float, and if the finish must move, through change control with the impact made visible.