The problem
A project that starts with a quick call and a “sounds good, let’s go” often surfaces its first real misunderstanding at delivery — by which point fixing it costs far more than a 15-minute kickoff conversation would have.
Expected outcome
By the end of this guide you will have a kickoff checklist covering the three points where misunderstandings most commonly slip through: before you start, during the actual kickoff conversation, and immediately after.
Requirements and costs
- Any text editor.
- Cost: free.
Step-by-step implementation
- Download the checklist from the link below.
- Work through “Before kickoff” before you schedule the actual kickoff conversation — scope, success criteria and budget should all already be in writing by then.
- Use “At kickoff” as your actual meeting agenda — walking through scope out loud catches things a written document alone doesn’t.
- Complete “After kickoff” within 24 hours — a written summary sent while the conversation is still fresh prevents “I thought we agreed…” disputes weeks later.
A real example
“Success criteria are specific enough that you’d both agree, at the end, whether they were met” sounds obvious written down, but it’s the single most commonly skipped item — “make the site better” isn’t a success criterion; “page load under 2 seconds and a working checkout” is.
Verification and troubleshooting
What we actually checked: the checklist’s three phases (Before kickoff, At kickoff, After kickoff) are present, with 11 concrete, checkable items across them — none of the vague “communicate well” style items that sound right but can’t actually be checked off. This is a structural check of the template file, not a record of a specific real project.
Troubleshooting:
- The client doesn’t want a formal kickoff. You don’t need to call it a “kickoff meeting” — cover the same ground in whatever conversation starts the work, even informally.
- Something wasn’t resolved by the end of kickoff. Write it down under “anything left open” rather than letting it quietly disappear — an acknowledged open question is far easier to deal with later than a forgotten one.
- You’re the only side tracking any of this. That’s fine — the summary you send after kickoff creates a shared written record even if the other side never looks at a checklist themselves.
Free vs. paid
This is free and complete as a Markdown checklist. Paid project management tools add shared tracking across a whole team and automatic reminders — useful at scale, not necessary for a single project’s kickoff.
What to do next
Keep the sent kickoff summary somewhere you’ll actually find it again later — a dedicated project folder, not just buried in an email thread — so it’s there to check against if a disagreement about scope comes up weeks into the work.
Free resources
The download is the full checklist.
Download the project kickoff checklist (ZIP, 1 KB)
Is there a paid version?
Not yet. This is the complete method. TNT Review has sold nothing to date and has no checkout, so any price we discuss in future should be read as a hypothesis, not an offer.