Trade Show Lead Capture Form: Template, Fields, QR Setup and Follow-Up

A trade show lead capture form is the short, mobile-first form your booth staff or visitors complete in under a minute to record who a person is, what they need, and how they agreed to be contacted. The best version asks only what changes the follow-up, works on a phone through a QR code, and feeds a list your sales team can act on the same day.

This guide gives you a copyable field template (minimum and full versions), a comparison of capture methods from paper to badge scanners, a qualification rubric, a booth workflow, consent guidance, and a follow-up timeline. If you are choosing the layout, read multi-step vs single-step forms first. For the broader catalog of patterns, including the event follow-up form, see lead capture form examples. The definitions used here are in the lead capture form glossary entry.

Why a trade show lead capture form is different from a website form

A website visitor arrives alone, with time, on a device they chose. A booth visitor arrives in a loud hall, holding a coffee and a tote bag, with four other stands to see before the keynote. Everything about the form has to respect that:

• Time budget is measured in seconds. A visitor will give you 30 to 60 seconds of typing, not five minutes. Every field beyond the essentials costs you a lead or costs you accuracy, because people abbreviate and mistype when hurried.
• The device is usually a phone. Either the visitor's own phone (QR code) or a staff tablet. Desktop assumptions about column layout, hover states, and wide dropdowns fail here.
• The conversation already happened. Unlike a cold website visit, someone talked to this person. The form's job is to record that context (interest, timeline, next step) so the follow-up email does not read like a mass blast.
• Consent is collected face to face, so it has to be explicit. A badge scan is not a subscription. The form is where you ask, record, and time-stamp permission.
• The list expires fast. Event leads lose value with every day of silence. The form has to deliver data into a system that a human checks before the show ends, not a spreadsheet someone opens the following Monday.

The rest of this post is built on those five constraints. When a recommendation below feels strict, it is because one of them is behind it.

Trade show lead capture form template (field by field)

Copy the table, delete what does not apply, and keep the two versions separate. The minimum version is what a visitor completes alone by scanning a QR code. The full version is what a staff member completes on a tablet during or immediately after a conversation, because staff will tolerate more fields and can fill them from what they just heard.

A few rules for the template:

One name field. "First name" and "last name" doubles the taps on a phone and breaks for people whose names do not split cleanly. Ask for the full name and split it later if your CRM insists.

Selects beat text. Every question that can be a list of five options should be. Options are tap targets; text fields summon the keyboard. On a tablet the staff member can also tap while still looking at the visitor.

"What are you looking at?" is the most valuable field. It costs one tap and it decides which email the person receives. If your product has one use case, replace it with "What problem brought you to the booth?" and give three to five concrete answers.

Timeline instead of budget. People rarely tell a stranger their budget at a booth, and asking makes the form feel like an interrogation. Timeline is a question people answer honestly, and it correlates with buying intent well enough for triage.

Requested next step is the contract. When a visitor picks "Send pricing," your follow-up email has a purpose and a subject line. When they pick "No follow-up," you still learned something, and you do not burn goodwill by ignoring the request.

Field types listed in the table (text, email, phone, select, radio, checkbox, textarea) are all standard; any form tool should support them. The point is the discipline of which ones to show to whom.

Which capture method: paper, badge scanner, tablet, QR code, or card scan?

There is no single best method. Most well-run booths use two: one fast path for crowded moments and one richer path for real conversations. The table compares the five common options on the dimensions that matter at a booth.

Badge scanners and trade show lead retrieval

Lead retrieval is the organizer's rental service: a handheld scanner or an app that reads the attendee badge and returns the registration record. It is fast and it captures everyone who lets you scan them, which is also its problem. The record contains whatever the attendee typed at registration, sometimes a personal email, sometimes a company name typed in lower case, rarely anything about why they stopped at your stand. Treat a scan as an identity lookup, not a lead. Pair it with a two-question qualification (interest and requested next step) on the scanner app if it allows custom questions, or on your own tablet form if it does not. Ask the organizer, in writing, what fields the export contains and in which format, before you rent.

QR code lead capture

A QR code turns every printed surface into a form entrance: the back wall, a table tent, a staff lanyard, the slide at the end of a talk. Modern phones scan a QR code from the Camera app with no extra software, which Apple documents in its scan a QR code with your iPhone or iPad page. Practical rules:

• Point the code at a short, dedicated landing page, not your homepage. The visitor should see the form within one second of scanning, with a headline that names the event.
• Print one code per staff member or per surface by adding a query parameter to the URL (for example ?staff=maria or ?src=backwall). You will learn which surfaces and which people generated leads.
• Test the code from three meters away under hall lighting, on both iOS and Android, on the morning of setup.
• Put a fallback short URL under the code for people whose camera app does not cooperate.
• Assume the hall wifi is unreliable; a visitor's own mobile data is usually the more dependable path, which is another point in favor of QR over booth tablets.

