Describe your show, casting, or fashion event. Makeform creates one registration form with tailored paths for designers, models, attendees, vendors, and press.
Route fashion registrations to email, Google Sheets, Slack, and connected workflows.
Sample prompts for the builder
Choose a prompt, adapt it, or send it to the builder. The fields are an example structure, not a live AI result.
Audience
Independent labels applying for runway slots
Format
Application with collection profile and lookbook upload
Prompt size
325 chars
Example form structure
Application with collection profile and lookbook upload
Designer and label details
Collection category and number of looks
Lookbook and line sheet
Do you need event-provided models?
Production and backstage requirements
Suggested routing tags
Designer applications
Model casting
Guest registrations
Ask for a role first. Conditional sections keep attendee signup short while collecting portfolios or measurements where needed.
Step 1
Choose role
designer, model, guest, vendor, or press
Step 2
Collect details
show only the fields that role needs
Step 3
Review
route applications and registrations by team
Step 4
Coordinate
confirm schedules, access, and next steps
One organized intake
Generic signup leaves staff chasing measurements, lookbooks, seating requests, and load-in needs. Role-based registration collects the right details at the start.
A role selector reveals designer, model, attendee, vendor, or media sections without irrelevant fields.
Required dates, sizing, uploads, technical needs, and contacts create consistent review records.
Role and status fields separate casting, guest services, vendor operations, and press review.
Built for fashion teams
Choose a focused form or combine audiences with conditional sections, then edit dates and options.
Collect collection concepts, look counts, sizes, lookbooks, dates, and backstage requirements.
Gather representation, measurements, images, availability, and accommodation requests.
Offer session choices and collect accessibility and reception needs.
Separate booth logistics from credential requests and collect supporting details.
Registration workflow
Turn the event brief into a form, test every path, and share one signup destination.
Name the format, dates, venue, roles, deadlines, and whether submissions are applications or confirmed attendance.
Put role first, check each conditional path, add real sessions or categories, and require only necessary fields.
Submit a test for each enabled role. Check uploads, dates, confirmation copy, and the recipient view.
Share or embed the form, then use role and status for casting, guest, vendor, and credential lists.
Choosing an intake method
A fashion registration form makes required details clear before submission.
Field guide
Collect what the team will use, explain requested uploads, and keep details within the relevant role path.
Identity and role
Name, contact, organization, and role create the core record. Ask role early because it controls later questions and review routing.
Creative profile
Request consistent portfolio links, concise experience, collection context, and labeled images so reviewers can compare submissions efficiently.
Sizing and availability
Use labeled measurement and size fields that wardrobe needs. Ask separately about fitting, rehearsal, and show availability.
Guest choices
Identify session, ticket type, and seats requested. Ask about accessibility and reception needs in plain language.
Operations
Structured options make booth size, power, backstage, interview, and equipment needs visible before plans are locked.
Information and acknowledgment
Place deadlines, venue rules, photography notices, cancellation details, and upload guidance beside relevant fields. Record acknowledgment of stated terms.
Related tools
Add tools for event signup, vendor applications, documents, and post-show feedback.
FAQ
Practical answers for show producers, casting teams, guest services, and event operations.
It is an online intake for a show, casting, showroom, or market. It can collect designer applications, model profiles, guest reservations, vendor logistics, and media requests. Role-based sections support several groups without showing everyone every question.
Collect designer and label names, contact details, portfolio, collection title, category, size range, look count, and availability. Add lookbook or line-sheet uploads plus questions about models, racks, dressing space, music, or setup.
Ask for contact and representation details, relevant measurements and sizes, portfolio links, requested images, experience, and availability for casting, fitting, rehearsal, and show dates. Offer an accommodation field and explain how details will be used.
Yes. Start with role selection and show a matching conditional section. Keep shared identity questions first, then tailor fields for collections, sizing, tickets, booth logistics, or credentials. Test each branch and its confirmation before publishing.
List real sessions and collect requested seats. If the form does not confirm live availability, say that submission is a request. Offer a waitlist option and review responses in the system used for capacity decisions.
Yes. Add labeled upload fields to designer or model paths. State expected file type, orientation, naming, and content. Offer a portfolio URL when appropriate and request only assets needed for the current review.
Yes. Makeform provides unlimited free forms and responses. You can generate, edit, publish, and collect registrations without a response cap. The paid tier removes the Makeform badge. Replace sample event details and test each path before sharing.
Route by registrant role, then add statuses such as new, needs details, shortlisted, confirmed, waitlisted, or declined. Connect responses to your planning workspace and limit access when records contain contact details, measurements, schedules, or documents.
Bring every fashion registration into one clear workflow.
