A signed contract is a commitment, not a project plan. Before an agency can deliver well, the client and team need a shared view of what is being done, who is responsible, how decisions will be made, and what must happen first.
A reliable agency client onboarding checklist helps make that transition repeatable. It reduces the chances that a project begins with missing logins, unclear approvers, or a payment misunderstanding. It also gives the client a calm, professional first experience without burying them in forms and meetings.
The steps below are designed for small and midsize agencies. Adapt them to your service, contract, and client size: a short design engagement does not need the same intake process as a multi-market website rebuild. The goal is not to collect everything. It is to resolve the questions that could delay work, create risk, or lead to conflicting expectations.
What agency client onboarding should accomplish
Onboarding is the bridge between the sales process and delivery. It starts when the client signs and ends when the team has enough confirmed information to begin the first meaningful work. In practice, that may take a few days or several weeks, depending on access, client availability, and the complexity of the engagement.
By the end of onboarding, both sides should be able to answer five questions:
- What did we agree to deliver, and what is outside the agreement?
- Who is doing the work, providing inputs, reviewing, and approving?
- What information, access, or materials are needed—and by when?
- How will changes, delays, questions, and decisions be handled?
- What is the first scheduled project activity, and what does it depend on?
If the proposal or contract leaves important details open, address them before treating the schedule as fixed. A clear proposal that covers more than scope, timeline, and price makes onboarding easier, but it does not eliminate the need to confirm details with the actual delivery team.
The agency client onboarding checklist
1. Confirm the agreement and commercial starting conditions
Save the signed agreement, final proposal, and any approved addenda in the client’s designated record. Check that the versions match: the agreed services, deliverables, fees, payment schedule, start conditions, and named entities should not conflict across documents.
- Confirm the authorized client signatory and the agency’s day-to-day contact.
- Record the project fee, billing schedule, invoicing contact, purchase-order requirements, and payment terms.
- Confirm whether work starts after signature, deposit, purchase order, or another stated condition.
- Note the contract’s rules for expenses, cancellation, pause periods, intellectual property, confidentiality, and changes.
- Set a reminder for any renewal, end date, or notice period relevant to the engagement.
Do not assume that “signed” means “ready to start.” If your agreement requires an initial payment or purchase order, make that a visible gate in your project workflow. If the client’s accounts-payable process requires a vendor form, ask for it early rather than discovering it when an invoice is overdue.
For recurring work, record what the retainer includes, how requests are prioritized, and whether unused time carries forward. When monthly demand can vary, make sure the practical working model matches the commercial terms; retainer pricing is only one part of setting those expectations.
2. Run a structured sales-to-delivery handoff
The person who sold the work may know details that never made it into the proposal: internal politics, a promised launch window, a sensitive stakeholder, or why the client chose the agency. Capture those details before the delivery team has to rediscover them through guesswork.
Use a short handoff document or a 20-minute internal meeting. Include:
- The client’s stated goals and the business problem behind the request.
- What success means to the client, including any agreed measurement or decision point.
- Scope, exclusions, assumptions, dependencies, and known risks.
- Important statements made during sales that are not yet reflected in writing.
- Client communication preferences, working hours, and any known approval bottlenecks.
- Team roles, estimated effort, and any capacity conflicts that need attention.
Separate confirmed commitments from sales-stage impressions. “The marketing director seemed to prefer a fast launch” is useful context, but it is not the same as a signed deadline. The project lead should confirm priorities directly with the client before basing a delivery plan on them.
Also check that the proposed start fits the team’s real availability. A signed project can still create delivery strain if several projects begin at once. Use a capacity review, such as the method in this guide to calculating agency capacity, before promising a kickoff date.
3. Send a focused welcome and intake request
Within a business day or two of signature, send a concise welcome message. Introduce the project lead and explain what happens next, what the client needs to provide, and when the kickoff is expected. Avoid sending a sprawling questionnaire before the client knows why the information matters.
Ask for information in manageable groups. Depending on the work, the first intake request may include:
- Business overview, priority audiences, products or services, and current positioning.
- Existing brand guidelines, research, content, analytics, or campaign materials.
- Known deadlines, launch constraints, legal requirements, and other active initiatives.
- Names and roles of stakeholders, reviewers, and final approvers.
- Preferred communication channel and any relevant procurement or compliance steps.
State a due date and distinguish required items from helpful background. For example: “We need the current site analytics and CMS contact before the technical review; previous campaign reports can follow next week.” This lets the client make progress even if they cannot assemble every file at once.
Where information is sensitive, ask only for what is needed and use an appropriate method for receiving it. The FTC’s business guide to protecting personal information recommends limiting the information a business collects and retains. That principle is useful for agency intake too: do not request customer records or personal data just because it might be interesting.
4. Set up project communication, roles, and approvals
Agree on how the work will run before discussions scatter across email, chat, and meeting notes. The client does not need to adopt every agency tool, but both sides need a dependable source of truth for decisions, tasks, files, and feedback.
- Name one agency project lead and one client lead for routine coordination.
- Identify the final approver and any reviewers whose input is required.
- Choose the main channel for day-to-day questions and the location for formal approvals.
- Agree on a normal response window and how urgent issues should be raised.
- Set recurring status meetings only if they serve a clear purpose; otherwise use written updates.
Be explicit about review windows. “Please review promptly” is difficult to schedule around. “Please return consolidated feedback within three business days” gives both teams a useful planning assumption. Also clarify whether the agency will treat silence as approval; unless the agreement clearly says so, do not assume it.
For a client with several reviewers, ask for one person to reconcile comments before they reach the agency. If the brand lead requests one direction and the sales lead requests another, the agency should not be left to decide which stakeholder outranks the other.
5. Collect access and materials safely
List the systems needed for the first phase, not every platform the client has ever used. A website project might require CMS access, analytics, hosting or DNS coordination, a design library, and a staging environment. A campaign project may need ad-account access, brand assets, landing-page details, and reporting history.
For each item, record the system, who grants access, the permission level required, the date needed, and whether access has been tested. Prefer individual accounts and role-based permissions over shared passwords. Ask the client to grant the minimum access needed for the task, and remove or reduce access when it is no longer required.
The U.S. Cybersecurity and Infrastructure Security Agency explains that multi-factor authentication adds protection beyond a password. Where client systems support it, use MFA for agency accounts and ask clients to use secure access-sharing practices rather than sending credentials in ordinary email or chat.
Accessibility can also be an early input, not a last-minute check. For a website or digital product, ask about the client’s accessibility requirements and include them in the brief and review plan. The W3C’s overview of web accessibility fundamentals explains why accessible design benefits people with different abilities and situations. The right implementation standard depends on the project and applicable obligations, so clarify that with the client rather than making assumptions.
6. Translate the agreement into a working delivery plan
The contract describes the commercial agreement; the project plan turns it into work. Break the engagement into phases or milestones, identify dependencies, and assign an owner to each next action. For each milestone, define what the client will receive and what counts as review or approval.
For example, a small website redesign might start with a discovery workshop, then a content and technical review, then design concepts. The schedule should show that design depends on agreed goals and access to current content. If those inputs arrive late, the team may need to revise the sequence or launch date.
Build the plan around actual dependencies rather than an optimistic calendar. Include client review time, holidays, and known decision gates. If the scope is not yet clear enough to estimate confidently, make the first phase a discovery or definition stage instead of presenting uncertain dates as firm commitments.
Record how a request outside the agreed scope will be assessed. A simple route is: document the request, explain its effect on cost or timing, obtain written approval, then schedule the work. If the project shifts, use a consistent process; this change-order process for agency work can help make the impact visible before extra work begins.
7. Prepare a useful kickoff meeting
A kickoff is not a ceremonial introduction or a meeting to read the proposal aloud. It is a working session to test shared understanding, resolve open questions, and agree on the first steps. Send a short agenda beforehand and include the people who can answer key questions or make decisions.
A practical 45- to 60-minute agenda might cover:
- Introductions, roles, and the client’s priority for the engagement.
- Project goals, audiences, and how the client will judge progress.
- Scope, deliverables, assumptions, and boundaries.
- Timeline, dependencies, review windows, and approval process.
- Access or information still outstanding, with named owners and due dates.
- Risks, open decisions, and the first scheduled work session or deliverable.
Close by reading back the decisions and actions. Send notes soon after the meeting, with each action assigned to a person and a date. A useful note says “Client lead to confirm the final approver by Thursday,” not “Approver details to follow.” This small discipline prevents unresolved questions from disappearing into a meeting recap.
A simple onboarding sequence to adapt
For a straightforward project, the following sequence is often enough. Adjust the timing to the client’s procurement process, project complexity, and start conditions.
- Day 0: Agreement signed; agency saves final documents and confirms payment or purchase-order requirements.
- Day 1–2: Sales-to-delivery handoff; project lead sends welcome note, intake questions, and access request.
- Before kickoff: Client confirms key contacts and supplies essential inputs; agency drafts milestones and lists open dependencies.
- Kickoff: Team confirms goals, roles, scope, timing, review process, and immediate actions.
- After kickoff: Agency circulates decisions, updates the project plan, and begins the first agreed task when start conditions are met.
Keep one onboarding tracker with status fields such as “not requested,” “requested,” “received,” “verified,” and “not needed.” That is more useful than a long checklist that cannot show what is blocking the start. Assign an owner to every unresolved item, including items the agency must provide.
Common onboarding mistakes—and how to avoid them
Treating kickoff as the start of discovery
If the agency has not reviewed the proposal, sales notes, or client materials before kickoff, the meeting becomes an expensive first read-through. Prepare enough to ask informed questions, while leaving room for the client to correct your assumptions.
Requesting too much at once
A 40-item intake form can make a small project feel like an administrative burden. Start with information needed for the first phase, then ask for later-stage inputs when they become relevant. Explain why sensitive or time-consuming items are necessary.
Confusing access with readiness
A login that works does not mean the team has permission to change production settings or publish content. Confirm the allowed actions and approval requirements. For a high-risk change, agree on backups, staging, and rollback responsibility before proceeding.
Letting informal promises become hidden scope
“We can probably include that” may be heard as a commitment. If a request changes the work, make the impact clear and document the decision. Early, calm boundary-setting is easier than trying to recover margin after the team has already done the extra work.
Starting before the team has capacity
Sales pressure can make an immediate start seem attractive, but beginning without a staffed plan creates delays and context switching. Confirm who will do the work and when. If the start date must move, explain the dependency and offer a realistic alternative rather than pretending the schedule is unchanged.
Keep the checklist proportionate
A repeatable onboarding process should make the client’s next step clearer, not create paperwork for its own sake. For a small, low-risk engagement, one handoff note, a short intake email, and a focused kickoff may be enough. A complex website, regulated client, or multi-team retainer needs more formal access controls, approvals, and documentation.
Review the checklist after projects, especially when a delay or disagreement reveals a missing question. Remove steps that no longer help. The best agency client onboarding checklist is not the longest one; it is the one that reliably surfaces important dependencies before they become delivery problems.
FAQ
When should agency client onboarding begin?
Begin as soon as the agreement is signed, while respecting any start conditions such as a deposit or purchase order. The first steps are usually saving the final documents, completing the internal handoff, and telling the client what information or access is needed next.
Who owns client onboarding at an agency?
One person should own the process, usually the project manager, account lead, or delivery lead. Sales still contributes context, and specialists may handle access or technical checks, but a single owner should track open items and make sure the client knows whom to contact.
What should an agency request before kickoff?
Request only the inputs needed to make the kickoff productive: client and approver names, goals, relevant background materials, known deadlines, and essential access or procurement information. Other materials can be requested later if they are not needed for initial planning.
Should work start before all onboarding items are complete?
Sometimes. The team can begin tasks that do not depend on missing information, but identify the dependency and avoid treating the full schedule as confirmed. Do not proceed with sensitive access, production changes, or work requiring formal approval until the necessary authorization is in place.
How can an agency keep onboarding from feeling bureaucratic?
Explain why each request matters, group questions into a few manageable messages, and distinguish required items from optional context. Use a short kickoff agenda and track only decisions, dependencies, access, and responsibilities that affect delivery.