The playbook
Website Planning: Checklist
Use this website planning checklist before a new release, a handoff, or a scheduled review. Its purpose is to verify the decisions that affect priority visitor tasks supported. Check an actual page or interaction record; a box marked complete without evidence does not show that the customer journey works.
Put the task in context
For a home-services site, define whether the primary action is an emergency call, a scheduled visit, or an estimate request. Each implies different information and routing. Decide which action applies to each service before choosing the page layout.
Before you use the checklist
Name the exact item being checked and its purpose. Gather audience, task, page, function, owner. If one of those details is unknown, mark it as unknown and assign a way to resolve it. An invented value makes the checklist look complete while weakening every later decision.
Working checklist
| Check | Evidence to keep | Responsible role |
|---|---|---|
| List the primary audiences and their decisions | A dated observation showing how audience was verified | website lead |
| Map each decision to content and functionality | A dated observation showing how task was verified | designer or developer |
| Agree on launch scope and acceptance criteria | A dated observation showing how page was verified | site owner |
Check the failure path
- Look specifically for this failure: starting visual design before the business goal is clear.
- Write a short brief with one primary visitor outcome. Record the actual correction, not just the intention to make it.
- Repeat the affected task after the correction and check owner.
- Make sure the next owner can find the decision and supporting evidence.
Use three outcomes for each check
Mark an item as complete only when the expected behavior or information has been observed. Mark it as incomplete when a required condition is absent. Use not applicable when the condition genuinely does not belong to the chosen scope, and write a short reason. These states keep a review useful without forcing every process into an identical mold.
For example, if the check is “List the primary audiences and their decisions,” a meeting about the subject is not the evidence itself. Retain the relevant audience and task, the decision made from them, and the result of checking that decision. The record should allow someone who missed the meeting to understand what changed.
Decide what must be resolved first
An incomplete item that prevents define what a website must help visitors do before design or development begins deserves attention before a cosmetic improvement. Assign an owner and a next action to that issue. Keep optional refinements visible, but do not let them obscure a failure in the core process.
Close the review
Recheck corrected items and note anything still uncertain. The checklist is finished when the next owner understands what was verified and what remains open. Follow priority visitor tasks supported using a consistent definition so later reviews can connect execution quality with useful results.
Use realistic content lengths and assets during review. Short placeholder headings can conceal overflow and hierarchy problems that appear with real service names, prices, or instructions. Check the result after the final content is inserted.
Skip the manual steps. Let AgentixHUB run this for every client.
Start now