Web Design Client Onboarding Checklist: Everything to Collect Before You Start Building

A web design client onboarding checklist is what separates a project that launches on time from one that stalls in week three because you are still waiting on brand guidelines, hosting logins, or the client’s real content. If you have ever handed off a Figma file that a client rejected for reasons they could have told you on day one, or discovered mid-build that the hosting is on a plan that will not support what you designed, you already know why a proper intake matters.

This guide walks through every asset, credential, form, and decision to collect before you open Figma — plus how to stop doing it over eight email threads and a shared Notion page nobody updates.

Why web design agencies and freelancers need a formal onboarding process

Web design projects fail for a small number of predictable reasons: unclear scope, missing brand assets, inaccessible hosting, and content that never arrives. All four are onboarding problems, not design problems.

A structured onboarding checklist does three things at once:

• Locks scope early. A signed brief and page inventory prevent the “can we also add a booking system?” moment in week four.
• Removes technical blockers before design starts. Hosting, domain, and analytics access collected upfront means dev handoff does not stall on a forgotten login.
• Signals professionalism. Clients who receive a structured intake trust your process and stop questioning your rate.

If you handle more than one project a month, informal onboarding breaks. A checklist in a Notion page cannot tell you the client’s SSL certificate expires next week. That is where a proper client onboarding automation workflow starts to pay for itself.

The complete web design client onboarding checklist

Below is a full checklist for onboarding a new client to a website design, redesign, or landing page project. Not every item applies to every engagement — landing page projects skip most of the content section, e-commerce projects add product inventory and payment gateway credentials.

1. Contract and scope documents

Signed before any design work, no exceptions.

• Master services agreement or SOW — Scope, deliverables, revision rounds, timeline, out-of-scope changes policy
• Deposit invoice — Typically 30–50% upfront, non-refundable, holds the start date
• Payment schedule — Milestones tied to deliverables (design approval, dev complete, launch)
• IP and ownership terms — Who owns the final files, who owns pre-launch iterations, licensing for stock assets used
• NDA — If the client is pre-launch, has proprietary content, or is in a regulated industry
• Kill fee clause — What happens if the project is cancelled mid-build

2. Discovery brief

The one document that determines whether you build the right thing.

• Business overview — What they sell, to whom, at what price point
• Target audience — Primary persona, secondary personas, buyer intent
• Business goals for the site — Lead capture, e-commerce revenue, thought leadership, direct booking
• Success metrics — How they will judge the launched site in month three
• Current site pain points — What is broken, slow, off-brand, or missing
• Competitor sites they admire — Three to five references with notes on what they like
• Sites they dislike — What to avoid, in their words
• Tone and voice — Formal, playful, technical, luxury, direct
• Non-negotiables — Anything the CEO, founder, or legal team requires

3. Brand assets

The materials your designers need before they open the first file.

• Logo files — SVG, PNG (transparent), print-ready EPS or AI, in every approved lockup
• Brand guidelines PDF — Colors (hex, RGB, CMYK, Pantone), typography, spacing rules, do’s and don’ts
• Font files or licenses — Especially for custom or licensed typefaces
• Photography library — Approved product shots, team photos, lifestyle imagery, with usage rights
• Video assets — Hero video, product demos, testimonials
• Icon set — If they have an existing custom set to maintain
• Color palette in accessible format — Confirm WCAG AA contrast for text on brand backgrounds
• Illustration style guide — If custom illustrations are part of the brand

4. Content and copy

The single largest cause of missed launch dates. Get this before design, not after.

• Sitemap approval — Every page, in the exact tree structure
• Page-by-page copy — Headlines, subheads, body copy, CTAs, meta descriptions
• Blog or article backlog — If migrating, an export in a workable format
• Product or service descriptions — With SKUs, pricing, and variants for e-commerce
• Team bios and photos — Job titles, LinkedIn URLs, headshots
• Testimonials and case studies — With permission to publish and named source
• Legal pages — Privacy policy, terms of service, cookie policy, accessibility statement, imprint (if applicable)
• FAQ content — Real questions from sales or support, with approved answers
• Newsletter and lead magnet copy — Confirmation emails, welcome flows

If content is going to slip, agree upfront on placeholder policy and who writes the fallback. A document request email template sent at kickoff makes the “please send us your bios” ask feel routine, not needy.

5. Technical credentials and access

Every login the dev team needs before they touch a line of code. Batch this — nothing kills week two like waiting on a hosting provider password reset.

• Domain registrar login — Or DNS management access
• Current hosting provider access — With ability to point DNS, back up, and eventually migrate
• New hosting decision — If moving, the target host, plan, and billing owner
• CMS admin access — WordPress, Webflow, Shopify, Ghost, HubSpot, etc.
• Google Workspace or email admin — For MX record changes at launch
• Cloudflare or CDN access — If in use
• SSL certificate provider — Or confirmation new host will handle it
• Git repository access — If the client owns the codebase
• Staging environment credentials — Or agreement on where staging will live
• FTP or SFTP credentials — For legacy hosting scenarios
• Environment variables and API keys — For any third-party services the site consumes

6. Analytics, tracking, and integrations

Credentials that used to be nice-to-have. Now they are day-one required if you want to measure anything post-launch.

