ServiceNow Resource Management Best Practices

This page sets out the resource management practices that match people to projects: capacity planning, skills inventory, allocation, utilization tracking and succession planning. It is written for resource managers and portfolio owners who must decide who works on what.

Capacity Planning and Resource Forecasting

Start the year with a capacity plan. For each team or skill set, define the number of people available and their typical utilization rate (for example, a developer might spend most of their time on project work, with the remainder spent on support or training). Calculate available capacity: if you have 10 developers and each dedicates the majority of their time to projects, you have a strong available capacity for project work. Forecast demand: how much development work do your planned projects require? If demand exceeds capacity, you have three options: reduce project scope, add resources or extend timelines. Plan this at the beginning of the year to avoid resource surprises mid-year.

Skills Inventory and Competency Tracking

Maintain a skills inventory in ServiceNow. For each employee or contractor, record primary skill (job role), secondary skills (expertise areas), skill level (junior, mid, senior), and certification status if applicable. Update skills inventory annually and when employees gain new certifications. Use this to match project requirements to available skills: a project needing a senior database administrator can query the inventory and find available candidates. Identify skill gaps: if projects need SAP expertise but no one has it, plan to hire, train or contract SAP expertise.

Resource Allocation and Contention Management

When projects are approved, allocate resources. Create a resource plan for each project: what roles are needed, for how long and at what utilization level. Use ServiceNow to assign resources to projects. Monitor for conflicts: if the same person is allocated to competing projects simultaneously, flag the conflict and have portfolio management decide which project has priority. Aim for clear assignment: each person should know who they report to during their project assignment. Avoid matrix assignments (person reports to both their manager and project manager) when possible; when matrix assignments are necessary, define decision rights clearly so the person knows whom to escalate to when conflicts arise.

Utilization Tracking and Efficiency Metrics

Track utilization monthly. Planned utilization shows what was expected (resource allocated to a project at a certain level); actual utilization shows what was achieved (tracked via timesheet or project management system). If actual utilization falls significantly below planned, the resource is underutilized (available capacity is idle). If actual utilization substantially exceeds planned, the resource is overutilized (working more than expected, risk of burnout). Investigate variances: why is the resource underutilized? Is project demand less than expected? Can the resource be moved to another project? Why is the resource overutilized? Is scope creep occurring? Can scope be reduced or additional resources added?

Resource Leveling and Workload Balancing

When multiple projects compete for limited resources, use resource leveling to smooth the workload. Identify periods when resource demand exceeds supply (bottlenecks) and periods when demand is light. Shift lower-priority work to light periods and high-priority work to periods with available capacity. For example, if April has 3 projects competing for the QA team and August has only 1 project, delay non-critical testing to August. This reduces bottlenecks and improves resource efficiency.

External Resources and Vendor Management

When internal capacity is insufficient, use contractors or vendors. Maintain a vendor list: contractors available for short-term projects, outsourced service providers for ongoing work. For each vendor, track: skills, cost rate, availability, contract terms and performance history. When engaging a vendor, define the scope clearly and include in the contract the skill level (junior, mid, senior) and expected delivery. Use the same resource planning process: allocate vendor resources to projects and track utilization. Manage vendor performance: if delivery is late or quality is poor, address it formally in the vendor relationship.

Pipeline and Succession Planning

Plan for resource transitions. When a key person will retire or move to a different role, start grooming a replacement well in advance. Use project assignments to develop junior staff: assign them to projects where they work alongside more experienced staff and gain experience. Track bench resources (people between project assignments): use bench time for training, skill development and special projects. Plan for seasonal or cyclical demand: if demand is high Dec-Feb and low June-Aug, plan hiring and training during the slow season so staff are available for the busy season.

Where the practices break first in a live resource pool

Many resource practices look sound on a slide and fail in the first busy month. The breakpoint is rarely the forecast itself. It is the moment a manager has to choose between two requests that both look urgent and neither carries a recorded priority. When the pool has no agreed answer to that question, people start allocating informally, the records drift away from reality, and the next forecast is built on figures nobody trusts. Before adopting any of these practices, a resource manager should ask who makes the call when two commitments collide and where that decision gets written down.

