# Trade enquiry form review

Use privately with the owner and website implementer. The CSV matrix is a worked planning example; it is not evidence of conversion improvement or a universal requirement.

## Field decisions

Record the actual offered service and form purpose. For each field, identify the first decision it supports, whether it is required/optional/conditional and who needs it. Agree contact choice behaviour: phone-only, email-only or a choice requiring one usable selected detail. Agree which unknown/not-sure answers are valid.

Write labels, help, permitted formats and clear error messages. Decide why any street address, files or other personal information is needed now; record private access/storage/retention handling in the business's own reviewed process. Keep newsletter/marketing choices separate. This sheet does not assess legal compliance.

## Controlled test record

Use an agreed test environment where possible. Authorise and label any live test before submission; editorial has submitted no test enquiry. Keep tests out of real lead totals.

| Check | Observed result / evidence | Owner / follow-up |
| --- | --- | --- |
| Phone path can submit without email when supported | | |
| Email path can submit without phone when supported | | |
| Empty contact detail is rejected appropriately | | |
| Required fields explain what is missing | | |
| Optional fields and uploads can be skipped | | |
| Unknown technical detail / not-sure service works | | |
| File type/size limits appear before upload | | |
| Failed file upload has a useful recovery path | | |
| Entered details survive a recoverable error | | |
| Keyboard focus reaches controls and messages | | |
| Visible labels and instructions stay available | | |
| Phone screen layout is readable | | |
| Server acceptance verified in the intended private record | | |
| Request reaches the person/system handling it | | |
| Failure does not display a misleading success | | |
| Success message distinguishes request from booking | | |
| Public reply-time/availability wording is owner-confirmed | | |

Do not store actual customer details or test credentials in this public template. Keep any populated working copy private.