Images are AI-generated illustrations, not documentary photographs or product screenshots.
Client onboarding checklist: confirm the agreement before collecting access
Onboarding begins with what has already been approved: scope, price, payment process, schedule and client responsibilities. Do not treat a friendly introductory conversation as authorization to change a production system. Summarize the deliverables and any unresolved assumptions in writing. A small project needs a simple process, not a large portal full of forms. The objective is to prevent avoidable confusion before work becomes dependent on missing information.
Identify the decision-maker and communication route
Find out who can approve the work and who provides subject-matter feedback. Agree on where decisions are recorded, how urgent issues are raised and when updates will arrive. If several stakeholders disagree, ask the client to consolidate feedback. Do not copy sensitive conversations into public channels. A defined approval route protects the schedule and reduces the chance that you finish one version only to discover that a different person expected another.
Request only necessary information
Collect the files, brand materials and content the deliverables require. Explain which formats are useful and why. Avoid demanding identity documents or unrelated business records simply because an onboarding template contains a field for them. Set an approved transfer method and ask about confidentiality obligations. If materials are late, discuss the effect on the schedule instead of pretending that the original deadline is still achievable without changes.
Use safe account access
Prefer named accounts with limited permissions over sharing the owner’s administrator password. Enable supported MFA and agree on how access will be removed at handover. CISA recommends strong passwords, password managers and MFA as basic account protection. Never ask a client to send a verification code through an untrusted message or disable a security requirement to make your work easier. Escalate access problems through the legitimate account owner.
Agree on review and handover
Explain what the client will receive at each checkpoint and how feedback should be submitted. Include any documentation, source files and training that form part of the offer. Identify what happens after the included support period and what counts as additional work. For a website, agree on who owns hosting and renewals. Do not leave routine maintenance responsibilities ambiguous until a service fails after the project is over.
Use a concise kickoff record
Create one shared summary containing the goal, deliverables, exclusions, contacts, required inputs, approval steps and target dates. Check it with the client rather than assuming a completed form means agreement. For example, a simple landing-page project may need approved copy, licensed imagery and a designated reviewer before implementation starts. Keep the record current when decisions change. Good onboarding is a reusable habit, not a guarantee that every client project will be friction-free.
Sources and further reading
Upwork: fixed-price and hourly project trade-offs
CISA: passwords, MFA, phishing and updates