# Client onboarding questionnaire and kickoff checklist

Prepared for: [Client / engagement]
Prepared by: [Team / contact]
Response requested by: [Agreed date]

Adapt these questions to your signed scope. Remove irrelevant items and mark optional inputs clearly. This questionnaire does not change your agreement.

## 1. Goals and agreed scope

- What outcome should this engagement support?
- Which deliverables are included in the signed agreement?
- Which items are explicitly outside scope?
- What would a successful handoff look like?
- Are there fixed dates or external dependencies we should know about?

## 2. People and approvals

- Who is the day-to-day client contact?
- Who has final approval for deliverables?
- Who will consolidate feedback from other stakeholders?
- What review window have we agreed?
- Who should be informed when a decision affects scope or timing?

## 3. Information and files

For each required item, record:

- Item: [Current brand guidelines, approved copy, source data, etc.]
- Purpose: [Which deliverable this supports]
- Owner: [Name]
- Due date: [Agreed date]
- Format / version: [What your team can use]
- Status: [Requested / received / needs clarification / reviewed]
- Link or location: [Where the item can be found]

## 4. Access

- Which services does the team need access to?
- Who can issue a named-user invitation in each service?
- What is the minimum role needed for the agreed work?
- Who will remove access at the end of the engagement?

Do not put passwords, API keys or recovery codes in this questionnaire. Grant access in the original service using its supported invitation process.

## 5. Communication

- Where should project updates be shared?
- What update cadence works for the engagement?
- How should urgent blockers be raised?
- Are there unavailable dates or holidays that affect review?

## Kickoff readiness checklist

- [ ] Confirm the signed scope and success criteria.
- [ ] Confirm the client contact and final approver.
- [ ] Assign an owner and date to every required input.
- [ ] Review received files for relevance and current version.
- [ ] Verify required access in the original services.
- [ ] Record missing inputs and the work they block.
- [ ] Agree the update cadence and feedback process.
- [ ] Confirm the kickoff decision with the delivery owner.

## Outstanding blockers

| Blocker | Impact | Owner | Next action | Agreed date |
| --- | --- | --- | --- | --- |
| [Missing input] | [Work affected] | [Name] | [Action] | [Date] |

Template by Angelwood — https://angelwood.io/client-onboarding-software