Document: 33-client-onboarding.md
Version: 1.0.0

Purpose

This document defines the standard client onboarding process followed across all Rundown projects.

Client onboarding establishes the foundation for a successful project by aligning expectations, defining responsibilities, collecting required assets, and preparing both the client and the engineering team before development begins.

A structured onboarding process reduces misunderstandings, improves communication, and creates a smoother project experience.

Onboarding Philosophy

Projects should begin with alignment rather than implementation.

Every stakeholder should have a clear understanding of:

• Project objectives

• Scope

• Responsibilities

• Communication channels

• Timeline

• Deliverables

Successful projects begin with shared expectations.

Onboarding Objectives

The onboarding process should:

• Confirm project scope.

• Establish communication.

• Collect required assets.

• Verify technical requirements.

• Define success criteria.

• Prepare the engineering team.

Development should not begin until onboarding is complete.

Onboarding Workflow

Every project follows the same onboarding process.

Project Approval

↓

Contract Signed

↓

Initial Payment

↓

Kickoff Meeting

↓

Asset Collection

↓

Technical Discovery

↓

Project Setup

↓

Development Begins

Kickoff Meeting

The kickoff meeting establishes the working relationship.

Topics should include:

• Business objectives

• Target audience

• Project scope

• Timeline

• Milestones

• Communication expectations

• Approval process

Meeting outcomes should be documented.

Asset Collection

Required assets may include:

• Brand guidelines

• Logos

• Images

• Videos

• Copywriting

• Product data

• Domain information

• Hosting credentials (if applicable)

Missing assets should be identified before development begins.

Technical Discovery

The engineering team should confirm:

• Functional requirements

• CMS requirements

• Integrations

• User roles

• SEO requirements

• Performance expectations

• Accessibility requirements

Technical assumptions should be documented.

Communication

Every project should define:

• Primary client contact

• Primary Rundown contact

• Communication platform

• Meeting cadence

• Response expectations

Clear communication reduces delivery risk.

Responsibilities

Responsibilities should be explicitly defined.

Examples include:

Client

• Provide assets

• Review deliverables

• Approve milestones

• Supply feedback

Rundown

• Deliver agreed scope

• Maintain communication

• Provide progress updates

• Document significant decisions

Clearly defined ownership prevents unnecessary delays.

Project Setup

Before development begins:

• Repository created

• Project management workspace prepared

• Documentation initialized

• Development environment configured

• Timeline confirmed

Every project should begin with a consistent operational foundation.

Scope Confirmation

The agreed project scope should be documented and approved before implementation.

Requests outside the agreed scope should follow the project's change request process.

Preventing scope ambiguity is preferable to resolving disputes later.

Success Criteria

Every project should define measurable success criteria.

Examples include:

• Functional completion

• Performance targets

• SEO objectives

• Accessibility requirements

• Launch readiness

Success should be agreed before development begins.

Engineering Decision

Structured Client Onboarding

Status: Accepted

Decision

Every Rundown project follows a standardized onboarding process before development begins.

Reasoning

A structured onboarding process:

• Aligns expectations.

• Reduces misunderstandings.

• Improves planning.

• Minimizes scope ambiguity.

• Creates a stronger client experience.

Onboarding Checklist

Before beginning development, verify:

• Contract signed.

• Initial payment received.

• Kickoff meeting completed.

• Assets collected.

• Technical discovery completed.

• Communication channels established.

• Scope approved.

• Success criteria documented.

• Project workspace prepared.

Summary

Client onboarding establishes the operational and strategic foundation for every Rundown project.

By ensuring alignment before implementation begins, Rundown reduces delivery risk, improves communication, and creates a more predictable and professional project experience.

Related Documents

• 32-project-lifecycle.md

• 34-project-management.md

• 36-client-handover.md

Related ADRs

• ADR-003: Documentation Information Architecture