How to choose the right information for a request form
A practical guide to designing request forms that collect the information needed to move work forward without creating unnecessary effort.
Start with the decision, not the fields
A useful form begins with the action it needs to support. Before adding a field, ask what the receiving person must decide, check or do once the request arrives.
This keeps the form connected to the work rather than to a vague wish to collect more information. It also makes it easier to explain why each answer matters.
- Name the person responsible
Ask only what changes the next step
Most forms become difficult when they ask for information that is interesting but does not change the outcome. Keep the essential path short, then make genuinely optional context easy to add.
- The request type or service needed.
- The person or team responsible for the next action.
- The timing, location or reference that changes the response.
Make the handoff visible
Tell the requester what happens after submission, who will see it and how they can check progress. A clear handoff reduces follow-up messages and makes gaps in the process easier to spot.