How to run employee workplace service requests from intake to confirmation

Define the service boundary

A workplace request can concern furniture, supplies, a room problem or a building service. It is not automatically an IT support ticket, an HR case or an emergency call. Publish a short service list with the correct route for those exceptions. ServiceNow's workplace documentation illustrates this category of employee needs; it does not mean SFI integrates with that software.

One intake process can accept several channels if they lead to the same operating record. Avoid requiring employees to understand the landlord's responsibilities or vendor contracts before asking for help. The coordinator can determine the responsible party after collecting the basic facts.

Ask for information the employee can provide

Begin with site, exact location, what happened, effect on work and a contact for clarification. A photo can help when appropriate, but avoid collecting client documents, badge details or unrelated personal information. Ask what the user observed rather than demanding a technical diagnosis.

Use a small set of categories and an obvious 'not sure' option. The intake owner can refine classification later. A long form may produce more fields while leaving the important question unanswered: can the team keep working safely?

Triage by impact and urgency

Separate safety concerns, widespread loss of an essential service, localized disruption and routine needs. Let employees explain impact; have the responsible team apply the agreed priority. If there is an immediate threat, follow the site's emergency procedures and contact the appropriate emergency or building service directly. A routine request queue should not be the only route for urgent safety help.

Document service hours, acknowledgment expectations and the escalation contact. Do not promise that every repair will be completed within the acknowledgment window. Parts, access and approval can affect the resolution plan.

Use statuses that describe the next action

Received, being assessed, scheduled, waiting for approval and awaiting confirmation are more useful than a vague 'in progress.' For every waiting status, name the person expected to act and the next follow-up date. Employees do not need every vendor email, but they do need to know what to expect.

Keep the coordinator responsible when the work moves to a provider. A handoff should not remove ownership. If a promised update is missed, the coordinator follows the escalation rule and changes the record to reflect the new plan.

Verify the result before closing

A provider saying 'done' may mean the visit ended, not that the user's problem is resolved. Ask the requester or designated site contact to confirm the result. Store an appropriate service record and any remaining limitation. If a workaround remains in place, label it as temporary and track the permanent action separately.

For repeated issues, link the new request to the earlier event. Review repeat visits, unresolved aging and the number of status inquiries alongside closure counts. Those measures help identify where communication or the underlying service needs improvement.

Introduce the workflow in one team first

Publish the intake route, service list and escalation instructions. Walk employees through a routine example and explain how updates will arrive. Review whether the process works during absence of the usual coordinator. SFI can discuss managing an agreed request workflow, with local access and physical work assigned to appropriate people. Service hours and coverage remain a scoping decision.