The playbook
Website Template Selection: Checklist
Use this website template selection checklist before a new release, a handoff, or a scheduled review. Its purpose is to verify the decisions that affect required tasks supported by the template. 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
Replace demonstration text with a realistic service description and a longer business name. Test the menu, forms, and mobile layout. A template that looks strong with minimal sample content may require substantial changes for the actual business.
Before you use the checklist
Name the exact item being checked and its purpose. Gather template, required task, fit, modification. 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 required pages and interactions | A dated observation showing how template was verified | website lead |
| Test the template with realistic content and devices | A dated observation showing how required task was verified | designer or developer |
| Estimate changes needed for brand and functionality | A dated observation showing how fit was verified | site owner |
Check the failure path
- Look specifically for this failure: choosing solely from a polished homepage thumbnail.
- Inspect navigation forms content length and mobile behavior. Record the actual correction, not just the intention to make it.
- Repeat the affected task after the correction and check modification.
- 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 required pages and interactions,” a meeting about the subject is not the evidence itself. Retain the relevant template and required 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 choose a starting design based on the business journey it must support 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 required tasks supported by the template using a consistent definition so later reviews can connect execution quality with useful results.
Verify the actual visitor journey on a narrow screen and with a keyboard. A design can look complete while hiding an unreachable control or a missing confirmation. Record the task attempted and what happened at the end.
Skip the manual steps. Let AgentixHUB run this for every client.
Start now