The playbook
Website Template Selection: Template and Field Guide
This website template selection template turns a broad task into a record another person can use. It captures template, required task, fit, 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
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.
Copyable worksheet
| Field | Entry instructions |
|---|---|
| template | Record the template associated with this page or interaction record. Use a stable reference so later updates can be matched. |
| required task | Record the required task associated with this page or interaction record. Keep the value specific enough for another owner to interpret. |
| fit | Record the fit associated with this page or interaction record. Keep the value specific enough for another owner to interpret. |
| modification | Record the modification 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 template. Use the same reference throughout the record so notes are not attached to the wrong item. Then list required pages and interactions. This establishes the information required before the worksheet becomes a request for action.
Next, test the template with realistic content and devices. Use the observed problem and evidence fields to explain why that step is needed. A useful entry describes an actual condition, such as choosing solely from a polished homepage thumbnail, rather than a broad instruction to “improve performance.”
Finally, estimate changes needed for brand and functionality. Put inspect navigation forms content length and mobile behavior 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 | Choosing solely from a polished homepage thumbnail |
| Action | Inspect navigation forms content length and mobile behavior |
| First check | List required pages and interactions |
| Follow-up check | Estimate changes needed for brand and functionality |
| Outcome to define | required tasks supported by the template |
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 required 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 required tasks supported by the template connected to the item so the team can later assess whether the action was useful.
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