• Google Analytics 4 property access — Admin role, not just viewer
• Google Tag Manager admin access
• Google Search Console verification — With ownership transfer if needed
• Meta Business Manager — For pixel install and ads integration
• LinkedIn Insight Tag admin
• HubSpot, Salesforce, or CRM access — For form submissions and lead routing
• Email service provider access — Mailchimp, ActiveCampaign, ConvertKit, for form connections
• Booking or scheduling tool — Calendly, Acuity, if embedded
• Payment gateway access — Stripe, PayPal, for e-commerce
• Live chat provider — Intercom, Drift, if embedded

7. Legal, compliance, and accessibility requirements

The requirements that turn into rework if they surface after launch.

• Cookie banner requirements — GDPR, CCPA, ePrivacy — depends on audience geography
• Data processing agreement — If handling EU user data. If the client operates in Europe, our guide on GDPR-compliant document collection covers what actually needs to be in place.
• Accessibility target — WCAG 2.1 AA is standard; some regulated industries require AAA
• Industry-specific compliance — HIPAA for health, SOC 2 evidence for enterprise SaaS
• Copyright and image licensing — Written confirmation the client owns or has licensed every image they supply
• Trademark or brand approval process — Who signs off on final creative before launch

8. Third-party approvals and stakeholders

The people who can kill your project on day 42 if they only see it on day 42.

• Full stakeholder list — Names, roles, decision-making authority
• Sign-off matrix — Who approves design, who approves copy, who approves technical decisions
• Legal review process — Timeline and approver
• Founder or CEO involvement — At what milestones and via what format
• Design system or parent brand team — If subsidiary of a larger org
• External agency dependencies — SEO agency, PPC agency, PR firm

Web design client onboarding checklist by project type

Not every project needs everything above. Here is what to prioritize by engagement type.

The mistakes web design agencies make onboarding new clients

Three patterns show up in almost every stalled or over-budget project:

1. Design starts before content is in. Designers end up filling pages with lorem ipsum and stock images. When real content arrives, layouts break, headline sizes are wrong, and the client “does not like it anymore.”
2. Hosting decision deferred to launch week. The team discovers the current host does not support Node, the CDN cannot be pointed without a downtime window, or the client’s DNS is managed by a former developer who is no longer reachable.
3. Sign-off authority never confirmed. Design goes to the marketing manager who loves it, then the founder sees it two weeks later and asks for a full redirection.

All three come from the same root cause: no single source of truth for what has been collected, what is missing, and who needs to approve what. A kickoff spreadsheet does not remind the client to send the SSL provider login. A shared Google Drive does not flag that the brand guidelines PDF is the outdated 2022 version.

How to automate web design client onboarding

Manual onboarding falls apart the same way at scale: it depends on you remembering to send the next email. Automating it looks like this:

1. Build one workflow template covering every asset, credential, brief question, and approval in the checklist above.
2. Send a magic link to the client the moment the SOW is signed — no account creation, no password reset loop.
3. The client uploads at their own pace through a branded portal that looks like your agency. They see what you still need, what is approved, and what you flagged for a second version.
4. You get notified every time an asset lands. Approve, reject with a specific reason, or request a corrected version in a click.
5. The system chases the client on the schedule you set — no follow-up emails from your project manager.
6. Credentials that expire (SSL certs, API keys, third-party integrations) trigger renewal reminders automatically. See how document expiration tracking closes that gap for anything with a renewal date.

Agencies that switch from email-based onboarding to a workflow-based system report kickoff-to-design-start dropping from three weeks to under a week, and near-zero missed content on launch day.

For agencies that want the intake experience to look like their brand end-to-end, a white-label client portal removes any third-party logo — the client only ever sees your studio name and colors. This alone is often what turns a $12k project into a $30k retainer client.

The same workflow logic applies to any high-touch client onboarding. If your agency also runs paid media or long-form content, our broader marketing agency client onboarding checklist covers the intake for engagements beyond design and build.

Frequently asked questions

What documents do I need from a client before starting a web design project?

At minimum: a signed SOW and deposit, a completed discovery brief, brand assets (logo, colors, typography), page-by-page copy or a content plan, hosting and domain access, and admin credentials for any CMS or third-party tool the site will integrate with. E-commerce projects add product data and payment gateway access.

How long should web design client onboarding take?

Well-run onboarding is typically five to seven business days from signed SOW to design kickoff. Manual onboarding often stretches to three weeks because credentials, brand assets, and content arrive one at a time over email. Running collection in parallel through a client portal compresses this significantly.

Do I need a signed contract before I start collecting brand assets?

Yes. A signed SOW and deposit invoice are the trigger for onboarding — not the other way around. Starting discovery before the contract is signed is how agencies end up doing free work for a client who never signs.

What is a discovery brief and why does it matter?

A discovery brief is a structured document capturing the client’s business goals, target audience, success metrics, tone, and non-negotiables for the site. It matters because every design decision after kickoff will reference it. If the brief is vague, the design is vague, and revisions multiply. The brief is the artifact you point to when scope creep starts.

How do I stop clients from delaying my web design project with late content?

Two things work: collect placeholder content or a content plan before design starts (never after), and use a workflow tool that automatically reminds the client which pages are still pending. Manual “hey, checking in on that copy” emails from a project manager scale badly and feel needy. Automated reminders through a branded portal do not.

Onboard every web design client through the same clean workflow

If you are ready to stop chasing logos, hosting logins, and page copy across email threads, Superdocu handles the whole intake in one branded workflow — brief, assets, credentials, and approvals in one link. Start a free trial — no credit card required.