Turn a list of questions into a form

How a line becomes a field

The model reads each question and picks a field type from the toolkit, guided by the generator's own rules. Names become a full name field and addresses an address field rather than several separate boxes. Repeated data, such as a list of items with the same details, becomes a table. Emails and phone numbers become short text fields. Dates, times and quantities usually become date, time and number fields, and an open question that invites a paragraph becomes a long text box. It is a judgement from the wording, not a fixed rule, so a line that says what it wants gets the right type more often.

How required flags are chosen

Unless you say otherwise, the generator follows a required field strategy: identity fields such as name and email, the main purpose of the form, consent statements and signatures on legal forms are marked required. Optional preferences, a second contact method, comments and "how did you hear about us" questions are not. It aims for roughly three to six required fields on a ten field form. A note on the line saying optional or required is a stronger signal than that default, so write it where it matters.

Writing choices so they survive

Put the options on the same line as the question, after a colon or in brackets, separated by commas, for example Team size: 1 to 10, 11 to 50, 51 to 200, more than 200. Say "choose all that apply" when several answers are allowed, because a bare list reads as a single choice. Whether a single choice question becomes radio buttons or a dropdown is the model's call; name the control on the line if you care which.

Labels may be tidied, so say when they must not be

The generator writes labels in one consistent tone suited to the form, so "Could you tell us your full name please" may come back as Full name. That is usually an improvement. When the wording is fixed, such as a screening question from a policy or a consent sentence approved by a lawyer, say in the prompt that those lines must be kept word for word. The prompt text itself is used exactly as you pasted it.

Moving from another form tool

This is the quickest route off another builder when there is no clean export. Copy the question list out of the old form, paste it in, then rebuild only what a plain list cannot carry: file uploads, photo fields, signatures and design blocks. Those take a few clicks each in the builder, and they are the parts worth rethinking anyway.

How it works, in three steps

1. Step 1

   Paste the questions, one per line

   Start with a sentence saying what the form is for. Put choices after a colon, and mark optional or required questions on the line.

2. Step 2

   Pick classic or conversational

   A long list someone works through at a desk suits a classic form. A short list for strangers on a phone suits conversational, one question at a time.

3. Step 3

   Add the parts a list cannot carry

   Uploads, photos and signature fields are added in the builder, then read the required flags once before publishing.

The full walkthrough with screenshots is in the guide Create a form from scratch with AI.

Limits worth knowing

• The prompt box takes 10,000 characters, which is roughly 1,200 words.
• A plain list carries no file uploads, photos or signatures. Add those in the builder.
• Field types and required flags are chosen by the model from the wording, so check them before publishing.
• Options you list are used as written, so tidy them before pasting.

See it on a finished piece

Customer feedback survey

6 fields

Conference registration form

11 fields

Volunteer signup form

10 fields

Questions people ask

Related pages