Recommended combination

For most B2B exhibitors: a QR code for volume and self-serve moments, plus a staff tablet running the full version of the same form for conversations that deserve notes. Rent the badge scanner only if the show is large enough that scanning speed matters, and even then push scanned leads through the same qualification questions before they reach sales.

Lead qualification rubric (BANT-style, without the pretending)

BANT (budget, authority, need, timeline) was designed for phone qualification by a sales rep with time. At a booth you get two of the four honestly. Here is a rubric that scores what you can actually observe and records the rest as unknown rather than guessed.

Score 0-12. Suggested bands:

• 9-12: Hot. Sales owner assigned before the end of the day, personal email within 24 hours, meeting proposed.
• 5-8: Warm. Interest-specific email within 48 hours, a second touch a week later, revisit after 30 days.
• 0-4: Cold or unknown. Newsletter only if consent was given; otherwise a single thank-you email tied to the requested next step, then nothing.

Two honesty rules. First, budget is not on the rubric because you did not ask and should not pretend a booth chat revealed it. Second, unknown is not zero. If a QR self-serve lead left role blank, mark authority as unknown and let the first email's reply fill it in, rather than sinking a good lead into the cold band.

The rubric is deliberately simple enough to score on a tablet during a lull. If it takes longer than 20 seconds per lead, cut a row.

The booth workflow

A form is only as good as the routine around it. This is a workflow for a two to four person booth; scale the roles up or down.

Two weeks before

• Build the form, both versions, and test on the phones your team actually carries.
• Decide the lead delivery path: where submissions land, who watches that channel, and what "hot" triggers.
• Write the follow-up emails now (see the timeline below). Writing them in the hotel at 11 pm produces worse emails.
• Print QR codes per surface and per person; laminate the table tents.
• Load the CRM with the target account list so company matching works on the spot.

Morning of each day

• Open the form on every device and submit a test lead named TEST to confirm delivery still works.
• Charge everything; bring a power bank per tablet.
• Agree on the day's qualifying question (for example, "What would you want to see in a demo?") so every staff member asks it the same way.

During a conversation

1. Talk first. Do not lead with the tablet.
2. When the visitor shows interest, ask permission: "Can I take your details so I can send you the pricing we discussed?"
3. Fill the full form on the tablet while the visitor is still there, or hand them the QR code if they prefer to type.
4. Confirm the requested next step out loud. This is the moment the lead becomes a task.
5. Add two lines of notes before the next person arrives. Memory of the third conversation fades by the eighth.

End of each day

• Score every lead with the rubric; 15 minutes with the whole team.
• Send the hot leads' first email the same evening, from the person who spoke to them.
• Export the day's CSV as a backup, even if delivery is automated.
• Note which surface or staff code generated the most self-serve submissions and move the underperforming QR code somewhere better tomorrow.

The day after the show

• Dedupe against the CRM, tag every record with the event name and date, and archive the paper backups by scanning them.
• Confirm every "book a demo" lead has a calendar invite sent.
• Hold a 30 minute retrospective while the memory is fresh: which questions worked, which fields stayed blank, what the next show's form should drop.

Mobile form UX for booth visitors

Most self-serve submissions will happen on a phone held in one hand. That changes the layout decisions.

Split the form into two or three steps. On a desktop, a ten-field single page is scannable. On a phone, it is a scroll of anxiety with the keyboard covering half of it. Splitting into logical groups (contact, interest, next step and consent) keeps each screen to two or three inputs and lets the visitor commit progressively. The W3C's multi-page forms guidance recommends dividing long forms into a series of logical steps, indicating progress, and grouping controls by task. The trade-offs, and the cases where a single screen is still better, are covered in multi-step vs single-step forms.

Put the easy tap first. Start with "What are you looking at?" as a set of radio buttons. It costs nothing, it feels like a choice rather than a demand, and it lets you show a tailored second step. Contact details come second, once the visitor has invested a tap.

Use the right input types and autocomplete. An email field with type="email" opens the email keyboard; type="tel" opens the number pad. The autocomplete attribute lets the browser fill name, email, organization and phone in one tap, which is the difference between 20 seconds and 60 at a booth. The web.dev autofill guide covers the correct tokens.

Single column, big targets, visible labels. Nielsen Norman Group's website forms usability recommendations include keeping fields in one column, grouping related fields visually, and cutting anything unnecessary. Placeholders are not labels; in a bright hall with a dimmed screen, a placeholder that disappears on focus becomes a guessing game.

Show progress in text. "Step 2 of 3" is clearer than a thin bar in brand color that nobody notices under fluorescent lights.

