01
Step one: define what can be requested
Start by listing the kinds of asks the form will accept and write them as short choices. In the office equipment example, the choices might be new laptop, replacement charger, monitor, desk accessory and other. Limiting the list keeps requesters from inventing categories that nobody owns. Next, name one person or team responsible for each choice, because a request without an owner stalls. Resist the temptation to cover every department on day one. A narrow form that routes cleanly teaches you which categories are missing, and adding a choice later is far easier than untangling a muddled queue.
02
Step two: choose the fields that decide action
Every field should help someone act. For the equipment desk, require the requester's name, the item type, the reason, the date needed and the delivery location. Make the reason a short sentence rather than an essay, and offer a simple urgency selector with defined meanings, such as blocking work today or needed this month. Remove anything that exists only out of curiosity, since long forms push people back to chat messages. Add one optional notes box for surprises. Test the form by submitting three realistic examples yourself and checking whether the owner could act on each without a follow-up question.
03
Step three: confirm, route and close the loop
After submission, the requester should see a confirmation showing a reference number and what happens next. Route the entry to the owner you named in step one, and set a target response time that you can honestly meet, such as two working days. In the example, the facilities coordinator marks the request approved, ordered or declined, with a short reason. Each status change should notify the requester. Review the queue weekly, looking for repeated asks and missing fields, then adjust the form. The loop is complete only when the requester knows the outcome, not when the ticket merely disappears.