Build a reusable kickoff without making it generic
Standardize the collection system while keeping each client’s project specific.
A reusable kickoff should preserve the questions your team repeatedly needs, not force every client through the same irrelevant questionnaire. The most useful template has a stable core and a deliberate project-specific layer.
Start with recurring dependencies
Review recent projects and list the inputs that repeatedly blocked work: decision owner, access, content, brand files, constraints and launch dates.
Phrase each item so a first-time client knows what to provide. Internal shorthand belongs in team notes, not client-facing requests.
- Why the item is needed
- What a usable response looks like
- When it becomes necessary
Add conditional sections
Ask follow-up questions only when they apply. Ecommerce, multilingual content and data migration each need different branches.
Shorter relevant forms earn better answers than giant “comprehensive” forms. Gather templates can be duplicated and adjusted without carrying forward prior client answers.
- Core questions for every project
- Conditional questions by project type
- One-off risks for this client
Improve the template after delivery
At handoff, note which request was unclear, missing or unnecessary. Change the template while the evidence is fresh.
Keep an owner and revision date for the template. A reusable system stays useful only when someone curates it.
- Remove low-value questions
- Add the missing decision or format
- Update examples and ownership
