Most freelancers end onboarding when the kickoff call is over. That’s not when onboarding ends, it’s when onboarding starts. The kickoff is the planning meeting. Onboarding is the two-week period between contract signing and the point when the engagement is running on a clear, agreed, tested foundation.
Calling onboarding complete before that foundation is built is how you get to month three and discover that nobody agreed on who approves final deliverables, that your client still hasn’t sent the brand assets, and that the person you thought was your primary contact doesn’t actually have budget authority. These are not month-three problems. They’re day-two problems you didn’t fix.
The 12-point audit below tells you exactly when an onboarding is finished. Run it at the end of week two of every engagement. A score below 10 means you have specific gaps to close before you enter the execution phase. A score of 12 means you can operate.
The 12-Point Onboarding Audit
Score each point 0 (not done) or 1 (complete). Total possible score: 12.
Point 1: Contract Signed
Is the fully executed contract (signed by both parties) saved in the shared documentation vault? A verbal agreement or a DocuSign link that was “probably signed” is not a yes. The contract must be signed, downloaded, and in your shared file system.
Why it matters: All disputes in professional services come back to what was in writing. “I thought we agreed” is not a contract.
Point 2: Kickoff Call Held and Documented
Did a formal kickoff call happen with a written summary sent within 24 hours? Not an informal “let’s get started” conversation, a structured call with agenda and documented outcomes.
Why it matters: The kickoff is the only moment when both parties are fully attentive, information is fresh, and decisions can be made before the work creates pressure. Every unresolved question from the kickoff will cost three times as long to resolve in month two.
Point 3: Communication Norms Agreed in Writing
Is there a written document (email, shared doc, Slack pin) that specifies primary channel, response time expectations on both sides, meeting cadence, and escalation path for urgent issues?
Why it matters: Communication friction in ongoing engagements almost always traces back to undefined norms in week one.
Point 4: Access Shared and Tested
Do you have working access to every system you need, CMS, project management tool, analytics, email platform, repository? “They said they’d add me” is not access. Test it.
Why it matters: Blocked access blocks work. Discovering on day five that your login doesn’t work delays the first milestone by a full day, which sets a precedent you don’t want.
Point 5: Asset Intake with Named Deadlines
Is there a written list of every asset you need from the client, with a specific person responsible for each and a specific date? Not “we need brand guidelines”, “Sarah will send brand guidelines by May 8.”
Why it matters: Without deadlines, asset delivery is optional. With deadlines, delayed delivery is documented and clearly the client’s responsibility, not yours.
Point 6: Stakeholders Mapped
Do you know every person who will touch this engagement, name, role, relationship to the project, and whether they’re a decision-maker, reviewer, or informational stakeholder?
Why it matters: Surprise stakeholders, people who appear in month two and want changes because they weren’t consulted, are a major source of scope creep and rework. Mapping stakeholders in week one gives you a chance to include them or formally exclude them.
Point 7: Success Metrics Defined and Agreed
Are there 2-4 specific, measurable outcomes that define success for the first 90 days, and has the client confirmed these in writing?
Why it matters: Without agreed metrics, “success” is defined retroactively by whoever is unhappiest. Success metrics turn renewal conversations from “was this worth it?” into “did we hit the numbers we agreed on?”
The most expensive onboarding gap is undefined success metrics. When you don’t have agreed numbers, client satisfaction becomes entirely subjective. The client will measure you against an expectation you didn’t know existed. Define the numbers in week one so the entire engagement has a shared scoreboard.
Point 8: Risk Register Created
Is there a written list of at least three risks that could affect timeline, scope, or outcome, with mitigation plans for each?
Why it matters: Risks discussed in week one feel like professional foresight. Risks that appear in month three feel like incompetence. A simple two-column table (Risk / Mitigation) is sufficient. It doesn’t need to be exhaustive, it needs to be honest.
Point 9: First Milestone Scheduled
Is there a specific deliverable with a specific due date and a specific review process on the calendar? Not “we’ll aim to have something in a few weeks”, a named deliverable, a named date, and a named reviewer.
Why it matters: Engagements without scheduled milestones drift. The first milestone is the proof of concept for the entire engagement. Put it on both calendars.
Point 10: Decision Authority Matrix Confirmed
Do you know who has the authority to approve deliverables, approve scope changes, and approve budget changes? Has this been confirmed in writing (even if just an email)?
Why it matters: Deliverables approved by someone without authority get overturned. Scope changes agreed with the wrong person get rejected. Knowing exactly who can say yes, for each type of decision, eliminates the most common source of rework.
Point 11: First Invoice Set Up and Acknowledged
Is the first invoice sent, acknowledged by the client, with payment terms confirmed?
Why it matters: An unsent or unacknowledged invoice is not a business relationship, it’s a favor. The payment setup is a professional act that signals organized operations and starts the financial accountability on both sides.
Point 12: Day 14 Check-In Scheduled
Is there a 20-minute call on both calendars for 14 days after kickoff, specifically for the purpose of early alignment check, not deliverable review?
Why it matters: Day 14 is the earliest moment when misalignments are visible but still small enough to fix cheaply. Most early engagement problems are still correctable at day 14. By day 45, they’re structural.
How to Use the Score
12/12: Onboarding is complete. Begin execution phase with confidence.
10-11/12: Close the gaps in the next 48 hours. Identify the missing points and take specific action. At 10+, your foundation is solid but has small holes. Patch them now.
7-9/12: You have significant onboarding risk. Several key agreements are missing. Schedule a short call to address the gaps before proceeding. Do not treat this as a production problem, it’s a foundation problem.
Below 7/12: Restart the onboarding process. The engagement is running on assumptions, not agreements. The problems you haven’t addressed yet will arrive eventually, and they’ll be harder to fix the longer you wait.
The 10-Minute Weekly Review
For the first six weeks of any engagement, run a shortened version of this audit each week. Not all 12 points, just the ones that are still incomplete or could regress. The goal is to catch slippage before it compounds.
After week six, a fully healthy onboarding should score 12/12 with no attention required. At that point, shift to the quarterly review cadence.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
