Building the form is the easy half. Dragging fields into place takes a few minutes and the interface does not fight you. What costs time is a handful of choices made in the first thirty seconds that are tedious to reverse once forty questions sit on top of them, plus one step at the end that people skip and then spend an afternoon debugging.
So this walks the official route through the builder and stops at each point where a decision gets locked in. The steps themselves come from Jotform's own guide. The commentary is about which ones matter later.
Decide three things before opening the builder
None of these take long to settle on paper and all three are annoying to change afterwards.
The layout. Jotform offers two: a classic form, which shows every question on a single page, and a card form, which shows one question per page. This is not a styling preference. It changes how long the form feels, how respondents scan it, and whether section headings do any work. Long forms on a phone generally do better one question at a time. Forms where somebody needs to see all the options at once, such as an order with variants, generally do better on one page.
Which questions are required. Marking everything required feels thorough and costs completions, because a respondent who cannot answer one question abandons the whole form rather than sending a partial one. Decide the minimum set that makes a submission usable, and leave the rest optional.
Who gets told. A submission that nobody sees is the only true failure mode of a form. Decide the address or the channel before building, because the notification step is near the end of the process and is the one most often left at its default.
Write the question list somewhere plain first. Editing a list is faster than editing a form, and it stops the builder from turning into the place where the thinking happens.
While the list is open, give the form a name that will still make sense in a year. The workspace listing is the only place anyone will look for it later, and a workspace full of entries called Form and Copy of Form is how organisations end up with three versions of the same intake collecting answers in parallel.
Starting from scratch
The route through the interface is short. On the My Workspace page, click Create at the top left, then click Form in the window that opens. At that point there are two ways forward: Start from Scratch, or Use Template to pick from over 20,000 premade forms.
Choosing Start from Scratch presents the layout choice described above, as Classic Form or Card Form. After that the Form Builder opens with an Organization Settings prompt, which offers to upload an organisation logo, edit the organisation name, save those changes, or dismiss the prompt. There is also a Don't Show This Again option on it.
That prompt is worth two minutes rather than a dismissal. The logo and name appear on the form respondents see, and a form carrying no identity at all reads as a phishing page to anyone who received the link secondhand.
Adding the fields
In the Form Builder, the Add Element menu on the left holds everything that can go on the form, split across three tabs.
The Basic tab covers the fields most forms are made of: name, email, short and long text, multiple choice, dropdown and date picker. The Payments tab holds the payment gateway elements, including PayPal, Stripe and Square. The Widgets tab holds the more advanced fields, including e-signatures, file uploads, rating scales and progress bars. Elements are dragged from the list onto the form.
Two things are worth knowing before the field count climbs. The first is that field allowances differ by plan: the free Starter plan allows 100 fields per form, Bronze 250, Silver 500 and Gold 1,000. For an ordinary intake form that ceiling is irrelevant. For a long application or an assessment rebuilt each cycle by adding to last year's version, it is reachable.
The second is that a payment element changes what the form is metered against. Payment submissions are counted separately from ordinary submissions on every plan, at 10 a month on Starter, 100 on Bronze, 250 on Silver and 1,000 on Gold. Adding a payment field to a busy form is the fastest way to hit a limit that has nothing to do with how many people filled the form in.
Conditional logic is the alternative to a longer form, and it is worth reaching for earlier than most people do. Jotform lists conditional logic among its features, and the effect is that a question only appears when a previous answer makes it relevant. A form with forty questions of which any given respondent sees twelve completes far better than a form with twenty that everybody has to read past.
Keep the field order close to the order a person would naturally answer in. Contact details first, the substance in the middle, consent and file uploads last. Uploads at the end matter in particular, because they are the step most likely to fail on a phone, and a failure at the end costs you one answer rather than all of them.
Changing how it looks
Design lives behind the paint roller icon at the top right of the Form Builder, which opens the Form Designer. It has four tabs: Colors for background, button and text colours; Styles for font, spacing and field alignment; Themes for premade designs; and Layout for switching between the single page classic format and the one question per page card format.
That last tab is the reason to settle the layout decision early. Switching it here does work, and it also changes which questions sit together, which section descriptions still make sense, and where the form feels long. Doing it after the form is built means reading every question again.
Colour and font choices are worth less attention than the amount of interface devoted to them suggests. The two things that genuinely affect completion are how the form behaves on a phone and how clear the question wording is. A form in default styling with well written questions outperforms a branded one that asks vaguely.
Setting up the emails
Jotform creates an email notification automatically when a form is created, so a new form normally notifies the account already. Creating another one, or checking the existing one, follows the same path: in the Form Builder, click Settings in the orange navigation bar at the top, click Emails in the left menu, click Add Email, then select Notification Email. The Recipients tab is where the address goes, and Save finishes it.
There are two distinct kinds of email and conflating them causes most of the confusion here. A notification goes to you or your team when a submission arrives. An autoresponder goes to the person who filled the form in. They are configured separately.
Skipping the autoresponder is a false economy. Without a confirmation, a proportion of respondents will assume the form failed and either submit again or send an email asking whether it went through. Both outcomes create more work than writing two sentences of confirmation would have. The autoresponder is also the natural place to say what happens next and by when, which removes a second wave of chasing messages.
For notifications, send them somewhere more durable than one person's inbox where possible. A notification that only reaches the person who built the form is a single point of failure, and it fails silently the week that person is away.
Publishing and the step nobody should skip
Publishing is a click. In the Form Builder, click Publish in the orange navigation bar, then Copy link, and send that link wherever it needs to go. Jotform also documents sending a form by email, and its templates are described as embeddable in a website, so a link is not the only route.
Testing is the step that gets skipped. Toggle Preview Form on at the top right, fill the form in, and submit it. Then check two things: that the notification email actually arrived at the address you set, and that the entry appears in the submissions table where you expect to read it.
That single test catches almost every real failure. A notification pointed at an old address, a required field that cannot be completed on a phone, a payment element not connected to an account, a file upload that rejects the size people will actually send. All of it surfaces in two minutes, and none of it surfaces from looking at the form in the builder.
One habit worth adopting: do the test from a signed out browser or a phone, not from the tab you built the form in. The builder view and the respondent view are not the same thing, and problems that only appear to strangers are the ones that cost you submissions.
What the builder does not set up
The form now collects answers into a table, and that is where the tooling stops and the manual work starts.
A submission in that table has no owner. Nothing records which colleague is dealing with it. It has no status either, so there is no difference visible between an entry read this morning and one answered last week and closed. The reply is sent from somebody's mail client, which puts the record of what was said in one person's sent items rather than beside the submission it answers.
Teams bridge this with a spreadsheet export and a column typed in by hand. It holds together while one person maintains it and comes apart when two people sort the sheet at once. The seat count makes that likelier than it sounds: Jotform lists one user on Starter, Bronze, Silver and Gold, and describes Enterprise as its only multiuser platform, so shared handling on the cheaper plans happens outside the tool by design.
That is worth knowing at the point of building rather than six months later, because the shape of the form barely matters to it. A perfectly built form and a rough one create the same amount of follow up work if the follow up has nowhere to live.
What to change first
Settle the layout and the required fields on paper, then build, then run one test submission from a phone and confirm both the notification and the stored entry. That sequence prevents most of what goes wrong. If the part that actually consumes the week is what happens after the answers land, look at how response handling works on one screen and try it on live submissions. Halict keeps forms and responses unlimited and charges only for the number of people, so a second person reading the responses is not an upgrade decision.
Q1. How do you start a new form in Jotform?
On the My Workspace page, click Create at the top left, then Form. Choose Start from Scratch or Use Template, then pick Classic Form, which shows all questions on one page, or Card Form, which shows one question per page. The Form Builder then opens with an Organization Settings prompt for a logo and organisation name.
Q2. What is the difference between a Classic Form and a Card Form?
Classic displays every question on a single page. Card displays one question per page. Card tends to suit long forms and phone respondents, while classic suits forms where somebody needs to compare options side by side, such as an order with variants. The setting can be switched later under the Layout tab in the Form Designer, but doing so changes how the questions group together.
Q3. Where are email notifications set up on a Jotform form?
In the Form Builder, click Settings in the top navigation bar, then Emails, then Add Email, then Notification Email, and enter the address on the Recipients tab. Jotform creates a notification automatically when a form is made, so the more common task is checking the existing recipient rather than adding one.
Q4. How do you test a Jotform before sending it out?
Toggle Preview Form on in the top navigation bar, fill the form in and submit it, then confirm the notification email arrived and the entry appears in the submissions table. Do it from a phone or a signed out browser rather than the tab the form was built in, since that is where problems with required fields and uploads actually show up.
Q5. How many fields can one Jotform form have?
The allowance depends on the plan: 100 fields per form on the free Starter plan, 250 on Bronze, 500 on Silver and 1,000 on Gold. Most intake forms are nowhere near that. The limit tends to appear on long applications and on assessments rebuilt each year by adding to the previous version.