ServiceNow Field Service Management for Professional Services

Field Service Management in a professional services firm is dispatch for consultants: who goes on site when the plan changes, and what that does to billable utilisation and travel. This page covers project scheduling and milestone management, utilisation and revenue impact, skills inventory and capability management, travel and expense tracking, client satisfaction, a decision table for common dispatch situations, an ordered procedure for a mid-week reassignment, where dispatch decisions go wrong, and when field service scheduling is not the right layer.

Project scheduling and milestone management

Professional Services projects have defined phases: discovery, design, implementation and delivery. Field Service should track project phases and schedule consultants to the phases they are assigned to. As projects progress through phases, consultant assignments may change based on phase requirements.

Project milestones affect consultant scheduling. If a project milestone is at risk due to resource constraints, Field Service should surface this risk to resource managers. Resource conflicts should be identified and resolved through negotiation or prioritisation.

Project staffing plans define which consultant roles are needed in each project phase. Field Service should match project staffing plans to available consultants. Gaps between planned staffing and available resources should trigger hiring or contractor engagement.

Billable utilisation and revenue impact

Billable utilisation—the percentage of a consultant’s time charged to clients—is a key profitability metric. Field Service should track utilisation rates by consultant. Low utilisation may indicate bench time that needs to be addressed through new projects or internal work allocation.

Bench time represents unutilised capacity. When consultants are between client assignments, they may work on internal projects, training or skill development. Field Service should distinguish between billable work and internal work so that true utilisation is understood.

Consultant rates vary based on experience and specialisation. Senior consultants with scarce skills should be assigned to work that requires their expertise. More junior consultants can be assigned to lower-skill work. Field Service should optimise assignment to balance utilisation with appropriate utilisation of consultant skills.

Skills inventory and capability management

Professional Services competitiveness depends on having consultants with the right skills. Field Service should track consultant skills and certifications. When a project requires specific skills, Field Service can identify which consultants are qualified and available.

Skills development should be planned and tracked. New consulting methodologies or technologies require training. Field Service should surface opportunities for consultants to develop new skills and track certification completion.

Consultant certifications often have expiration dates. A consultant’s AWS certification may expire, requiring renewal for continued work on AWS projects. Field Service should track certification dates and flag expirations so that renewals are planned before expiry.

Travel and expense tracking

Professional Services consultants incur travel and client expenses. Field Service should integrate with expense management so that consultants can report expenses for client assignment. Travel time, accommodation and client meals should be tracked separately from billable consulting time for accurate cost accounting.

Travel billing may be passed through to clients separately from consulting fees. Field Service should track billable versus non-billable travel so that client invoicing is accurate.

Client satisfaction and engagement management

Client relationships depend on consultant performance and engagement. Field Service should track which consultants are assigned to which clients and their engagement history. Client preferences for specific consultants should be noted and applied to future assignments when possible.

Deciding who goes on site when the plan changes

Scheduling a consultant onto a client site is easy when the plan holds. The harder decisions come on a Tuesday afternoon, when a client moves a workshop, a senior consultant falls ill, or a second client asks for the same specialist. At that point the delivery manager is choosing between a few imperfect options, and each one carries a cost in travel, client trust and billable time. A field service design should make those trade-offs visible before the decision is made, rather than leaving the choice to whoever answers the phone first.

This section is for delivery managers and resource planners who dispatch consultants to on-site work. It assumes that skills records, client contact details and project phases already exist, even if they are maintained loosely. It is less about how the scheduling screens look and more about the decisions the screens have to support. The field service roles and responsibilities guide is a useful companion for deciding who approves each type of dispatch. For the wider sector context, see the professional services industry page.

A decision table for common dispatch situations

The point of the table is that every option has a check attached. A substitution that breaks a client’s access restriction is not a saving; it is a contract problem that appears a week later. Write the check into the dispatch record so the approver sees it at the moment of decision.

An ordered procedure for a mid-week reassignment

1. Record the reason the original visit is changing, with the time it was known. The timing matters later when a client asks why notice was short.
2. Pull the list of consultants with the required skill and an active client access approval for that site, and remove anyone the client has restricted.
3. Estimate the travel time from each candidate’s current location, including the time to reach the site and return, and compare it against the billable window available.
4. Get the approver’s decision in the same record, then send the handover note to the new consultant with the open points from the previous visit.
5. Update the project phase and staffing plan so that the change does not reappear as a gap in next week’s forecast.

Where dispatch decisions go wrong

A common problem is stale skills data. A consultant recorded as expert in a platform who has not used it for a year is a poor choice for a complex on-site fix, but the scheduling view shows no reason to doubt the record. Require skills to be re-confirmed when a consultant leaves a project, and treat a skill with no recent evidence as unconfirmed.

The second problem is an override that bypasses the client’s preferences. Delivery managers under pressure sometimes assign whoever is free, and the client finds out when their nominated consultant is later asked to attend a review they were not told about. Keep client preferences on the client record and make the override require a reason.

The third is double-booked travel. A consultant assigned to two sites within the same afternoon, separated by a long drive, is unlikely to meet either commitment. The dispatch view should show travel time between assignments, not only start and end times. To keep those handovers visible, see the field service case coordination article.

When field service scheduling is not the right layer

Where most delivery is remote and on-site visits are rare, a simple request and approval flow may be enough, and a full dispatch layer adds maintenance without much return. The reverse also holds: a firm that sends many consultants to client premises every week will feel the cost of informal dispatch quickly. Decide based on how often the dispatch decision is made and how much a wrong choice costs the client relationship.

Frequently asked questions about on-site dispatch

Should travel time count as billable?

That depends on the commercial terms agreed with each client, not on the scheduling tool. The dispatch record should show travel time separately from working time, so that finance can apply the agreed rule consistently and the delivery team can see the real cost of a choice.

How far ahead should a client access permit be requested?

Ask the client’s site contact for their own lead time, because it varies with building security and sponsor availability. Once the lead time is known, the dispatch view should flag any assignment that falls inside it, so the planner sees the risk early rather than on the morning of the visit.

What if the consultant the client wants is not available?

Offer the closest qualified alternative and explain what changes, rather than substituting silently. Some clients will accept a different consultant for a routine session but not for a decision meeting. The client record should hold that distinction so the planner does not have to guess.

Can remote delivery replace an on-site visit?

Sometimes, for analysis, configuration and review sessions. It is less suitable for physical checks, hands-on fault finding and sensitive discussions the client prefers to hold in person. Record the client’s position on this in the engagement, so the choice is not made case by case under deadline pressure.

Reviewing the dispatch decisions your team makes most often

Start with the decisions the delivery team makes most often in a normal month, and ask which of them still rely on memory.