A second breakpoint is skills data. A capacity view is only as useful as the skill tags behind it. When a project asks for a senior integration engineer and the pool holds a large group of people all tagged simply as developers, the search returns nothing useful and the manager falls back to a phone call. Skills work should therefore start from the requests the pool has actually received over the last few cycles, not from a complete taxonomy designed in a workshop. Tag the skills that appear most often in those requests first, then extend the list as new requests arrive.

A weekly review that keeps the forecast honest

A forecast reviewed once a quarter drifts for the whole quarter. Teams that get lasting value from resource management tend to run a short weekly review that compares what was planned with what happened. The review does not need a long meeting. The order below works because each step feeds the next, and the review never starts with opinions about individuals.

1. List the allocations that were due to start or end in the past week, and mark which ones changed in the system and which changed only in conversation.
2. Check every project with an open resource request and record whether it has been fulfilled, is queued, or has been withdrawn.
3. Compare planned hours with logged time for the people with the widest gaps, and write one sentence explaining each gap.
4. Pass any conflict the resource managers cannot settle in the room to the portfolio owner, together with the two competing requests and the date each one is needed.
5. Update the forecast for the coming weeks only after the changes above are recorded, so the forecast starts from the corrected state rather than from the previous assumption.

Choosing between deferring, hiring, contracting and reshaping scope

When demand exceeds the pool, the practical question is which lever to pull. The answer depends on how long the gap will last and how scarce the skill is. The table is a starting point for that conversation. It is not a rule to apply mechanically, because a contractor who arrives late can cost more than a short, well-managed delay.

Signs the practices are working

Good practice shows up in how people behave inside the system, not in the number of dashboards that exist. Look for these signs over a sustained period before concluding that the practice has taken hold.

• Requests are raised before work begins, rather than after a developer has already started on the task.
• Planned and logged time move broadly together, and the explanations for gaps are short and specific.
• Managers can name the open conflicts in the pool without opening a separate spreadsheet.
• Contractors carry the same allocation records as employees, so the cost and capacity picture is complete.

When not to apply the full practice set

Consider a hypothetical team that supports one internal platform and has the same people in every week. A full forecasting cycle would take more attention than it returns. In that case a shared calendar of planned work and a monthly comparison against logged time is often enough. The formal practices earn their cost when the pool grows, when several projects start competing for the same people, or when a sponsor asks for a forecast that the team cannot produce from memory. Adopting the whole set early tends to produce a large amount of data that nobody reads.

Follow-on questions from resource managers

Should people being reviewed attend the weekly review?

Usually not for the whole review. The review is about the state of allocations and requests, and it works best when resource managers and project leads run it. Individuals can be asked for context on a specific gap afterwards, in a short one-to-one conversation. Keeping individuals out of the main room stops the review turning into a search for who to blame.

What do we do when only one person can do a critical task?

Treat it as a risk to be recorded, not a scheduling puzzle to be solved each week. Name the task and the person, note what happens if that person is unavailable, and decide whether the answer is a planned backup, a contractor with a handover, or a reduction in the scope that depends on them. The forecast should show the dependency so the sponsor can see it before a crisis does.

Do contractors belong in the same forecast as employees?

Yes, for planning purposes. A contractor’s time is still capacity, and leaving them out makes the forecast look healthier than the delivery will be. Keep the cost and the contract terms separate from the allocation record, so the capacity view stays clean and the finance view stays accurate.

How far ahead should the forecast look?

Far enough to cover the lead time for a hire, a training course or a contract to take effect, and no further than the portfolio can describe with reasonable confidence. Beyond that point the forecast is a guess presented as a plan. Revisit the horizon whenever the portfolio changes shape.

Talk through your resource practices

If your pool is growing faster than your review process, a short working session can help you decide which practices to adopt first. Bring a sample of the last few months of requests and allocations so the discussion starts from your own data. For the wider design, start by deciding who decides each resource question, then phase the work using the implementation roadmap. The capacity planning article covers signals that point to a capacity problem and is a useful check before the first review cycle.