The playbook
Website Planning: Template and Field Guide
This website planning template turns a broad task into a record another person can use. It captures audience, task, page, then connects that information to a decision. Copy the table into your working document or system and create a separate record for each item in scope.
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.
Copyable worksheet
| Field | Entry instructions |
|---|---|
| audience | Record the audience associated with this page or interaction record. Use a stable reference so later updates can be matched. |
| task | Record the task associated with this page or interaction record. Keep the value specific enough for another owner to interpret. |
| page | Record the page associated with this page or interaction record. Keep the value specific enough for another owner to interpret. |
| function | Record the function associated with this page or interaction record. Keep the value specific enough for another owner to interpret. |
| owner | Record the owner associated with this page or interaction record. Keep the value specific enough for another owner to interpret. |
| Decision field | Entry instructions |
|---|---|
| Observed problem | Describe the actual condition and where it was observed. |
| Recommended action | State the smallest action that resolves the documented problem. |
| Evidence | Link to the record, observation, or test supporting the action. |
| Owner and next review | Name the accountable person and when the decision should be revisited. |
How to complete the worksheet
Begin with audience. Use the same reference throughout the record so notes are not attached to the wrong item. Then list the primary audiences and their decisions. This establishes the information required before the worksheet becomes a request for action.
Next, map each decision to content and functionality. Use the observed problem and evidence fields to explain why that step is needed. A useful entry describes an actual condition, such as starting visual design before the business goal is clear, rather than a broad instruction to “improve performance.”
Finally, agree on launch scope and acceptance criteria. Put write a short brief with one primary visitor outcome in the action field only when it addresses the observed condition. If the problem is different, change the action. The template is a structure for judgment, not a reason to apply the same fix everywhere.
Illustrative completed decision
| Part | Illustrative entry |
|---|---|
| Problem | Starting visual design before the business goal is clear |
| Action | Write a short brief with one primary visitor outcome |
| First check | List the primary audiences and their decisions |
| Follow-up check | Agree on launch scope and acceptance criteria |
| Outcome to define | priority visitor tasks supported |
Adapt the fields without losing meaning
You can add fields required by your team, but each should change a decision or preserve necessary context. Keep factual observations separate from recommendations. If task changes, record the new value and its effective date instead of silently rewriting the context of an earlier decision.
Use the record in a handoff
Ask the receiving owner to explain the next action using only the worksheet. Missing context becomes visible quickly during that exercise. Repair the record before applying the structure to a larger batch. Keep priority visitor tasks supported connected to the item so the team can later assess whether the action was useful.
Treat visual changes and functional changes separately in the change log. A clearer label may improve comprehension, but a broken submission destination still prevents completion. Confirm both understanding and successful delivery.
Skip the manual steps. Let AgentixHUB run this for every client.
Start now