Describe your career fair and its audiences. Makeform turns the brief into a job fair registration form for employers, candidates, or both, with tailored questions and confirmations.
Send registrations to Google Sheets, Slack, and Zapier.
Sample prompts for the builder
Choose a prompt, tailor its details, or send it to the Makeform builder.
Audience
Companies reserving recruiting space
Format
Company application with booth requirements
Prompt size
322 chars
Example form structure
Company application with booth requirements
Company and recruiter contact
Roles and experience levels recruiting
Booth representatives
Booth and accessibility requirements
Company logo
Suggested routing tags
Employers
Job seekers
Needs follow-up
Start with a registrant-type question. Conditional paths keep candidates from seeing booth questions and employers from seeing resume questions.
Step 1
Register
employer or attendee chooses a path
Step 2
Route
details go to the right organizer
Step 3
Prepare
booths, sessions, and support are planned
Step 4
Check in
the team works from one registration list
Why one structured form
Headcount cannot reveal booth power needs, candidate interests, or accessible check-in requests. Capture operational details before event day.
Route employers to booth fields and candidates to career interests, sessions, and resume upload.
Dropdowns produce clean counts for industries, openings, time slots, table needs, and support requests.
Send employers setup instructions and candidates check-in details in distinct confirmations.
Fits the event format
Choose the closest format, then edit its questions, instructions, and routing.
Collect majors, graduation dates, openings, recruiter rosters, and booth requirements.
Offer language preferences, support requests, walk-in details, and experience choices.
Match candidate specialties with employer job families, locations, and interview times.
Capture time zones, sessions, employer interests, caption requests, and access email.
Registration workflow
Describe your audiences, review the generated structure, publish, and route responses.
Name the format, venue, audiences, booth setup, time slots, and operational needs.
Edit choices, require operational answers, add conditions, and remove unnecessary questions.
Send the public link or embed the form with clear deadlines and contacts.
Separate audiences, export lists, address support requests, and reconcile check-ins.
Choose a collection method
Email and generic sign-up sheets leave organizers chasing booth needs, interests, files, and schedules.
Field guide
These six sections turn company and candidate responses into an event plan.
Registrant identity
Start with registrant type, contact details, and organization or school so each record routes correctly.
Employer profile
Collect employer details once for the public list and internal planning.
Candidate goals
Use broad choices to understand candidate demand and recommend sessions.
Booth logistics
Structured setup answers provide counts before tables and materials are assigned.
Access needs
Invite accessibility, language, dietary, or other support requests for organizer follow-up.
Schedule and confirmation
When capacity matters, collect a time choice and show a role-specific confirmation.
Related tools
Connect registration, employer coordination, applications, sponsorship, and networking.
Create a general-purpose event sign-up flow with attendance details and confirmations.
Open toolCollect organization profiles, space requirements, files, and review details from event vendors.
Open toolBuild the next-step application employers can share with interested candidates.
Open toolGather sponsor contacts, package interests, assets, and fulfillment needs for the fair.
Open toolRegister guests for mixers, recruiter receptions, or post-fair networking sessions.
Open toolHandle multi-session registration when a career fair is part of a larger conference.
Open toolFAQ
Practical answers for career-services teams, workforce organizations, associations, and recruiting event planners.
It registers companies, recruiters, job seekers, or other participants and collects details for communication, booth setup, scheduling, accessibility follow-up, and check-in.
They can. Conditional logic shows employers hiring and booth questions while attendees see career interests, time choices, and resume upload. Use separate forms when different teams own each audience.
Ask for company and recruiter contacts, industry, roles and experience levels being recruited, hiring locations, representative names, a logo, and booth requirements such as power or accessible placement. Include deadlines and organizer contact details beside questions that may require coordination.
Usually name and contact details, career stage, target roles or industries, work-location preferences, attendance slot, and any accessibility request. A resume can be optional when employers will receive or review it; avoid collecting information the event team will not use.
Yes. Add file-upload fields to the relevant conditional path. Label accepted file types and explain how organizers plan to use the upload, then limit each request to files that are genuinely needed for the event workflow.
Yes. Use registrant type as a routing tag, then filter or export responses. Group records by arrival slot, industry, job interest, or follow-up status.
Yes. Makeform offers unlimited free forms and responses, so you can generate, edit, publish, and collect registrations without a response cap. The paid tier removes the Makeform badge.
Provide a clear optional field for the registrant to describe what they need and name a contact for follow-up. Route those responses to the appropriate organizer, restrict access to people handling arrangements, and confirm details directly rather than assuming what support is required.
Turn sign-ups into an event plan.
