cross circle-down

Scroll-progress stopwatch inspired by Ryan Mulligan’s scroll-driven animation experiment and adapted for this WordPress resource template.

Templates

Website Project Kickoff Questionnaire

A structured intake template for gathering goals, audiences, content needs, technical constraints, approvals, and launch requirements before implementation.

Template

This questionnaire helps turn a loose project request into a practical implementation brief for WordPress design and front-end development work.

Use this when

  • A new website, landing page, or block system project is starting.
  • The team needs to clarify scope before estimating or building.
  • Content, approvals, and technical constraints are still fuzzy.

Project overview

  • What is the main goal of this project?
  • What problem should the new page, site, or feature solve?
  • Is this a new build, redesign, cleanup, or extension of an existing site?
  • Who needs to approve the final work?
  • What does success look like after launch?

Audience and content

  • Who is the primary audience?
  • What action should visitors take?
  • Which pages, sections, or content types are required?
  • Is final copy ready, in progress, or still being planned?
  • Are there existing pages or assets that need to be reused?

Design and interface needs

  • Are there approved designs, wireframes, or brand guidelines?
  • Are there existing components or blocks that should be reused?
  • Which responsive states need extra attention?
  • Are there examples of sites or interfaces that feel close to the desired direction?

Technical requirements

  • Does the project require forms, filters, custom post types, or third-party integrations?
  • Will editors need reusable fields, blocks, or templates?
  • Are there accessibility, performance, or browser support requirements?
  • Does the work need to fit into an existing WordPress theme or plugin setup?

Approval and launch details

  • What is the desired launch date?
  • What needs to be reviewed before launch?
  • Who will enter or maintain content after handoff?
  • What post-launch support or documentation is needed?

Quality check

  • Separate must-haves from future enhancements.
  • Flag dependencies before development starts.
  • Translate answers into build tasks, not just notes.