Why it matters
A useful request identifies the service, scope variables, location or delivery context, timing and the best way to clarify uncertainty. The form should reduce a follow-up round without becoming an interrogation.
Common mistakes
- One long free-text box for every type of request
- Forcing an exact budget before explaining scope
- Collecting documents before explaining why they are needed
What you can do now
- Branch questions by service or request type
- Explain optional and required information
- Show a review summary before submission
Key takeaway
The form should prepare a good conversation, not pretend to replace judgement.