OBLYTECH Logo
OBLYTECH Logo

ServiceNow / Practical guide

ServiceNow Facilities Service Management: Run the Work Clearly

ServiceNow facilities service management coordinates location-based requests, work orders, maintenance needs, workplace issues, safety concerns, suppliers, communication, and completion evidence. The workflow should help the right team understand what is needed, where it is needed, what conditions apply, and who accepts the result.

For facilities and workplace owners managing service requests, work orders, safety concerns, and location-based tasks..

ServiceNow facilities service managementfacilities workflow ServiceNowwork orders

Guide map

Setting up facilities requests as a clear workflow

Define the facilities service and request boundary

Facilities requests are clearer when the boundary states which tasks are routine, which need a safety check and which belong to an outside contractor.

Capture location and work context at intake

Ask for the site, floor, and access notes when the request is raised, because technicians lose time returning to ask for details already known.

Dispatch work with safety and dependency checks

Before a technician is sent out, confirm the site hazards on file, whether another job must finish first and that the right tools are booked.

The practical framework

Organize ServiceNow facilities service management around location, request type, safety, dispatch, suppliers, work evidence, communication, and closure.

Begin with the service boundary and the outcome. A generic “facilities issue” category is rarely enough to dispatch safe and useful work.

Define the facilities service and request boundary

State supported services, locations, audiences, hours, exclusions, emergency paths, and accountable owner. Distinguish facilities fulfilment from IT, security, procurement, HR, or supplier work that may be related.

The ServiceNow workplace service route is the relevant internal destination when facilities work belongs to a wider employee service experience.

Capture location and work context at intake

Collect the location, area, issue or requested outcome, timing, access conditions, safety concern, affected people, equipment or asset, photos or evidence where appropriate, and contact or escort information. Make the reason for each required field understandable.

The ServiceNow request-fulfilment route provides an internal path when facilities intake and fulfilment need structured design.

Define what happens when the location is incomplete, the issue is urgent, the request is outside the service, or a safety concern changes the response.

Dispatch work with safety and dependency checks

Break the work into dispatch, assessment, approval, supplier, maintenance, inspection, and closure tasks where applicable. Record which action depends on access, equipment, a permit, a supplier, a shutdown, or another team.

The ServiceNow process optimization route is the appropriate internal destination when facilities tasks need coordinated states, handoffs, and exceptions.

Safety-related conditions should have a defined escalation and communication path. Do not rely on a normal work-order route when the consequence requires a different decision.

Track suppliers, delays, and communication

Record supplier or internal owner, expected evidence, timing condition, dependency, delay, next action, and requester communication. An external task still needs internal coordination and acceptance.

The ServiceNow support and maintenance route gives the reader an internal path for ongoing facilities workflow ownership and support.

Verify completion and improve the service

Closure should describe the work performed, result, evidence, remaining issue, requester or owner acceptance, and follow-up. Do not close because a supplier marked a task done if the workplace outcome has not been checked.

The ServiceNow continuous-improvement route provides an internal path for repeated location issues, incomplete requests, supplier delays, and workflow improvements.

Common questions

Questions teams ask about facilities workflows

What information should a facilities request contain?

At minimum, the service or issue, location, desired outcome, timing, affected people or area, access or safety condition, contact, and evidence needed to dispatch and complete the work. The exact fields should match the service boundary.

Who accepts a completed work order?

The accountable facilities or service owner should define acceptance. A supplier or technician can provide completion evidence, while the requester or owner may confirm that the workplace outcome was achieved.

The research-grounded boundary

For facilities service management, treat a reusable workflow or bounded customisation as a governed operation. Define the trigger, the permitted action, the human checkpoint, the failure signal, and the record that closes the loop. The practical safeguard is to make each dependency visible before the team treats the workflow as complete.

Separate facilities requests by the consequence they carry

