OBLYTECH Logo
Enquire Now
OBLYTECH Logo

ServiceNow / Practical guide

Connect Workplace Requests Across ServiceNow

ServiceNow workplace service delivery coordinates requests about the environment in which people work, whether that involves a physical location, equipment, access, a move, a maintenance need, or a related employee service. The workflow should make location, eligibility, fulfilment, dependencies, suppliers, communication, and completion visible.

For workplace and employee-service owners coordinating physical or remote workplace requests..

ServiceNow workplace service deliveryworkplace services ServiceNowfacilities requests
Discuss this ServiceNow topic

Guide map

Turn workplace requests into a repeatable review.

Define the workplace outcome and service boundary

The outcome and the owner's boundary come first, before any form or workflow is designed.

Capture location, eligibility, and request context

Each field should exist because the fulfilment team uses it to route, approve or deliver.

Coordinate fulfilment and dependencies

Write eligibility rules and approvals as explicit conditions, not guesses left to the requester.

The practical framework

Organize ServiceNow workplace services around request context, location, eligibility, fulfilment, suppliers, dependencies, communication, and closure.

Begin with the workplace outcome and the owner who can decide what the service includes. A generic request form can hide the information required to route and fulfil the work.

Define the workplace outcome and service boundary

State the service, audience, locations or work arrangements, supported request types, hours, exclusions, and owner. Distinguish a workplace service from an IT, HR, security, procurement, or supplier action that may support it.

The ServiceNow solutions route is the relevant internal destination when workplace work must connect to an enterprise service experience.

Capture location, eligibility, and request context

Request context may include location, building or area, work arrangement, timing, affected person or team, equipment, access, urgency, and required outcome. Collect only what the fulfilment team needs and make the reason for each important field clear.

The ServiceNow service-catalogue route provides an internal path when workplace requests need structured intake and fulfilment design.

Define eligibility and approval where the service has conditions. When information is missing or a request is outside the boundary, route it to a named owner rather than leaving the person to discover the correct process.

Coordinate fulfilment and dependencies

Break the work into tasks for workplace, facilities, IT, security, procurement, suppliers, or other teams. State which task blocks another, what evidence confirms completion, who owns the dependency, and how a failure is escalated.

The ServiceNow process optimization route is the appropriate internal destination when workplace requests need coordinated handoffs and exception handling.

Do not close the request when only the first team has acted. Confirm the workplace outcome with the requester or accountable owner.

Communicate delays, changes, and completion

Tell the requester what was accepted, what is pending, who owns the next action, what has changed, and what evidence confirms completion. Supplier or internal delays should create an accountable decision rather than a silent status.

The ServiceNow knowledge-management route provides an internal path for recurring workplace questions, preparation guidance, and support instructions.

Review workplace work as a service

Review repeated requests, incomplete information, handoff delays, supplier dependencies, location-specific issues, and requests that do not fit the catalogue. Decide whether the cause is service design, content, ownership, access, data, or fulfilment.

The ServiceNow continuous-improvement route gives the reader an internal path for improving workplace service delivery.

Common questions

Questions teams ask about workplace services

Should workplace requests use one workflow?

No. A shared front door can help people find services, but fulfilment, eligibility, approvals, location, and dependencies may differ. Use a common structure where helpful and distinct paths where the work requires them.

How should supplier work be tracked?

Record the supplier task, owner, request or work reference, expected evidence, communication, dependency, delay decision, and acceptance. The supplier does not replace internal accountability for the workplace outcome.

The research-grounded boundary

A reusable workflow or bounded customisation should be treated as a governed operation. Define the trigger, the permitted action, the human checkpoint, the failure signal, and the record that closes the loop. For workplace service delivery workflows, the practical safeguard is to make the dependency visible before the team treats the workflow as complete.

Define the workplace outcome a person is waiting for

Workplace requests are rarely about the workplace in the abstract. An employee who asks for a desk near a colleague wants to work with them this week. A manager who asks for a room for an interview wants a room that is private, available and set up before the candidate arrives. Starting from the outcome shows which teams must act and in what order, and it prevents a catalog that lists facilities items without saying what the person will be able to do afterwards.

Write the outcome for each common request in one sentence, then list the teams whose action is needed to achieve it. That list is the first version of the workflow map, and it shows quickly where a single form would hide several separate owners.

Workplace requests that need different context

