Resource management is consistently one of the hardest parts of SPM to configure well. The workspace gives you visibility into who is allocated to what and at what capacity — but getting to that view requires a specific setup that many implementations skip or rush.
This guide covers the Resource Management workspace: what it shows, the concepts you need to understand before touching the configuration, and the most common reasons implementations end up with unusable utilisation data.
What the Resource Management workspace does
The Resource Management workspace is the primary view for capacity planning in ServiceNow SPM. It lets resource managers see:
- Who is allocated to which projects and tasks
- How much of each resource's capacity is consumed (utilisation rate)
- Where there is surplus capacity or overallocation
- How planned allocation compares to actual time worked
It is built around two related but distinct concepts: allocation and utilisation.
Allocation vs utilisation — why the distinction matters
| Term | What it means | Where it comes from |
|---|---|---|
| Allocation | The planned percentage of a resource's time assigned to a project or task | Set by the resource manager or project manager in the resource plan |
| Utilisation | The actual percentage of time a resource has worked on project activities | Calculated from time sheet entries (requires Time Card module) |
Most implementations start with allocation-only visibility. Utilisation requires the Time Card module to be active and resources to submit timesheets — which is a separate change management challenge.
Common trap: Teams report 100% utilisation on all resources but never reconcile it with actual deliverables. Allocation without timesheet discipline gives false confidence. The workspace shows what was planned, not what was worked, unless Time Card is running.
Planning attributes — the key concept most guides skip
Planning attributes are the common currency of resource management in modern ServiceNow SPM. They are configurable properties — role, skill, team, location — that link the supply side (resources) to the demand side (project requirements).
When a project manager says "I need a Business Analyst for 50% of their time", they're requesting a resource with a specific planning attribute. The Resource Management workspace matches that need against available resources who have that same planning attribute configured on their profile.
Without planning attributes properly configured on both resource profiles and project requirements, the matching system has nothing to match on — and you end up managing allocation manually by name, which defeats the purpose of the workspace.
The capacity planning workflow
A working capacity planning process in ServiceNow SPM follows this sequence:
- Resource profiles set up — every managed resource has their capacity (% available) and planning attributes configured
- Project resource plans created — each project has a resource plan specifying the planning attributes and time allocations needed
- Allocation requests submitted — project managers request specific resources or resource types
- Resource manager reviews requests — in the workspace, they can see total demand vs available supply, by planning attribute
- Allocation confirmed or negotiated — resource manager approves, rejects, or proposes alternatives
- Timesheets submitted (if Time Card active) — resources log actual hours, creating the actuals layer
What typically goes wrong
Resource profiles aren't maintained
If resource profiles don't have accurate capacity and planning attributes, the workspace shows garbage. Keeping profiles current requires either a process for HR to update ServiceNow or an integration with the HR system. This is often an afterthought.
Resource plans are created too late
Resource planning should happen at demand approval or project initiation — not mid-execution. Late resource plans mean the workspace never had a chance to surface the conflict before resources were already committed.
Time Card adoption is low
Utilisation is only as good as timesheet compliance. Without executive sponsorship for timesheet submission, actual vs planned data never materialises. Allocation without actuals is a planning fiction.
Zurich and Australia release changes
The Zurich and Australia releases (June 2026) brought updates to the Resource Management workspace including improved planning attribute filtering and performance improvements in large resource pools. Module 5 of SPM Mastery covers these changes in the CURRENT context.
Module 5 covers this in full
SPM Mastery Module 5 (STAFF) walks through resource management, time tracking, and capacity planning with hands-on quiz questions and flashcards. Free with your email.
Start SPM Mastery free →