What to Collect From an Agency Client Before Kickoff

Confirm the commercial starting line

Check the accepted scope, named approver, agreement, and required first payment. The checklist should reflect what was sold, not an old package template. If work begins before a deposit under your terms, say so explicitly instead of treating payment as a universal gate.

Collect the minimum working materials

Ask for the version your team will actually use. A shared folder full of outdated logos creates another review job.

• Brand guide, approved logo files, and the person who can approve new uses.
• Existing website, campaign, analytics, or design materials relevant to the first milestone.
• Content owner and status: ready, being written, or still undecided.
• Examples or constraints that affect the approved scope.
• Required legal or compliance review contact when the project needs one.

Verify access instead of collecting passwords

Ask the client to invite a named team member with the minimum permission required through the relevant product. Record the account or property, requested role, owner, and whether the invitation works. Avoid asking for passwords in email, a generic form, or a document link. If a specialist credential tool is necessary, use your approved process.

Mark each item ready, blocked, or not needed

For each request, show why it matters, who owns it, where to provide it, and when it is needed. Review incoming file links and permissions. If something is blocked, explain the exact fix. Kickoff can still happen with a noncritical item missing, but make that a conscious decision and adjust the agenda.

Keep the client-facing path simple

CroozFlow can organize supported questions, requested file links, review, update requests, and the next booking action. It does not store the underlying files from external providers or replace their access controls. The important improvement is that the client can see what is still needed and your team can verify it before promising a start date.