ServiceNow Field Service Management for Public Sector

Field service management for a public body is the system that dispatches crews, records their time and parts, and keeps work orders defensible at audit. This page covers the records, stock, safety and service commitments that public crews need, and when field service is the wrong tool.

Field Service Management in a public body has to produce records that stand up to inspection: work orders shaped the way public crews operate, parts reconciled against stock, and safety and wage compliance that can be shown to an auditor. This page covers procurement and vendor records, asset and inventory control, health and safety standards, public accountability, service commitments, budget and cost control, work order types for public crews, which data is captured and by whom, an ordered approach to dispatch rules, and when field service is the wrong tool.

Public Sector Procurement and Vendor Management

Public sector organisations maintain detailed records of purchases and vendor performance. When a technician orders a part, the order must be documented: date, cost, vendor, reason for purchase. This documentation supports the audit trail and enables analysis of vendor performance (which vendors deliver on time, which have quality issues). Field Service Management records are more complete when part purchases stay traceable, whether through an integration with procurement systems or a manual step.

Prevailing wage requirements apply in some public sectors: field technicians must be paid the locally determined prevailing rate for their trade, which is usually above the general minimum wage (sometimes by government union agreements). Field Service Management should track whether work assignments comply with prevailing wage rules and whether labor costs are reasonable. A public manager can query: what is the average cost per field visit, how does this compare to budgets and to industry benchmarks?

Asset Management and Inventory Control

Public sector assets (vehicles, equipment, tools) are public property and must be tracked carefully. A technician is assigned tools when they start a shift and must return them at shift end. Inventory must be counted regularly and discrepancies investigated. Field Service Management integrates with asset management to track what equipment each technician has and what equipment is checked out or missing.

Public records laws mean that asset records may be disclosed publicly. Documentation should be clear and defensible. A missing tool is not a minor issue in the public sector; it must be investigated and documented because someone might eventually ask: where did that tool go, who was responsible.

Health and Safety Standards

Public sector work often involves higher safety standards than private sector work. Field technicians working on public infrastructure, in public buildings, or around hazardous materials must follow OSHA (or equivalent) standards. Work must be documented: what hazards were present, what safety measures were taken, what protective equipment was used. Field Service Management should capture this information so that safety records are available for inspection.

Stakeholders and Public Accountability

Public sector stakeholders are different from private sector stakeholders. Managers answer to elected officials, agency heads, or civil service leadership. The public (citizens who are affected by service) may be interested in service quality. Politicians may demand that service delivery is efficient and cost-effective. A public works department must be able to answer: how long does it take to fill a pothole, what does it cost, how does that compare to last year?

Field Service Management dashboards should provide transparency: work orders by district, average time to close a work order, average cost, citizen satisfaction (if you have feedback). Reporting should support democratic accountability: clear data that can be explained to the public.

Service Level Agreements and Public Commitments

Public sector organisations often make service commitments to the public. A water utility might commit to a response time for main breaks. A transportation agency might commit to a repair time for potholes after they are reported. These are public commitments, and failure to meet them can be politically damaging. Field Service Management must track whether commitments are being met.

Configure Field Service Management SLAs to match public commitments. When a work order is created, Field Service Management should show whether the SLA is being met. Escalate SLAs that are at risk of being missed so that work can be prioritised accordingly.

Budget Constraints and Cost Control

Public sector budgets are typically tighter than private sector budgets and are subject to legislative oversight. A department is allocated a budget for field service expenses (labor, parts, vehicles). Any significant overage requires justification and approval. Field Service Management should track costs against budget: how much has been spent this year, how much of budget remains, what is the projection for the full year? A manager who is at risk of overrunning budget should get alerts so they can take corrective action.

Compliance and Audit Documentation

Public sector compliance is different from private sector compliance. Public sector compliance means meeting regulatory requirements and statutory obligations. It often means being able to demonstrate that work was done in accordance with policy and that money was spent appropriately. Field Service Management should document the complete work lifecycle so that auditors can review and verify that work met standards.

Work order types that match how public crews actually operate

A field operations supervisor for a public works department does not manage one kind of job. Pothole repairs, streetlight faults, water valve exercises and inspections of a licensed premises have different skills, different safety requirements and different records that must be kept. Putting them all under one generic work order type makes reporting unreliable and forces crews to fill fields that do not apply to their work. Create a small set of work order types, each with the tasks, parts and safety checks that its work genuinely needs. Then review the list once a year, retiring types that are no longer used and splitting any type that has grown to cover two different kinds of job.

Each type should also name the default response expectation the agency publishes for it, so dispatch can see at a glance whether a job is nearing a commitment. Do not hard code a commitment into the type if the service owner has not confirmed it in writing.

Which data is captured, when, and by whom

Field work produces records in three places: the office where the job is raised, the vehicle where the work happens and the depot where materials are drawn. Data entered at the wrong point is either late or wrong. The table shows the usual split.

Time and parts are often entered at the depot at the end of a shift. That habit produces records that look complete but cannot be checked against the vehicle or the stores log. Where a crew cannot record on site, for example because coverage is poor, agree a short interval in which entries must be made and check adherence weekly.

