Nobody Logs the Corridor Request
‘Can you have a look at the printer when you’re passing?’ It’s the most common service request in every organization, and it’s invisible: not logged, not prioritized, not measured — remembered, if at all, by whoever was walking past at the time. Meanwhile the service desk’s actual queue fills with tickets missing the three things every fix depends on: what exactly is broken, where it physically is, and how urgent it truly is. The corridor request and the empty ticket queue are the same failure seen from two angles.
This work order form template gives the internal service desk — IT, facilities, or both — one front door: requests that arrive complete, routed, and measurable.
One Door, Two Desks
Start with the routing question: is this an IT matter, a facilities matter, or something else? A single dropdown sends each request toward the desk that owns it, and one form serves the whole organization — no parallel systems, no ‘was that a facilities thing or an IT thing?’ debate at the Monday meeting. For the requester, it’s one link to remember; for the desks, it’s one queue each, cleanly divided.
The Asset, Identified
‘The printer’ is not a location, and ‘the third-floor printer’ is not an asset. The form asks for the asset tag or model in a short text field — the number on the sticker that tells the technician exactly which machine they’re fixing before they’ve left their desk — and pins the physical location precisely: building, floor, and room, captured through structured selections rather than free text. The ten seconds a requester spends finding the tag saves the ten minutes a technician spends wandering a floor holding a screwdriver.
What Happened — and What’s Been Tried
The description gets a long text field with room to be specific, and a file upload takes the photo that replaces a paragraph — the error screen, the leak under the sink, the cracked screen. Then the question that kills the first three ticket replies before they’re ever written: what have you already tried? A multiple choice covers the classics — restarted it, checked the cables, tried another outlet, swapped the consumable — so the technician starts at step four instead of repeating steps one through three.
Priority, Claimed Honestly
Service desks run on SLAs, and SLAs run on triage — but the requester’s voice still belongs in the process. The form offers plain-language tiers via multiple choice: blocked — can’t work at all until it’s fixed; degraded — painful workaround exists; whenever — a nuisance, not a crisis. The claim sets the requester’s expectation; the desk’s triage keeps the truth honest. The combination matters in both directions: the genuinely blocked aren’t buried behind whoever shouted loudest, and the ‘this is blocking me’ printer nuisance gets its reality check before it jumps the queue.
Getting In — the Field That Saves Three Phone Calls
The fix is often scheduled before it’s performable: the server room needs a badge, the lab needs an escort, the floor is locked after six, the plant room requires a permit-to-work. A dedicated section captures access reality — door and gate codes, restricted hours, escort requirements, any safety preconditions — as structured short text and yes or no fields. Technicians arrive once, work, and leave — instead of arriving, phoning, waiting, and returning tomorrow.
Measured, Not Remembered
The moment a request lands, an instant alert reaches the duty desk, and webhooks can push it straight into your ticketing or scheduling platform with the data intact. The response view becomes the SLA board — filter by request type and age, and response performance is a filter away instead of a report away. Give the office manager read-only viewer access to check on their building’s open tickets without messaging the desk, and role-based permissions keep the two desks to their own queues. Internal service operations sit beside the IT templates collection and the wider business forms library.
Frequently Asked Questions
Should staff submit their own tickets, or should the desk do it?
Let staff submit directly — self-service is what makes the queue reflect reality. The form is deliberately simple enough for a non-technical requester in two minutes, and every self-submitted ticket is one less phone interruption for the desk.
How do the priority tiers actually work?
Requesters claim a tier in plain language — blocked, degraded, or whenever — and the desk triage confirms or adjusts it. The claim sets expectations on both sides; the triage keeps the queue honest. Together they replace the volume-based shouting match that decides priority in most organizations.
Why collect asset tags on a service request?
Because the tag identifies the exact machine — its model, history, and warranty — before anyone walks across the building. Tickets with tags get fixed on the first visit; tickets describing ‘the printer’ get a return trip.
Can one form really serve IT and facilities at once?
Yes — the request-type question routes each submission to the right desk, while the shared format keeps locations, access notes, and priorities consistent across both. One door for staff, two clean queues for the desks.
How do we measure whether the desk is actually performing?
Filter the response view by request type and submission age — the SLA picture is that simple. Watching response times by tier and desk turns ‘the service desk is slow’ into ‘P1 tickets average four hours, P3s are drifting’ — a conversation with a solution instead of a grievance.
What belongs in the access notes?
Whatever stands between the technician and the fix: door codes, badge requirements, escort rules, restricted hours, and any safety preconditions for the location. If the last repair visit needed a phone call to get inside, that call’s content belongs in this field.