Start with the decisions, not the form.
Before adding a question, ask what your team will do with the answer. A useful intake captures the people involved, the goal of the engagement, the deliverables, and the decisions that could block a start. If a question will not change the work, consider leaving it out.
Collect what is needed to begin.
Group requests into business details, project goals, materials, and access. Explain why each item matters and what a useful answer looks like. “Upload your current logo files, preferably SVG or PDF” is easier to act on than “Send assets.”
Make the agreement a visible step.
Put the scope and agreement where the client can review them in context. Keep a signature request separate from a casual acknowledgment. If the client has questions, make it clear who can answer them before they sign.
Treat account access as a handoff.
Name the platform and the permissions your team needs. Use the platform’s sharing process. For a guided setup, explain both sides: what the client supplies, what your agency does next, and how everyone knows access has been approved.
Give the welcome a destination.
A short tutorial can explain the working rhythm: where to send questions, where files belong, and how reviews happen. Then offer the kickoff booking link and a clear path to the client portal. Finishing onboarding should lead somewhere useful.
Keep the checklist small enough to finish.
Separate what blocks kickoff from what can arrive later. Give each required item an owner and put follow-up requests in the client workspace. The goal is a prepared beginning, not a perfect information archive on day one.
