A project kickoff checklist for freelancers: plan the first week

Use a project kickoff to turn an approved brief into decisions people can act on: what you will deliver, what is outside the work, who can approve it, which inputs are needed, and what happens first. If the assignment is small and familiar, you can confirm those points in writing instead of booking a meeting.

What should be ready before a kickoff?

Bring the agreed brief, the people needed for the first decisions, and a short list of open questions. A kickoff works best after you have enough agreement to plan delivery. If the client is still choosing the service or deciding what they want to achieve, finish that conversation first.

APM’s guidance on the first project management meeting emphasizes scope, acceptance criteria, responsibilities, and key dates. The checklist below applies those ideas to a small freelance engagement; its timing and examples are suggestions, not an industry standard.

Before the call, check whether the brief names the deliverables and client responsibilities. Use a clear scope of work to resolve missing boundaries. Do not use the kickoff to quietly expand an agreement that was already accepted.

The six decisions to leave with

1. Outcome: state the change the work should make possible. “A sales team can send a clear service overview” is more actionable than “a better brochure.”
2. Deliverable and finish condition: name the output, format, and person who checks it. Distinguish a first draft from an approved final file.
3. Boundaries: name likely requests that are outside this assignment, plus how you will discuss an added request before doing it.
4. Decision owner: identify who gathers feedback and who gives the final answer. Resolve conflicting reviewers before their comments reach the work.
5. Inputs and dependencies: list the material or decisions you need, the person supplying each, and when you need them.
6. First actions: agree the next few tasks, their owners, and the next check-in. Record unanswered questions separately from confirmed decisions.

Be precise about uncertainty. “Copy expected Tuesday; draft date to be confirmed after receipt” is more useful than recording Tuesday as a promise the client has not made.

A 30-minute agenda you can adapt

Suggested agenda for a small project kickoff

Time	Discuss	Record
0–5 minutes	Purpose and intended reader or user	One sentence describing the outcome
5–12 minutes	Deliverables and boundaries	What is included and what would need another conversation
12–20 minutes	Inputs, reviewers, and constraints	Names, required material, and open questions
20–27 minutes	First-week work	Tasks, owners, and realistic dates
27–30 minutes	Read back the decisions	Next check-in and confirmation request

The blocks add up to 30 minutes. Extend the meeting when the decisions need it, or remove it entirely when a written exchange will do. Move a detailed design debate into its own working session so it does not crowd out planning.

Worked example: a two-page service brochure

Imagine a freelancer preparing a two-page PDF brochure for a small consultancy. This is an illustrative project, not a customer case study. The approved assignment includes one layout direction and one consolidated revision round. Copywriting and printing are outside the assignment.

Illustrative first-week plan after the kickoff

Action	Owner	Timing or condition
Supply final copy, logo, and approved images	Client contact	Monday by noon
Check the material and list missing inputs	Freelancer	Monday afternoon
Prepare the first layout	Freelancer	Tuesday and Wednesday, if inputs are complete
Return one consolidated response	Client contact, after consulting the approver	Thursday by 3 p.m.
Apply the agreed revisions	Freelancer	Friday, subject to the response

If final copy arrives Wednesday, the first action is to reassess the plan and confirm the next feasible draft date. The freelancer should not assume that Friday still works or move another client’s work without checking. Trace those conditions with the guide to project dependencies.

Send a short record after the conversation

Use this structure for a kickoff note, filling it with the actual agreement:

Outcome:
Deliverables and finish condition:
Outside this assignment:
Client contact and final approver:
Inputs needed, from whom, and by when:
Next actions, owners, and dates:
Open questions:
Next check-in:

Ask the relevant people to confirm or correct the record. An unanswered message does not establish agreement by itself. Keep proposed changes labeled as proposals until someone with the right authority confirms them.

Put the agreed actions where you plan the work

In ProjectBook’s project workspace, keep the agreed overview in the project description and create tasks for the first actions. Schedule your own work and estimate its duration. If a source document lives elsewhere, include its location in the description; this does not require a proposal generator or a client portal.

Once the project starts, update the actions when facts change. Keep the original agreement available so a revised plan does not erase the decision that preceded it. Explore the project management library for the next stage, from dependencies to delivery.