Confirm loudly on submit. A full-screen "Thanks, Maria will email you the pricing today" message tells the visitor the form worked and hands the tablet back to staff in a known state. If the form is a popup on a landing page, hide it after submission so the same visitor does not see it twice when they return to show a colleague.

Test with the on-screen keyboard open. The submit button must remain reachable without dismissing the keyboard. This is the most common mobile form failure and it is invisible on a desktop preview.

Consent and privacy at events

Event lead capture is where data protection rules are most often ignored, because everything feels informal. It is not informal. The person handed you their details for a stated purpose, and the rules on what you may do next apply in full.

Separate the requested follow-up from marketing. Sending the pricing someone asked for is fulfilling their request. Adding them to a monthly newsletter is marketing. The first does not require a marketing opt-in; the second usually does, or at least a documented legitimate interests assessment with an easy opt-out. The UK Information Commissioner's Office explains the options in its guide to lawful basis and the balancing test in its legitimate interests guidance.

If you rely on consent, make it real. The ICO's consent guidance describes consent as a freely given, specific, informed and unambiguous indication, which in practice means an unticked checkbox with plain wording ("Email me product updates from Acme, about once a month; unsubscribe any time"), not a pre-ticked box, and not a line buried in the privacy notice. Record when and how it was given; a form submission with a timestamp does that for you, a scanned badge does not.

Collect only what you need. The European Commission's summary of the principles of the GDPR lists data minimization and purpose limitation among the seven core principles. A form that asks for company revenue and a home address "for the database" is a liability, not an asset.

A badge scan is not consent. Attendees agreed to the organizer's terms, which may or may not allow exhibitors to email them. Ask the organizer what the attendee agreed to, and add your own permission step regardless.

Business cards are not a subscription either. A card is an invitation to contact the person about what you discussed. Treat it like a "send me the pricing" request, not like a newsletter signup.

Tell people what happens next, on the form. One line linking to your privacy notice, plus the specific promise ("We will send the pricing and nothing else unless you tick the box"). This is both a legal hygiene step and a conversion aid: people give better data when they know what it is for.

US audiences. The FTC's CAN-SPAM compliance guide does not require prior opt-in for commercial email, but it does require honest headers, identification as an ad where applicable, a physical postal address, and an opt-out that works within ten business days. If your list mixes regions, design for the stricter rule and you will satisfy both.

Raffles and prize draws. The classic fishbowl of business cards for a chance to win a tablet is a consent trap: people entered a draw, they did not ask for your emails. If you run a draw, put a separate, unticked marketing checkbox on the entry form.

None of this is legal advice. Your privacy team or counsel should sign off on the wording; your job as the exhibitor is to make sure the form gives them something clean to sign off on.

Follow-up timeline after the event

The form's fields exist to make this table possible. Every row references a field.

Three rules that separate good event follow-up from spam:

1. The first email must fulfill the request. If someone asked for pricing and receives a "great meeting you" note without pricing, you trained them to ignore you.
2. Reply on the thread, not with a new template. Each subsequent email should look like a continuation of the first conversation.
3. Stop when asked, and stop by default for non-consented contacts once the requested item has been delivered. A short list of people who wanted to hear from you beats a long list of people who tolerate you.

Measuring trade show lead capture

Raw lead count is the metric that makes a show look successful in the recap deck and tells you nothing about whether to go back. Track these instead, per event, in a simple sheet.

Capture funnel

• QR scans (from your link analytics) and form views
• Step completion for the multi-step version (where do people quit?)
• Submissions, split by source: QR self-serve, tablet, badge scan, card scan
• Duplicate rate after CRM matching

Quality

• Share of leads in each rubric band (hot, warm, cold or unknown)
• Share with a marketing consent tick (a leading indicator of how well staff explained the ask)
• Share with the "What are you looking at?" field filled (if this is low, the question or the options are wrong)

Outcomes

• Meeting rate: meetings held ÷ leads who requested a demo or meeting. This is the number that tells you whether your requested next step field is honest.
• Cost per qualified lead: total event cost (booth, travel, staff days, swag, scanner rental) ÷ leads scoring 5 or higher. Compare it against your cost per qualified lead from paid channels, which you can calculate the same way.
• Pipeline created within 90 days, and closed revenue within your usual sales cycle, both tagged to the event.

The popup conversion rate calculator works for the capture funnel arithmetic, and the conversion rate glossary entry covers the definitional traps, such as counting scans instead of form views as the denominator. Do not publish benchmark comparisons you cannot source; your own event-over-event trend is the meaningful comparison.

Common trade show lead capture mistakes

The homepage QR code. Scanning a code and landing on a homepage with a cookie banner and a hero carousel loses the visitor before the form appears. Point the code at the form.

