Adapt a form to your organisation

Your organisation's actual work shapes a form more than its industry label does.

Design guidance version: 2026-10-20.1

Use your own context

Combine the purpose and respondent with approved Knowledge, Catalog items and your instructions. These considerations explain why a question might help; they don't require questions or establish legal obligations. An industry label never justifies sensitive collection by itself.

Consider the work the form supports

| Organisation | Questions to consider when designing | | --- | --- | | Retail | Enquiry, Order or return? Use actual products and variants. Delivery details matter only when delivery is relevant. | | Food | Enquiry, table Booking or Order? Use the current menu and service. Dietary information needs a specific purpose and careful handling. | | FMCG | Household customer, retailer or distributor? Pack sizes and delivery needs follow the approved offer, not assumptions about wholesale trade. | | Hospitality | Who is staying and who is arranging it? Use the actual property and services. Guest and accessibility details need a reason. | | Health | Administrative request or clinical intake? Don't turn an enquiry into medical assessment. Health questions need justification and a suitable route. | | Education | Nursery, school or adult programme? Separate parent and applicant details. Use approved classes; don't invent admission requirements. | | Professional services | What help is requested, and who is the client? Ask enough to direct it, avoiding unnecessary confidential documents and case details. | | Beauty | Which service and preparation are relevant? Don't infer health needs from a service name. Justify sensitive follow-ups separately. | | Property | Property interest, viewing or application? Use the actual listing. Don't invent affordability tests or request financial evidence at first enquiry. | | Automotive | Vehicle enquiry, service or parts request? Match vehicle details to the task. Ownership documents need an established reason. | | Finance and insurance | Enquiry or approved application? Don't invent eligibility, compliance questions or financial advice. Never collect payment security details. | | Nonprofits | Supporter, volunteer or person seeking assistance? Protect beneficiary information. A sign-up shouldn't require details of hardship. | | Events | Enquiry or registration? Use approved sessions and ticket choices. Separate attendee details from the person booking. | | Logistics | Quote request or existing delivery? Collect relevant locations, parcel details and timing. Don't promise unconfirmed routes, prices or services. | | Technology | Enquiry, support or onboarding? Ask for the goal and relevant product context. Never request passwords, one-time codes or secret keys. |

Review before using the design

Keep the smallest useful set. Check each question's reason, whether it's required, who it describes and the source of its choices. Leave extras and sensitive suggestions unselected. Supply missing choices in the review.

Choose the existing submission outcome and check each intended channel separately. A form submission doesn't itself approve an application, confirm a Booking or overwrite established customer details.

When a consideration doesn't apply

Ignore guidance for work you don't do. Keep unknown respondents or services open for review. If Qyra can't prepare a design, try again with the purpose and business details. Form edits and submitted answers never update this approved guidance automatically.

Related

• Choose the right questions for a form
• Match a form to its purpose
• Decide what happens after someone submits