The first two weeks of a freelance project determine whether it runs smoothly or turns into a nightmare. Most project problems — scope creep, missed deadlines, payment disputes, communication breakdowns — trace back to a sloppy or nonexistent onboarding process.
This checklist covers every step from the moment a client says "let's do this" to the moment you start actual work. Follow it, and you'll eliminate 90% of the problems that derail freelance projects.
Each step includes what to do, why it matters, and template language you can copy.
Phase 1: Pre-Project Setup
These steps happen before any work begins. Skip them at your peril.
1Send and sign the contract
Never start work without a signed contract. It should cover: scope of work, deliverables, timeline, payment terms, revision limits, intellectual property transfer, and termination clause.
Use e-signature tools like DocuSign, HelloSign, or even a simple "Reply AGREED to this email" for smaller projects.
2Send the deposit invoice
Standard practice is 25–50% upfront before work begins. This protects you from non-payment and signals that the client is serious. Use ToolKit.dev's free invoice generator to create professional PDF invoices instantly — no account required.
Hi [Name], attached is the deposit invoice for [amount]. Once this is processed, I'll begin the project setup outlined in our agreement. Payment is due within [X] days via [method]. Let me know if you have any questions.
3Collect all access and credentials
Create a single access request document listing everything you need: CMS logins, hosting credentials, analytics access, brand assets, style guides, social media accounts, FTP details, API keys. Send it as a checklist so the client can work through it.
Pro tip: Ask clients to use a password manager or shared vault rather than sending passwords in plaintext email.
4Review and confirm the project brief
If the client provided a brief, read it carefully and send back a summary of your understanding. If they didn't provide one, create a brief yourself based on your sales conversations and send it for approval. This eliminates the "that's not what I meant" problem.
• Objective: [what we're building/doing]
• Deliverables: [specific items]
• Timeline: [start date to end date]
• Out of scope: [things explicitly excluded]
If anything needs adjusting, let me know by [date]. Otherwise, I'll proceed based on this brief.
5Set up communication channels
Agree on where and how you'll communicate. Define: primary channel (Slack, email, Basecamp), response time expectations (within X hours during business days), meeting frequency (weekly check-ins), and emergency contact method.
Having this documented prevents the "why didn't you respond to my 11pm text?" conversation.
Phase 2: Project Kickoff
The kickoff phase sets the tone for the entire engagement.
6Schedule and run the kickoff call
Even for small projects, a 30-minute kickoff call prevents weeks of misalignment. Cover: project goals (the "why" behind the work), priorities and constraints, key stakeholders and decision-makers, review/approval process, and any questions from your brief review.
Record the call (with permission) and send summary notes afterward.
7Confirm the timeline and milestones
Break the project into milestones with specific dates. Each milestone should have: a deliverable, a review period, and a payment trigger (if using milestone-based billing). Share this as a simple table or timeline document.
8Agree on the review and feedback process
Define: how many revision rounds are included, how feedback should be delivered (consolidated, not piecemeal), turnaround time for client feedback, what happens if feedback is delayed (timeline shifts accordingly).
9Set up project management tools
Create the project in your PM tool (Notion, Asana, Trello, ClickUp) and invite the client if appropriate. Set up folders, task lists, and file sharing. Even a shared Google Drive folder with clear naming conventions works.
10Send the welcome packet
A one-page document that includes: your working hours, communication preferences, how to reach you in an emergency, what you need from the client (and by when), and a reminder of the project timeline. This is your "operating manual" for the engagement.
The Freelancer Business Kit
Proposal templates, contract templates, onboarding checklists, invoice layouts, and email scripts — everything you need to run the business side of freelancing.
Get the Kit — $19Phase 3: Project Execution
These steps keep the project on track while work is underway.
11Send regular progress updates
Weekly updates prevent the "how's it going?" check-in emails. Keep them brief: what was completed this week, what's planned for next week, any blockers or decisions needed. Consistency builds trust.
✅ Completed: [items finished]
📋 Next up: [items planned]
⚠️ Need from you: [decisions or materials needed]
We're on track for [next milestone] by [date]. Let me know if you have questions.
12Manage feedback rounds systematically
When sharing work for review, be specific about what you need feedback on. Use numbered items. Set a deadline. Ask for consolidated feedback from one point of contact rather than scattered input from multiple stakeholders.
13Track revisions against your contract
Keep a log of revision rounds. When you approach the contracted limit, flag it proactively: "We've used 2 of 3 included revision rounds. The next round is the final included revision." This prevents surprise additional-cost conversations.
14Handle scope changes formally
When a client requests something outside the original scope, respond professionally with a change order. Document the additional work, the cost, and the impact on the timeline. Get written approval before proceeding.
15Send milestone invoices on time
Invoice immediately when milestones are hit. Delayed invoicing signals that payment isn't a priority — and clients will treat it that way. Use ToolKit.dev's invoice generator to create and send professional invoices in minutes.
Phase 4: Project Wrap-Up
How you end a project determines whether the client comes back.
16Deliver final files with documentation
Don't just send a zip file. Include a delivery document that lists: all deliverables (with file names), any login credentials created, instructions for implementation, and maintenance recommendations if applicable.
17Send the final invoice
Include a project summary with the final invoice: total project cost, payments received, remaining balance. This provides a clean financial record for both parties.
18Request feedback
Ask for honest feedback about the experience. What worked well? What could be improved? This shows professionalism and helps you refine your process.
1. What went well that I should keep doing?
2. What could I improve for future projects?
Your honest feedback helps me get better. Thanks for the great collaboration!
19Ask for a testimonial
Strike while the iron is hot. If the client is happy, ask for a testimonial within a week of project completion. Make it easy — offer to draft one they can edit, or ask a specific question like "What was the biggest result you saw from this project?"
20Plant the seed for future work
End every project by mentioning what you could help with next. Not a hard sell — a genuine suggestion based on what you learned during the project. Also ask: "Is there anyone else you know who might benefit from similar work?" Referrals from happy clients are your highest-converting lead source.
Frequently Asked Questions
For most projects, onboarding should take 3–5 business days from signed contract to kickoff call. This gives you time to collect access credentials, review the brief, set up project tools, and prepare questions. Rushing onboarding leads to misaligned expectations and scope creep. For larger projects ($10K+), allow 1–2 weeks.
Yes. Onboarding is work — reviewing briefs, setting up systems, researching the client's business, and preparing project plans all take time. Include onboarding time in your project estimate. Some freelancers list it as a separate line item (Discovery & Setup) to make the value visible. Never do unpaid onboarding work.
Walk away. A client who refuses to sign a contract is telling you they want flexibility to change scope, delay payment, or dispute deliverables without accountability. No contract means no legal protection for either party. If they push back on your contract, offer to use theirs instead — but never start work without a signed agreement.
Refer back to the signed scope of work. When a client requests something outside the agreed scope, respond with: "That sounds like a great addition. It falls outside our current scope, so I'll put together a change order with the additional cost and timeline. Want me to send that over?" This is professional, not confrontational. Having a documented scope makes these conversations easy.
Get Every Template You Need
Stop writing contracts, proposals, and onboarding documents from scratch. The Legal Templates Pack includes everything:
- Terms of Service template
- DMCA Policy template
- Cookie Policy template
- Refund Policy template
- Acceptable Use Policy template
- Customization guides for each document