Reconciling parts and tools against stock

Stock reconciliation is where public field teams are often caught out in an audit. A part is drawn from the depot, fitted on a job, and the job is closed, but the stock record still shows the part on the shelf, or the reverse. Tie each part issue to a work order, and make the closing step check that the parts recorded match the parts drawn. Run a periodic count of high-value tools and vehicle stock, and investigate any difference before adjusting the record.

The investigation matters as much as the adjustment. A recurring shortfall for one crew can point to a supervision issue, a faulty process or simply a part that is being fitted without being recorded. Treat the pattern as information about the process, not as a judgment on the individual.

An ordered approach to setting up dispatch rules

1. List the work order types and, for each one, the skills and crew size needed to complete it safely.
2. Map the depot locations and the areas each depot covers, using the boundaries the agency already publishes.
3. Set the assignment rule: nearest qualified crew with the required skill, and a rule for what happens when none is available.
4. Define the escalation point for jobs that will miss their response expectation, and name who receives the escalation.
5. Test the rules with a week of historical jobs and compare the assignments with what the supervisors actually did.
6. Turn on live dispatch for one district first, and widen it once the escalation list is short enough to act on.

Safety records that stand up to inspection

Work on public infrastructure often happens near traffic, in confined spaces or around hazardous materials. The safety record should show what was checked before the job started, not just that the crew signed a generic form. Attach a short checklist to each work order type, with the hazards that apply to that type pre-listed, and require the crew lead to confirm which ones were present. A checklist that is always ticked in full, whatever the site, is a sign that it is being completed for the record rather than for the job.

When field service is the wrong tool

Field service management suits planned and reactive work done by crews against a defined location. It is a poor fit for a large capital project run on contractor schedules and milestone payments, which needs project controls rather than dispatch. Nor should it replace the building permit or regulatory inspection process, where the legal record must sit with the regulator’s own system or the agency’s licensing function. Field service can receive the operational outcome of those processes, but it should not be the decision record.

Signs that the field model is serving the agency

• Crew time and parts are recorded on site for most jobs, and the exceptions are few and visible.
• Stock counts reconcile within the tolerance the stores team has agreed, and differences are explained.
• Supervisors can see jobs at risk of missing their response expectation before they miss it.
• Safety checklists show the hazards that were present on each job type, not a single template.

Questions from supervisors and finance teams

How should a job that uncovers a larger problem be handled?

Close the immediate work order with what was done, and raise a linked request for the larger problem so it is estimated and funded separately. Keeping the two apart stops a small repair from absorbing costs that belong to a capital decision.

Can crews use their own devices to record time?

Only if the agency’s device and data rules permit it, and the records remain under the agency’s control. Confirm this with the information security team before allowing it.

What happens when a crew cannot reach a job because of access restrictions?

Record the reason on the work order, return the job to dispatch with the restriction noted, and let the escalation rule decide whether the commitment clock should pause. The pause should be a recorded decision, not an unexplained change to the timer.

How do we report cost per visit without misleading comparisons?

Group visits by work order type first. A pothole repair and a major valve replacement are not comparable, and an average across both tells a budget holder very little.

Stock and time records are where field programs lose credibility, so reconcile a recent period of crew records against the store before rolling out dispatch rules. The field service management overview describes how work orders are assigned to field teams and tracked to completion. The request fulfilment guide for public sector services covers how requests are fulfilled within public sector governance constraints.

Related guides: ServiceNow Field Service: Coordinate the Case to Completion.

Field service for the public sector: work order tables, states and names

Field service management for a public body dispatches crews against work orders and records their time, parts and safety checks on the job. The deciding fact is that a work order and the tasks under it are separate records, so one fault report can produce several crew visits, each with its own assignee and its own closing state.

These are common out-of-box names for the records an agency’s field model relies on. Labels and defaults change between releases, so check them on your own instance and release before writing reports for an auditor.

The closing states matter most to an auditor. A task closed as incomplete should carry a reason, because a blank reason looks like a lost visit, while a task closed as complete should show the parts and time recorded against it.

Example (hypothetical): a resident reports a failed streetlight. The contact center raises a work order with the location. A first task goes to an electrical crew, who find the fault is a damaged cable and close the visit as incomplete with that reason. A second task is created for a cable repair crew with the right skill. The order still shows one fault with two visits, and the history explains the gap between them.

Which table records a crew's visit?

A crew visit is a work order task in the wm_task table, linked to its parent work order in wm_order. The parent holds the fault and location; each task holds who attended, when and what was recorded.

Can one work order have several tasks?

Yes. A single work order can carry several tasks, for example an inspection followed by a repair, each assigned and closed separately. This keeps travel time and parts per visit clean, which matters when cost per job is reported.

Where is the history of a job's status changes kept?

Status changes appear in the record's activity history, and field-level changes depend on auditing being switched on for the table. Auditing is set per table, so confirm it is enabled for the work order tables before relying on it as evidence.

For the product itself see ServiceNow field service management; the agency context is in ServiceNow for the public sector, and the service pattern is described under field service and case coordination.