What to Collect From Clients Before Work Starts: Agency Onboarding Checklist

One of the easiest ways to spot a service business that has been doing client work for a while is to look at its onboarding checklist.

It usually starts simply.

• A few basic questions.
• A request for a logo.
• Website access.
• A kickoff meeting.

Then the work begins.

One client forgets to mention that every deliverable needs legal approval. Another can’t find their Google Analytics account. A website redesign pauses because nobody has the original logo files. An SEO project sits idle while everyone tries to figure out who owns Search Console.

Every delay shows the team something they should have known earlier.

So another question gets added to the checklist.

Then another.

Over time, a simple onboarding form can turn into a long questionnaire. What started as a way to move projects forward begins to feel more like an application than the start of a working relationship.

Most service businesses do not get there on purpose. They are trying to avoid the same problems from happening again.

The irony is that a checklist meant to speed things up can end up slowing everything down.

Clients sign an agreement expecting momentum. Instead, they are greeted with pages of questions, requests for files they have not opened in years, access to systems they barely remember setting up, and information they do not fully understand why they are being asked to provide.

After enough client projects, a pattern becomes clear.

The best onboarding processes are not the ones collecting the most information. They are the ones collecting the right information at the right time.

That is the difference between onboarding that helps work move and onboarding that gets in the way.

Client Onboarding Checklist

Before meaningful work begins, make sure you have collected:

• Primary point of contact
• Decision maker(s)
• Project goals and desired outcomes
• Brand assets
• Required system access
• Existing documentation or previous work
• Approval process
• Communication expectations

Every project is different, but these are the categories that most service businesses rely on to get work moving without unnecessary delays.

The rest of this guide explains what to collect, why it matters, and what can usually wait until later.

A Checklist Should Prepare the Team

Many onboarding checklists quietly drift away from their original purpose.

Instead of helping the team get started, they become a place to collect anything that might be useful one day.

It is easy to see how that happens.

A developer wishes they had known about an old plugin.

The design team asks for more brand assets.

The strategist wants competitor information.

Finance adds another billing question.

None of those requests are unreasonable on their own.

The problem is that almost nothing ever gets removed.

Eventually, clients are answering questions for people they have not even met yet.

Before adding anything to your onboarding checklist, ask one simple question.

Would missing this prevent meaningful work from starting?

If the answer is yes, collect it now.

If the answer is no, it can probably wait until the team actually needs it.

That does not mean the information is not valuable.

It means the timing matters.

The best onboarding processes are not designed to collect everything as early as possible.

They are designed to collect what the next stage of delivery depends on.

Everything else can wait.

Know Who You Work With

This sounds obvious, but it is one of the biggest reasons projects become confusing after they begin.

Most businesses collect contact information.

Far fewer identify who actually plays which role.

The person signing the agreement is not always the person reviewing the work.

A marketing manager may coordinate the project. The owner makes the final decisions. Finance handles invoices. IT grants system access. Another stakeholder may only appear when it is time to approve the first deliverable.

None of that is unusual.

The problem is discovering it halfway through the project instead of during onboarding.

Before work starts, know:

• Who is the day-to-day contact?
• Who can make decisions?
• Who approves major deliverables?
• Is anyone else likely to become involved later?

We did not know the founder wanted to review every page until the entire site was ready.

A project manager shared that after a website launch slipped by nearly two weeks.

Nothing had gone wrong.

The team had simply been building toward approval from the wrong person.

That is rarely a delivery problem.

It is usually an onboarding problem.

Goals Matter More

Clients rarely buy deliverables.

They buy outcomes.

A client might ask for a new website.

But the real goal could be:

• Generating higher-quality leads
• Shortening the sales cycle
• Building credibility with enterprise buyers
• Replacing a website that is difficult to maintain

Each goal leads the project in a different direction.

One thing we have learned is that projects become harder when teams inherit assumptions instead of understanding expectations.

Sales may have discussed one priority.

The client may be thinking about another.

Leadership may care about something completely different.

Getting everyone aligned does not require a lengthy discovery workshop.

Sometimes one question is enough.

Six months from now, what would make you say this project was absolutely worth doing?

The answer usually tells you far more than a list of requested features ever will.

Brand Assets Are Messy

Designers tend to smile when a client says, “We already have all our brand files.”

Not because they do not believe them.

Because they have heard it before.

The logo exists.

The question is whether anyone still has the original file.

The brand guidelines exist.

Nobody is quite sure if they are still current.

The marketing team has one version.

The founder has another.

Sales is using something different again.

None of this means the client is disorganized.

Most businesses simply have not needed these files in months or even years. A new project is often the first time anyone has gone looking for them.

