Describe your conference and production needs. Makeform creates a speaker registration form for profiles, sessions, availability, accessibility, and technical requirements.
Route speaker details to Google Sheets, Slack, and Zapier.
Sample prompts for your event
Choose a prompt, adapt it, or send it to the Makeform builder.
Audience
Confirmed speakers at a multi-track conference
Format
Registration form with profile, session, and production sections
Prompt size
323 chars
Example form structure
Registration form with profile, session, and production sections
Speaker profile and public bio
Upload a high-resolution headshot
Session title, abstract, and outcomes
Which equipment does your session require?
When are you available to present?
Suggested routing tags
New submissions
Program review
Production follow-up
Ask speakers to separate the public session description from internal production notes so your website copy stays clean.
Step 1
Register
profile, bio, headshot, and contact details
Step 2
Program
topic, abstract, outcomes, and availability
Step 3
Produce
AV, accessibility, travel, and stage needs
Step 4
Confirm
reviewed details routed to the event team
A cleaner speaker intake
A structured speaker registration form gives programming, marketing, travel, and production teams one usable submission instead of four different follow-up conversations.
Set bio length guidance, require a headshot, and ask how names should appear and be pronounced. Speakers supply the public-facing details once, in a format the marketing team can reuse.
Collect titles, abstracts, formats, tracks, audience levels, and learning outcomes with the same fields for every proposal. Reviewers can compare like with like.
Ask about microphones, adapters, demonstrations, seating, connectivity, accessibility, and rehearsal timing before the run of show is locked.
Fits the program format
Start with the event format closest to yours, then change the fields, instructions, and follow-up routing in the builder.
Track selection, session length, schedule conflicts, co-speakers, and room-specific technical requirements.
Panel roles, expertise, discussion boundaries, moderator prompts, rehearsal slots, and pronunciation notes.
Time zones, live versus prerecorded delivery, recording schedules, remote equipment, slide sharing, and backup contacts.
Executive contacts, public biographies, travel logistics, stage setup, media preferences, and production handoffs.
Speaker onboarding workflow
Generate the intake, tune it, share one link, and route complete records to your event teams.
Specify an open proposal or confirmed-speaker workflow, plus dates, tracks, formats, and deadlines.
Require essentials, guide bio length, and show co-speaker, virtual, or moderator questions when relevant.
Send the form with acceptance. Clear sections group profile, program, travel, and production details.
Use submissions for program review, speaker pages, travel follow-up, and production planning.
Form vs document vs email
A speaker packet communicates expectations, but it does not turn replies into a consistent roster. A generated form captures the same categories for every presenter.
Field guide
Separate public profiles, program details, and private logistics so speakers answer once.
Identity and contact
Separate the preferred public name from operational contact details and event-day contacts.
Public profile
Request a concise bio, headshot, and selected links. Label answers that may be published.
Session proposal
Separate the public abstract from reviewer context, then use structured program choices.
Co-presenters and roles
Collect each contributor's role and contact. Show co-presenter fields only when needed.
Technical and stage needs
Ask what will be demonstrated, which connections are required, and how speakers will use the stage.
Schedule and accommodations
Capture availability and private logistics separately from public profile copy.
Related tools
Connect speaker recruitment, attendee registration, planning, and post-event feedback with focused forms for each audience.
Collect session proposals and presenter backgrounds during an open call for speakers.
Open toolLet staff, partners, or attendees recommend experts for the program team to consider.
Open toolRegister attendees with ticket, track, contact, and event preference questions.
Open toolAsk attendees about goals, preferences, and logistics before the event begins.
Open toolMeasure reactions to sessions, speakers, logistics, and the overall event experience.
Open toolCollect the scope, audience, venue, schedule, and production inputs for an event brief.
Open toolFAQ
Practical answers for conference organizers, program leads, and event production teams.
It is an online intake for presenters. It gathers contacts, public profiles, sessions, availability, co-presenters, travel, accessibility, files, and technical requirements in one submission.
Include preferred name, organization, contact, bio, headshot, and pronunciation. Add the session title, abstract, outcomes, track, format, level, availability, co-speakers, logistics, AV, rehearsal, and uploads.
A call evaluates proposals before acceptance, emphasizing topic fit and outcomes. Registration follows acceptance and gathers final profiles, schedules, travel, files, and production details.
Yes. Combine long-answer fields with uploads for headshots, slides, handouts, or video. Put format, resolution, naming, and deadline instructions beside each upload.
Yes. Conditional paths can show moderator and panelist questions for panels, or time-zone, recording, equipment, screen-sharing, and backup questions for virtual talks.
Offer choices for microphones, displays, adapters, audio, internet, lighting, seating, and stage layout, plus notes for demonstrations. Identify essential requirements and collect a technical contact.
Yes. Makeform provides unlimited free forms and responses, so you can generate, edit, publish, and collect speaker registrations without a response cap. The paid tier is for removing the Makeform badge.
Label public profile, session, and organizer-only sections. Explain what may be published, then route travel, accessibility, contact, and technical details to responsible teams.
Bring every speaker detail into one workflow.