Request typeContext the requester must giveTeams whose action usually follows
Desk or space changeLocation, duration, team members affected and any accessibility needSpace or facilities team, then IT for equipment and access
Meeting room or event setupDate, time, headcount, equipment and whether the room must be privateFacilities for the room, AV or IT for equipment, catering if relevant
Office move for a teamCurrent and target locations, a move date and the systems each person relies onFacilities, IT for network and devices, the team’s own owner for sequencing
Reported workplace issueExact location, what is wrong, whether it is a safety matter and who is affectedFacilities or building contractor, with safety escalation where required

The context column is what makes a request routable. A request without a location cannot be assigned to the right building team, and a request without a duration cannot be checked against room bookings.

A workflow sequence for coordinated fulfillment

  1. Check the request against the service boundary and redirect anything that belongs to another service.
  2. Confirm the eligibility rule, such as who may request a private room or a relocation, before any task is created.
  3. Create one parent record for the outcome, and separate tasks for each team whose action is required.
  4. State which task blocks which, so an equipment delivery does not start before the space it needs is ready.
  5. Keep the requester informed at each task change, and close the parent only when the outcome has been confirmed.

The closure step is a common point of failure for workplace requests. The first team finishes its task, the record closes, and the person arrives to find the room open but without the screen they asked for. Closing on confirmation of the outcome, rather than on completion of the first task, prevents that.

When a dedicated workflow is not justified

A workplace request that is rare, low-impact and handled by one person may not need a formal workflow at all. A shared mailbox or a short checklist can be enough. The test is whether several teams act on the request, whether the timing matters and whether the outcome needs evidence. If none of those is true, a structured workflow adds forms without adding control.

Related reading includes the post on catalog request eligibility and the post on facilities service management workflow, which covers location-based requests, work orders and completion evidence.

Should all workplace requests use one workflow?

No. A single front door helps people find the right service, but fulfilment, eligibility, approval and dependencies differ between request types. Use one entry point with separate fulfilment paths behind it, rather than one workflow that tries to fit every case.

How should supplier work be tracked?

As a task with its own owner, the supplier reference, the expected evidence and the date the task must be confirmed by. The internal owner keeps the parent request moving and tells the requester about any delay, even when the supplier is the one who is late.

What is the best evidence that a workplace request is finished?

Confirmation from the requester or the accountable owner that the outcome is in place. A task marked complete by the team that did the work is useful, but it is not the same thing, and the difference is what the workflow should check.

How do we spot repeated problems in one building?

Group requests by location and request type and look for clusters that repeat each month. A cluster in one area often points to an infrastructure or a process issue, and fixing the cause is cheaper than handling each request as new.

Next step for workplace requests

If workplace requests reach the right desk but arrive with too little context to be fulfilled, the intake design is usually the first thing to check. The ServiceNow Employee Center and self-service page is the related service page for employee-facing requests.

Which workplace request belongs in which ServiceNow record

A workplace request is not automatically a ticket for the workplace team. The record type should follow the work that has to happen: an IT fault stays an IT incident, a desk or room booking is a reservation, and a change to a person’s location is one request with tasks for several teams. Choosing wrongly is the most common reason requests bounce between queues.

The workplace applications ServiceNow offers vary by subscription and release, so confirm what your instance actually holds before mapping anything. The question of which workplace module routes IT tickets has a short answer: none does on its own. IT work enters through incident or request records in IT service management, and the workplace workflow hands work to IT by creating a task or a linked request that an IT fulfilment group owns.

What the person needsUsually belongs inHandoff to watch
A monitor, dock or network port at a desk stops workingAn incident handled by IT supportTell facilities the desk is unusable until it is fixed
Equipment for a new deskA catalogue request with fulfilment tasksDelivery date must match the move date
A desk or meeting room bookingA reservation, with exceptions handled by the workplace ownerCancellation rules and no-shows
Repair, cleaning or maintenance in a spaceA workplace or facilities case with a task for the supplierSupplier confirms completion before closure
An employee moves floor or siteOne request with tasks for IT, facilities and securityOne named owner closes the whole request

The move row is where most designs go wrong. Take an office move: one parent request holds the employee, the old and new location and the date. Child tasks go to IT for equipment and network ports, to facilities for the desk, and to security for building access. If one task slips, the requester still sees a single status instead of three separate messages, and the parent closes only when every child task is complete.

Moves that follow a hire or a role change usually start in HR, so the employee onboarding and lifecycle events guides show where the workplace tasks should be triggered. Equipment and access items follow the rules in request fulfilment and the service catalog, and faults follow incident management. If workplace services sit in several tools today, the workplace service delivery solution page describes how that work is scoped.

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.

Review ServiceNow consulting

ServiceNow guides on this topic

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

More from the blog

Related reading