Ten required fields. Every required field that does not change the follow-up is a tax on your best leads, who are also the busiest people in the hall.

Fishbowl consent. Business cards in a bowl, then a newsletter to everyone. It is the fastest way to earn spam complaints from people who liked your booth.

Scanning everyone. A high scan count with no qualification questions produces a list that sales ignores. Scan fewer people and ask two questions.

Notes in memory. Staff who "remember" conversations produce identical follow-up emails. Two lines of notes per lead, typed before the next visitor, beat perfect recall.

Follow-up written after the show. Emails drafted while exhausted, a week later, generic because the sender no longer remembers the detail. Write the templates before you leave.

One form for every visitor. The self-serve QR form and the staff tablet form have different audiences and different tolerances. Build the two versions.

No test submission on the morning of day one. Wifi changes, tokens expire, someone edited the form last night. A test lead named TEST at 8 am costs one minute.

Ignoring "No follow-up." If a visitor picks it and still gets a sequence, the field was theater. Honoring it is what makes people trust the other options.

Paper as the primary. Paper is a fine backup for the hour the network dies. As the primary method, its transcription cost and error rate make it the most expensive option in the table above.

Build the trade show lead capture form with PopupForge

PopupForge is a popup and form builder, and the event use case maps onto it directly: a QR code pointing at a small landing page, where a brand-matched multi-step popup opens immediately and delivers each submission to your team while the show is running.

1. Generate the design from your website. Paste your site URL into the AI popup generator; it returns brand-matched directions (three variants free, without an account, 6-8 in the app). This matters at a booth because the landing page a visitor reaches after scanning your code should look like the company on the banner behind you, not like a generic form vendor.

2. Build the two versions as multi-step popups. The editor supports up to three steps and the field types the template needs: text, email, phone, select, radio, checkbox, textarea, and date. Step one: the interest question as radio buttons. Step two: name, email, company. Step three: requested next step and the unticked marketing consent checkbox. Save a second config with the extra staff fields (role, timeline, notes, staff member) for the tablet; running two popups at once needs a paid plan, since Free includes one modal.

3. Trigger immediately, hide after submit. Set the trigger to "immediately" so the popup opens the moment the landing page loads. Turn on hide-after-submit under frequency so a visitor who returns to the page to show a colleague does not see the form again; the colleague scans their own code.

4. Use URL targeting for per-surface codes. On a paid plan, URL targeting supports query strings, so /event?src=backwall and /event?src=lanyard can show the same or slightly different popups while your analytics tell you which surface produced the submissions. Pro targeting is the feature name.

5. Install with one script tag. Put the landing page on your own domain (any site that lets you add custom HTML or JS works; see the integrations pages for platform steps) and add the embed:

<script src="https://getpopupforge.com/lead-modal.js?appId=YOUR_APP_ID&configId=YOUR_CONFIG_ID" async defer></script>

Config changes publish from PopupForge without redeploying the page, which is what you want when you discover on the morning of day one that the interest options need a fifth choice.

6. Deliver leads where the team is looking. Submissions land in the lead list in the app and can be exported as CSV or emailed. Paid plans add Slack delivery, so a hot lead posts into the booth channel while the visitor is still walking away, and signed HTTPS webhooks, which Zapier or Make can receive to push the record into your CRM with the event tag.

7. Watch step progression during the show. The analytics show views, step progression, closes, and submissions per page. If step two loses most visitors, the contact step is asking too much; drop company to optional between sessions.

Where PopupForge is not the best fit: if your event program depends on organizer badge scanning and you need the scanner export merged in real time, you will still need the rental app for that path and a CSV merge afterwards. It is also not an offline-first tablet app; a staff tablet without connectivity should fall back to paper for that hour. For the self-serve QR path and the staff tablet path with connectivity, it does the job, and the lead capture popup solution page shows the pattern in more detail.

Copyable checklist

Before the show:

• Minimum and full form versions built and tested on iOS and Android
• QR codes per surface and per staff member, tested from three meters
• Landing page loads the form within one second of scanning
• Consent checkbox unticked, wording approved, privacy link present
• Follow-up emails written for each requested next step
• Lead delivery channel decided and monitored by a named person

Each day:

• Test submission on every device before doors open
• Notes typed before the next visitor, not at lunch
• Leads scored with the rubric at close
• Hot leads emailed the same evening by the person who met them

After the show:

• CSV export archived, CRM deduped, event tag applied
• Meeting rate and cost per qualified lead recorded
• Retrospective held; next show's form updated

The form is a small object. The discipline around it is what turns a booth into a pipeline. Start from the minimum template, ask the interest question first, honor the requested next step, and send the first email before you leave the hall.