Request these early for creative projects:

• Original logo files (SVG, AI, EPS, etc.)
• Brand guidelines
• Fonts
• Color palette
• Approved imagery
• Existing creative assets

A redesign can easily pause for days while everyone searches shared drives, old email attachments, cloud storage, or folders from the agency that handled the rebrand years ago.

Requesting brand assets is not the hard part.

Finding them usually is.

That is why they belong near the beginning of onboarding, even if the design work will not start immediately.

Access Is Never Simple

On paper, the request sounds simple.

We will need access to your website.

Or Google Analytics.

Or Search Console.

Or the CRM.

Then reality gets involved.

Getting access often means dealing with:

• Accounts created years ago
• Former employees who originally set everything up
• Two-factor authentication tied to an old phone
• IT approval processes
• Password resets
• Nobody knowing which email address owns the account

From the agency’s perspective, it is a simple request.

From the client’s perspective, it can mean tracking down people, resetting credentials, confirming permissions, and working through internal security policies before anyone can click Invite.

That is why experienced teams ask for critical access early, even if implementation will not begin for another week or two.

Be specific about what you need.

We will need WordPress Administrator access so we can review your current setup before making changes.

The more specific your request, the easier it is for clients to take action.

Existing Work Matters

By the time a business hires an agency or consultant, there is usually a history behind the project.

There may have been:

• A previous agency
• An internal marketing team
• A strategy workshop
• An SEO audit that was never implemented
• A messaging exercise that quietly disappeared into a shared drive

None of that guarantees the work is still relevant.

But it is worth knowing it exists.

That context can save your team from repeating work the client has already paid for.

It can also explain:

• Why certain decisions were made
• Which conversations have already happened
• Which ideas were tested and abandoned for good reasons

Instead of asking clients to upload every document they have ever created, ask for the material they still refer to today or anything they believe would help your team understand the business faster.

How Decisions Happen

It is easy to assume projects slow down because feedback takes too long.

Sometimes that is true.

More often, the delivery team simply does not understand how decisions get made.

Before delivery begins, understand:

• Who reviews work as it is being developed?
• Who gives final approval?
• Does anyone outside the project team usually become involved?

You do not need a complicated approval matrix.

You just need enough clarity that your team is not surprised halfway through the project.

Communication Should Be Simple

Most clients are flexible.

They are happy to use email, a client portal, scheduled meetings, or another agreed process, as long as everyone knows where important information belongs.

Problems usually begin when there is not a single source of truth.

Instead of everything living in one place:

• Files arrive by email
• Feedback appears in a shared document
• New requests come through Slack
• Additional changes are mentioned during meetings

The goal is not to control how clients communicate.

It is to reduce the number of places everyone has to look later.

Every Business Needs Its Own Checklist

A web design agency has different priorities than an accounting firm.

An SEO consultant needs access that a branding agency does not.

An IT provider asks questions a business coach never would.

Every service business needs:

• The right people
• Clear goals
• Assets
• Access
• Context
• Process

Look back at your own projects and ask:

• Where do projects usually pause?
• What information are project managers constantly chasing?
• What do clients regularly assume you have already been given?

Those answers will tell you far more than any template downloaded from the internet.

Review It Often

One pattern shows up in almost every growing service business.

Questions get added.

Very few get removed.

One difficult client leads to another intake question.

A missed approval adds another field.

A developer requests one more technical detail.

Instead of asking, “What else should we collect?”

Ask:

“What information did we actually use during the first stage of delivery?”

Removing unnecessary work from your onboarding checklist is just as valuable as adding something important.

Start With Confidence

The strongest onboarding checklists all have one thing in common.

They are not trying to eliminate every unknown before work begins. They are trying to eliminate the unknowns that would prevent meaningful work from starting.

No checklist can anticipate every client question or unexpected situation.

Its job is to give the team enough context, enough access, enough clarity, and the right people to begin delivery with confidence.

Projects rarely stall because one critical thing was forgotten.

More often, they slow down because a dozen small pieces of information were collected too late.

That is why experienced teams stop treating onboarding as paperwork.

They start treating it as the first stage of delivery.

As businesses grow, documents, spreadsheets, and email threads make it harder to answer simple questions:

• What is still missing?
• Who is responsible for it?
• What can the team start working on today?
• What is blocking the project from moving forward?

That is where a structured onboarding workspace becomes valuable.

The hardest part of onboarding is not collecting information.

It is keeping the right information organized, visible, and moving through the right people.

Cintram brings onboarding forms, files, approvals, client communication, and project progress into one place, so every new client starts with clarity instead of confusion.