Onboarding is complete when the client can submit a usable request and your studio can accept it responsibly. A paid invoice or a successful portal invitation is only part of that transition. Treat commercial status, account access and delivery readiness as separate checks.
Separate account information from request information
Collect reusable details once: requester, approver, billing contact, brand resources and access restrictions. Keep changing instructions with the request: audience, intended use, approved copy, deliverables and deadline context. This prevents the first brief from becoming a mixture of account administration and creative direction.
Use a secure, approved location for assets. Ask who may use licensed material and who can authorise its use, rather than treating an uploaded file as permission. Do not request passwords in a brief; arrange appropriate account access through the relevant system.
Run the readiness workflow
- Confirm the agreed service and commercial status through the responsible billing owner. Record the intended start conditions without treating payment alone as a production trigger.
- Name the client requester and final approver. Confirm what happens when that person is unavailable.
- Grant the minimum required access and check the client view, including whether unrelated account information stays private.
- Collect the first brief with the brief and onboarding worksheet. Have a delivery owner inspect it for missing decisions, not merely empty fields.
- Either accept it into the ready queue with a stated next step or return one consolidated list of blockers with an owner for each.
Explain the service in use
Show how to request work, reorder the queue, consolidate feedback and approve a version. Explain active limits using the client's first request rather than a feature tour. Give the client a clear distinction between received, ready and active so receipt does not look like a delivery commitment.
The payment-to-first-brief walkthrough provides an ordered rehearsal. Continue into requests and delivery once the readiness gate is passed.
Choose only the interface you need
A shared board can be sufficient when permissions are simple and clients can find the current brief and status. Evaluate client portals when account-level assets, repeated status questions or access boundaries justify a separate client interface.
For sensitive work, agree storage, retention and permitted users before collecting assets. This workflow does not establish security or legal compliance. If the approver or asset permissions remain unclear, keep the request unready and explain exactly what must change before scheduling it.