Why not just email
Because the answer to "can you send me your brand guidelines, your target audience and your top three competitors" arrives as one paragraph answering two of them, and then somebody has to chase. A form asks each question separately, records each answer separately, and shows plainly which ones are outstanding.
It also puts the request in the same place as the work, so it is not lost in a thread and it is visible to whoever picks the work up next.
Forms
9 outstanding
6 of 9 answered
Not started
Not started
Complete
Designing one
- Ask only what you will use. Every optional question lowers the completion rate of the ones that matter.
- One question per field. "Audience and competitors" is two questions and will be answered as one.
- Explain why you need the awkward one. Access credentials and budget both get answered far more often with a sentence of context.
- Attach it to the work order it is blocking, so the blockage is visible on both sides.
- Template the ones you send repeatedly. Onboarding is the obvious one.
Passwords and access keys should not be typed into a form and stored as answers. Use whatever secure sharing your client already uses, and use the form to record that access was granted rather than to hold the secret.
What this does not do
Every client sees every question. There is no branching.
Attachments are attachments.
A form goes to a client who signs in. It is not a web form for strangers.
For anything that needs signing, use Sign.
Questions
Can a client save and come back?
Yes. Partial completion is a state.
Can two people at a client answer?
Yes, anyone with portal access to that company.
Are answers editable after submission?
By your team, yes, with the change recorded.