Turn a staff request into owned work with a decision trail and an explicit handoff.
- Equipment and access listedCAPTURED
- Permissions checkedREVIEWED
- IT receives the handoffASSIGNED
PROCESS REFERENCE
Route the need
Give staff one clear path for equipment, access, facilities or people operations requests. Capture the request type, affected system or location, desired outcome and need-by date. Use an approved channel for sensitive information; ordinary intake should never ask for passwords.
Separate receipt from permission
An intake owner checks the details and names the team responsible. Where a manager, system owner or policy reviewer must authorize the work, record that decision before fulfillment. Receipt, approval and completion remain separate states.
Close with the requester
The receiving team gets the scope, context and relevant date together. Record what changed, who completed the work and what remains blocked. A transfer between queues becomes a handoff only when the next owner accepts responsibility.
Make the process work for your team.
Design an intake form people can finish
Collect enough context to route work without turning the first step into an interrogation.
Read the operating note
Close a request with a useful record
Define completion so future readers can understand what happened and what still needs attention.
Read the operating note
Map your next request.
Book a demo ↗