Begin with the decision you need
Ask yourself what the answer will change. “What should the website achieve?” can lead to a useful project goal. A broad request to “tell us about your business” may produce a long answer that does not help the team make the next decision.
Describe a usable response
If you need approved copy, ask for the approved document or its link. If you need a logo pack, say which files are expected and who should confirm usage permissions. Avoid asking a client to infer the required format from an internal term.
- Ask one question per item.
- Name the expected answer or asset.
- Explain the decision or deliverable it supports.
Assign the request to someone
A company can have several people who assume someone else owns the answer. Give the input a person responsible and a date when timing matters. The final approver may be different from the person supplying the content.
Leave space for an honest gap
A client should be able to say an input is not ready. Partial responses help you distinguish a missing decision from an inaccessible file. Use that information to agree the next step rather than treating a blank field as carelessness.
A working checklist
Check items as you work. Your ticks stay on this page and reset when you leave.