# Website project inquiry — fictional example

Form build brief created with Plainview Web’s Form & Intake Planner.

This is a specification, not a functioning submission form. Preview answers are not included.

## Introduction

A fictional form plan for a website project inquiry\. Adapt the questions and confirmation to the actual business before building a working form\.

## 1. About the project

A short outline is enough to begin\.

**Show:** always.

### 1.1 What kind of project is this?

- Identifier: field-project-type
- Type: select
- Required: Yes
- Help: Choose the closest match\. It is fine to be unsure\.
- Destination mapping: Not decided\.
- Choices, in order:
  - New website
  - Improve an existing website
  - Not sure yet

### 1.2 What would you like the website to help people do?

- Identifier: field-goal
- Type: textarea
- Required: Yes
- Help: For example\: request a quote, find articles or book a service\. A few sentences are enough\.
- Destination mapping: Not decided\.

### 1.3 Is there a date you are working toward?

- Identifier: field-timing
- Type: text
- Required: No
- Help: Optional\. A month, an event or Flexible is fine\.
- Destination mapping: Not decided\.

## 2. The existing website

Share a link if one is available\.

**Show when:** What kind of project is this? [field-project-type] equals Improve an existing website. Hidden follow-up sections stay hidden if their source section is hidden.

### 2.1 What is the existing website address?

- Identifier: field-website
- Type: text
- Required: No
- Help: Optional\. Include the full address, such as https\://example\.com\.
- Destination mapping: Not decided\.

## 3. How to reply

These details make a project reply possible\.

**Show:** always.

### 3.1 Your name

- Identifier: field-name
- Type: text
- Required: Yes
- Help: The name to use when replying\.
- Destination mapping: Not decided\.

### 3.2 Email address

- Identifier: field-email
- Type: email
- Required: Yes
- Help: The project reply will go to this address\.
- Destination mapping: Not decided\.

## Confirmation message

Thank you for sharing your project\. Your inquiry has been received\. The next step is a reply to the email address you provided\.

## Delivery and handoff decisions

These decisions describe the intended implemented form. No destination is connected, and no request is sent by this planner.

### Intended recipient

Not decided\.

### Submission destination

Not decided\.

### Follow-up owner

Not decided\.

### Follow-up timing

Not decided\.

### Storage and access

Not decided\.

### Retention and deletion

Not decided\.

### Successful submission behavior

Not decided\.

### Visitor failure message

Not decided\.

### Failure and retry handling

Not decided\.

### Duplicate handling

Not decided\.

## Delivery test checklist

Statuses and notes are manually recorded by the plan's author. This planner does not run delivery tests or verify a passed result. Record actual checks on the implemented form; use fictional data and an authorized test destination.

### Destination and recipient

Send an authorized test through the implemented form and confirm the intended destination, recipient and follow-up owner receive it.

- Recorded status: Not checked
- Notes: No test notes recorded\.

### Field mapping

Compare every accepted answer with its intended destination field, including optional and empty values.

- Recorded status: Not checked
- Notes: No test notes recorded\.

### Conditional paths

Test each conditional path and confirm hidden follow-up answers are cleared and excluded from delivery and storage.

- Recorded status: Not checked
- Notes: No test notes recorded\.

### Validation and accessible errors

Test required and invalid answers, accessible error recovery and server-side validation on the implemented form.

- Recorded status: Not checked
- Notes: No test notes recorded\.

### Success confirmation

Verify when the request is accepted and when confirmation appears. Check the next-step wording against the actual follow-up process.

- Recorded status: Not checked
- Notes: No test notes recorded\.

### Failure and retry

Test an authorized failure scenario, retained answers, visitor message, retry behavior and the owner's alert or review process.

- Recorded status: Not checked
- Notes: No test notes recorded\.

### Duplicate requests

Check repeated clicks and retries after an uncertain response; confirm duplicate handling without silently discarding a new request.

- Recorded status: Not checked
- Notes: No test notes recorded\.

### Storage, access and deletion

Check authorized access and the agreed retention/deletion process across stored answers, notifications and other copies.

- Recorded status: Not checked
- Notes: No test notes recorded\.

## Implementation reminders

- Resolve unfinished recipient, field mapping, storage and retention decisions before collecting answers.
- Build server-side validation, spam protection and accessible error messages.
- Clear and exclude answers when their conditional section becomes hidden.
- Decide any additional format, length, range, consent or delivery requirements.
- Test the finished form’s delivery and confirmation behavior; a local preview does not establish that a request reaches its destination.