Most freelance projects don’t go wrong in the middle. They go wrong at the start — because something critical wasn’t clarified before the work began.
A pre-project checklist is your defense against that. It’s a short list of everything you need to confirm, receive, or establish before you open a single file or write a single line.
It takes fifteen minutes to build. It saves hours on every project that follows.
Why a Checklist Changes Everything
Without a checklist, you start each project from scratch. You remember to ask about most things. You forget a few. The things you forget come back to bite you.
With a checklist, the project starts from a place of clarity. You have everything you need. The client has confirmed the details. The financial terms are agreed. You can focus entirely on doing good work.
The three categories of pre-project problems
Problems that derail projects usually fall into one of three categories: unclear scope (you and the client have different pictures of what “done” looks like), missing access or assets (you can’t start because you’re waiting for login credentials, source files, or brand assets), and payment surprises (the invoice comes due and the process is messier than expected).
A good checklist addresses all three before work begins.
Section 1: Scope Clarity
This is the most important section of your checklist.
Deliverables list
Can you write down, right now, exactly what you’re going to deliver? Not in general terms — specifically. “Three logo variations in PNG, SVG, and PDF formats” rather than “logo design.”
If you can’t write a specific deliverable list, the scope isn’t clear enough to start.
Revision rounds
How many rounds of revisions are included? This needs to be agreed before work begins, not after the third revision request arrives.
Out-of-scope definition
What’s explicitly not included? This feels awkward to establish upfront, but it prevents the most common disputes. “This includes copy for the homepage and three interior pages. Additional pages are outside scope and would be quoted separately.”
Success definition
Ask the client: how will you know this project was successful? Their answer tells you a lot about what they’re really optimizing for — and occasionally reveals expectations that differ significantly from what you understood.
Section 2: Timeline and Milestones
Project start date
When do you actually start work? This matters for your capacity planning and for setting the client’s expectations about delivery.
Key milestone dates
For longer projects: when is the first draft due? When is client feedback needed? When does final delivery happen? Getting these on the calendar at the start prevents last-minute scrambles.
Client response commitments
How quickly will the client respond to your questions or review requests? If you need feedback in 48 hours to hit a deadline, that commitment needs to be mutual — and it needs to be in writing.
Dependencies on third parties
Does the project require anything from someone else? A development handoff, a legal review, a client approval from their CEO? Identify these early. They’re often the source of timeline slippage you can’t control.
Section 3: Access and Assets
Login credentials and systems access
Do you need access to their website, CMS, analytics platform, design system, or code repository? Request this before day one.
Brand assets
Logos, fonts, color codes, past campaign materials, product photography — get these before you need them. Waiting mid-project for brand assets is an avoidable delay.
Source files from previous work
If you’re continuing work someone else started, you need their files. Not just the outputs — the editable source files. Clients sometimes don’t realize these need to be different things.
Relevant background materials
Past reports, previous proposals, existing research, customer data — anything that would help you understand context. Ask specifically. Clients often have useful materials they wouldn’t think to volunteer.
Section 4: Stakeholders and Communication
Who is your primary contact?
There should be one. If feedback comes from three different people with different opinions, your project will expand indefinitely.
Who has final approval authority?
This is different from your primary contact. Who can actually say yes? Make sure you know before you’re in a revision cycle that keeps stalling because the real decision-maker hasn’t weighed in.
What’s the preferred communication channel?
Email, Slack, a project management tool? Confirm this upfront and stick to it. Important decisions shouldn’t happen in text messages.
How often will you check in?
Weekly updates? Milestone-based check-ins? Define this rather than letting it develop organically. Clients who don’t hear from you assume the worst. Clients who hear from you regularly trust you more.
Section 5: Payment Terms — The Non-Negotiable Section
This section of your checklist isn’t optional. It’s the foundation that makes everything else work.
Deposit
Do you require a deposit before starting? Most experienced freelancers require 25–50% upfront. If you do, confirm the deposit is paid before work begins — not just agreed to.
Payment schedule
When will the remaining balance be invoiced? On delivery? At a milestone? Thirty days net? Be specific.
Payment method
How will the client pay? Wire transfer, credit card, PayPal? Know this before the invoice goes out. Payment method surprises cause delays.
Late payment policy
Does your contract include a late payment fee? Make sure the client knows this before it applies — ideally in the proposal and the contract.
The formal payment structure
Using a platform like PayOdin makes this section of your checklist almost automatic. The proposal and contract go through PayOdin. The invoice goes through PayOdin. A real person reviews the invoice before the client sees it.
When your payment setup is formalized from the start, there are no payment surprises. How it works covers the full process.
Section 6: The Signed Contract
Your checklist shouldn’t be marked complete until the contract is signed.
Not a verbal agreement. Not an email confirmation. A signed contract.
What the contract must include
The scope (by reference to your checklist or proposal), the timeline, the payment terms, the revision policy, and the intellectual property terms. For international engagements, also include jurisdiction and governing law.
IP transfer timing
Many freelancers forget to specify when IP transfers to the client. Most standard arrangements transfer IP upon payment in full. Make this explicit.
Contract as checklist confirmation
The act of having a client sign a contract is itself a checklist exercise. If there’s anything unclear in the contract, the signing conversation surfaces it. Use that conversation — it’s the last chance to fix ambiguities before work begins.
Putting Your Checklist Together
Here’s a simple template structure:
Pre-Project Checklist
Scope
- Deliverables list confirmed
- Revision rounds agreed
- Out-of-scope items defined
Timeline
- Start date confirmed
- Milestone dates set
- Client response turnaround agreed
Access and Assets
- All required logins and access granted
- Brand assets received
- Background materials provided
Stakeholders
- Primary contact named
- Approval authority identified
- Communication channel agreed
Payment
- Deposit received (if applicable)
- Payment schedule confirmed
- Payment method confirmed
Contract
- Contract signed by both parties
Making the Checklist Part of Your Process
Send it as part of your proposal
Include your pre-project checklist as part of the proposal. It signals professionalism and gives the client a clear picture of what they need to prepare.
Use it as a kickoff agenda
Open every new project kickoff call with your checklist. Work through it together. By the end of the call, everything should be confirmed.
Review it before you start work
The morning you’re supposed to start a new project, go through the checklist. Is everything actually checked? If items are unchecked, don’t start — get them confirmed first.
The Checklist Pays For Itself
Aiko’s story
Aiko is a freelance content writer from the Philippines. She built her pre-project checklist after a project went badly wrong due to unclear scope and a missing content approval chain.
“I spent six weeks on a project and then discovered the person I was working with couldn’t actually approve the content. It had to go through their legal team, who wanted major changes. I had to redo almost everything.”
After implementing the checklist, she’s had no similar situations. “The approval authority question alone has saved me twice.”
Getting Paid Cleanly Every Time
Your pre-project checklist gets you to a clean start. A good payment setup gets you to a clean finish.
PayOdin for freelancers covers the financial side of that. From proposal to payment — in one place, with a real person reviewing every invoice before the client sees it, and no company needed on your end.
No subscription. No setup fee. Just 10% per transaction. See the pricing page before you start your next project.
Conclusion
A pre-project checklist is fifteen minutes of work that protects every hour that follows.
It makes you more professional. It makes your projects run better. It catches problems before they become expensive. And it tells clients, before a single deliverable is created, that you’re organized, thorough, and trustworthy.
Build yours today. Use it on every project. Revise it as you learn what matters most in your specific work.
The best project is the one that starts with clarity. Your checklist creates that.