The playbook
Form Design: Template and Field Guide
This form design template turns a broad task into a record another person can use. It captures field, purpose, validation, 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
An email field should explain an invalid value in plain language and preserve the other entered information. Group related questions and identify required fields clearly. Use the appropriate input type, but also validate on the receiving system.
Copyable worksheet
| Field | Entry instructions |
|---|---|
| field | Record the field associated with this page or interaction record. Use a stable reference so later updates can be matched. |
| purpose | Record the purpose associated with this page or interaction record. Keep the value specific enough for another owner to interpret. |
| validation | Record the validation associated with this page or interaction record. Keep the value specific enough for another owner to interpret. |
| error message | Record the error message 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 field. Use the same reference throughout the record so notes are not attached to the wrong item. Then ask only for fields needed at the current stage. This establishes the information required before the worksheet becomes a request for action.
Next, use visible labels useful hints and specific errors. Use the observed problem and evidence fields to explain why that step is needed. A useful entry describes an actual condition, such as showing a generic error without identifying the affected field, rather than a broad instruction to “improve performance.”
Finally, preserve entered information when a recoverable error occurs. Put explain the issue beside the field and provide a recovery path 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 | Showing a generic error without identifying the affected field |
| Action | Explain the issue beside the field and provide a recovery path |
| First check | Ask only for fields needed at the current stage |
| Follow-up check | Preserve entered information when a recoverable error occurs |
| Outcome to define | successful form completions |
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 purpose 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 successful form completions connected to the item so the team can later assess whether the action was useful.
Keep the page’s main task visible when adding helpful detail. Supporting information should reduce uncertainty at the decision point. If a section introduces a second unrelated offer, decide whether it belongs on another page.
Skip the manual steps. Let AgentixHUB run this for every client.
Start now