The Blueprint Tab, Field by Field

Step 1: Adding a Field

Open your event and click into the Blueprint tab. Every field on your form is listed down the left, grouped under Identity, Verify, or Confirmation depending on where it sits in the registration flow. Click the plus button above the field list, or the dashed line between any two existing fields, and the Add to form panel opens on the right.

System Fields are the standard questions Express already understands: prefix, country, mobile number, position or title, and a dozen more. A padlock icon marks fields Express manages for you, like First Name and Email Address. The rest add cleanly with a click and inherit whatever formatting Express already uses for that field elsewhere in your account.

Nothing standard fit what you need? Switch to Blank Field and start from one of eleven types: Text, Long Text, Dropdown, Checkbox, Radio, Number, Date, Email, Yes/No, Rating, or File Upload.

Every field you add lands in the list on the left and in the form preview on the right, with a dashed line between fields where you can insert another. Drag any field by its handle to reorder it. Express saves the order as you go.

Step 2: Configuring a Question

Click any field, and the Field Editor opens on the right. This is where a plain text box becomes a real question: a Question Label your registrants will actually read, a Question Type if you want to change it, and Options for anything with a dropdown, checkbox, or radio list. Add them one at a time, or paste a batch in with Bulk.

Turn on Required, and Express won't let a registrant submit without answering. Field Behavior controls the rest: Normal is the default, Read-Only shows the field but locks the value (useful for something you've already filled in), and Hidden keeps a field on the form without displaying it, usually paired with a visibility rule elsewhere.

Share Row with Above puts two short fields side by side instead of stacking them, first name and last name, for example. Visibility Logic does more. Turn it on and you set a source field, an operator, and a value, so a question only appears when a registrant answers another one a certain way. Ask about dietary needs, then only show the allergy detail field once they've picked an option that isn't "No restrictions."

Under Question Context, a field starts as an Event Question, one that lives only on this form. Toggle it to an Account Question instead, and Express treats it as reusable: build the question once, and every future event can use it, with the same options and the same answer history attached to a registrant's profile.

Description adds optional instructions under the field label. Link to a content block goes further and opens a full reusable rich-text block in a modal from that description, handy for terms and conditions or a longer explanation you don't want cluttering the form itself.

Step 3: Adding Content

Not everything on a registration form is a question. Open Add to form and switch to the Rich Text tab, and you'll find blocks built for exactly that:

• Empty rich text, a blank box you write and format yourself.
• Event welcome, which greets a registrant using your event's own details tokens.
• Important notice, a styled callout for anything a registrant needs to read before scrolling past it.
• Event details block, which pulls in the date, time, and location automatically, so it stays correct even if the event changes later.
• Privacy notice, a ready-made legal disclaimer template.

For a form with more than a handful of fields, Section Header breaks it into named parts, Contact Information, Session Preferences, Dietary Requirements, so registrants can see roughly how much is left instead of scrolling through one undifferentiated list. Add one wherever the form shifts topic.

Step 4: Layout and Preview

Switch to the Layout tab, and Content Layout controls how the whole form sits on the page. Single Column keeps everything centered and simple. Content + Form and Form + Content split the screen so a hero image or event details run alongside the fields instead of above them.

Form Flow changes how a registrant moves through the questions rather than how they're arranged on the page. All Questions puts everything on one scrolling page, best for short forms. Card View (One Per Page) shows a single question at a time with Next and Back controls, built for mobile. Original Structure keeps whatever page groupings you already set up in the Blueprint tab.

Click Preview, and Express renders the form exactly as a registrant will see it: branded header, every field, every conditional rule you set. Toggle between desktop, tablet, and phone views right there before you save, so nothing about Card View or Column Layout is a guess.

For the fields already on a form before you touch the Blueprint tab, see "Express: How to Create an Event Step by Step." For more help, use Help inside Express or contact Certain Support.