Project kickoff email templates for freelancers

1. The kickoff email (send the day the deposit lands)

Confirms the start date, the first milestone and how you'll communicate.

Subject: [Project] kicks off [date]

Hi [Client],

Thanks for the deposit. [Project] officially starts on [date].

Here's how the first two weeks look:
- [Date]: kickoff call ([length], agenda below)
- [Date]: [first milestone] ready for your review
- [Date]: your feedback due (one combined round, please)

I'll share progress in [channel] every [day]. For anything urgent, [phone/email] is fastest.

The agreed scope is attached. If anything in it looks wrong, tell me before the kickoff call so we can fix it now.

Looking forward to it,
[Your name]

2. The scope recap (send right after the kickoff call)

Writes down what was agreed on the call so nobody remembers it differently later.

Subject: Recap: what we agreed for [Project]

Hi [Client],

Great call today. To make sure we're on the same page:

In scope:
- [Deliverable 1]
- [Deliverable 2]
- [Number] rounds of revisions per deliverable

Not in scope (happy to quote separately):
- [Item]
- [Item]

Decisions made today:
- [Decision]

Open questions (owner, date):
- [Question] ([who], by [date])

Please reply "confirmed" or tell me what to change. Once confirmed, this is the scope we'll work from.

Thanks,
[Your name]

3. The kickoff meeting agenda (send the day before)

Keeps the call short and makes sure scope, feedback and payments all get covered.

Subject: Agenda for tomorrow's [Project] kickoff

Hi [Client],

Here's the plan for tomorrow ([time], [length]):

1. Goals: what does success look like for you? (5 min)
2. Scope walk-through: deliverables, what's included, what isn't (10 min)
3. Timeline and milestones (5 min)
4. Feedback: who approves, how many rounds, how quickly (5 min)
5. Changes: how new requests are quoted and approved (5 min)
6. Access, files and next steps (5 min)

If someone else signs off on the work, please invite them too.

See you then,
[Your name]

4. The first check-in (end of week one)

Shows progress early and flags anything drifting from the scope before it grows.

Subject: [Project] week one update

Hi [Client],

Quick update on week one:

Done: [what's finished]
Next: [what's coming, by date]
Need from you: [files, access, decisions] by [date]

One note: [request] came up this week. It isn't in the agreed scope, so I'll send a short change order with the price and timing. Nothing changes until you approve it.

Thanks,
[Your name]

5. The how-we-handle-changes note (send once, early)

Sets the rule for extra requests before the first one arrives, so it never feels personal.

Subject: How we'll handle new ideas on [Project]

Hi [Client],

New ideas usually come up once a project gets going, and that's a good thing. Here's how we'll handle them so the timeline and budget stay clear:

1. You send the request any time.
2. I reply within [1 working day] with a short change order: what it is, the price and the effect on the deadline.
3. You approve it with one click (no login), or we park it for later.
4. Work on it starts after approval.

Anything already in the scope is covered, of course. This only applies to new things.

Thanks,
[Your name]

Tips

• Attach the scope to the very first email, so it's the document everyone starts from.
• Ask for one combined round of feedback with one approver, and name that person.
• Send the changes note before the first extra request, not in reply to it.
• Keep every confirmation in one thread so it's easy to find at sign-off.

Need the scope itself? Start with the one-page statement of work template, set your rounds with the revision clause generator and price extras with the change order template. When the project ends, use the project closeout checklist.

Keep the scope you kicked off with

ScopeLine stores the scope you agreed at kickoff, logs every extra request against it, and sends change orders the client approves through a no-login link. Free for 3 active projects, no card.