Facilities teams receive requests that look alike on a form but need different responses: a faulty door lock that affects building security, a slow water leak, a request to move a desk, and a complaint about the cleaning rota. Routing all of them through one work-order path is a common early mistake. The first design decision is to group requests by consequence, because consequence sets the response time, the approver and the evidence needed.

Request typeTypical consequence if delayedSuggested first pathWho must confirm completion
Safety-related conditionHarm to people or closure of an areaImmediate escalation to the on-duty facilities lead, outside the normal queueFacilities lead and the affected area owner
Building access or security faultUnauthorized entry or a blocked exitPriority work order with a security notificationSecurity owner
Repair affecting daily workLost productivity in one areaStandard work order with a scheduled visitRequester or area supervisor
Workplace change or moveInconvenience with a known datePlanned request with approval and a calendar slotRequester and approver

Intake steps that prevent a second visit

  1. Require a location the dispatcher can act on. A building name is not enough when a floor has several zones; capture the zone and a nearby reference point.
  2. Ask whether the issue is safety related before any other question, and send a yes straight to the escalation path.
  3. Capture access conditions: who must be present, whether an escort is needed, and whether a shutdown or permit applies.
  4. Ask for a photo only when it changes the work. A photo of a ceiling stain does not tell a technician which valve to check.
  5. Confirm the best contact and preferred time window, and record both on the work order rather than in an email thread.

Where facilities workflows break down

Duplicate reports are the first sign of trouble. Several people notice the same leak and each submits a request, so the team sends three visits and the cause is fixed on the third. Matching open requests by location and issue type before creating a new one reduces the duplication, and it also shows which spots keep returning.

The second failure is closure by the supplier alone. A contractor marks a repair finished when the part is fitted, but the area is still unusable because a dependency was missed. Closure should need the requester or area owner to confirm the workplace outcome, not only the task.

The third is a safety concern sitting in a normal queue because the requester chose the wrong category. Make the escalation path visible at intake, and review every item that carried a safety signal but was never escalated.

Measures that show the workflow is working

Watch repeat reports for the same location, return visits, requests reopened after the requester confirms them, and time spent waiting for access or an approval. Each points to a specific fix. Repeat locations can mean a root cause nobody owns. Return visits can mean the dispatch note was incomplete. Waiting for access means intake did not ask about access early enough. The wider workplace context is covered in the workplace service delivery workflows post.

When a normal work order is not the right tool

Some building systems carry safety functions that must be run by a dedicated control process, with its own alarms and a certified response. A service request can record and coordinate the work around those systems, but it should not be the thing that detects or controls them. Describe that boundary clearly so nobody assumes a ticket is a control.

Questions a facilities lead asks about the workflow

How should the team handle a request that belongs to another group?

Route it to the owning group with the original details intact, and tell the requester who now holds it and what happens next. A request refused without a route can come back as a complaint.

Should contractors have direct access to the workflow?

Give them access to the tasks assigned to them and the fields they need to record completion, and nothing more. Their updates should be visible to the internal owner, who stays accountable for the outcome.

What evidence is worth keeping for a completed repair?

The description of the work, the parts or service used, the requester’s confirmation, and any residual issue. A completion photo helps when the repair is structural or hidden behind finishes. Keep only what someone will need to find later.

How do we review repeated problems in one location?

Group closed requests by location and category each review period, then decide whether the pattern points to a cause that needs its own work item. Repeat-location reviews can be a useful part of the facilities process, because they move the team from reacting to correcting.

Where to take the facilities design next

If your team is handling safety, access and routine repairs in one queue, start by sorting the last month of requests by consequence. Discuss the intake design with OBLYTECH. The workplace service delivery page covers coordinating requests about the environment in which people work.

A practical next step

Need a clearer ServiceNow operating model?

OBLYTECH can discuss the questions raised by this guide and the next review step. See the ServiceNow consulting services page for the commercial route.

Useful starting pointBring the current question, scope, ownership concerns, and evidence needs into the first review conversation.

ServiceNow guides on this topic

Guides from the Oblytech ServiceNow library that explain the practice behind this page.

More from the blog