Describe your workplace or campus process. Makeform creates an ID card request form for identity details, new or replacement reasons, photos, and routing.
Send card requests to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a prompt, adjust it, or send it to the builder. The structure is an example, not a live AI result.
Audience
HR teams issuing cards during onboarding
Format
New-card request with manager routing
Prompt size
313 chars
Example form structure
New-card request with manager routing
Employee name and printed name
Employee number and department
Office and start date
Requested access level
Upload a card photo
Suggested routing tags
New card
Replacement
Ready for pickup
Ask for the name exactly as it should print on the card, separately from the requester's directory or student-record name.
Step 1
Identify
employee or student record details
Step 2
Explain
new card, replacement, or update
Step 3
Review
photo, printed name, and routing checked
Step 4
Fulfill
print queue and pickup message organized
A cleaner card queue
A structured request keeps identity details, photo, replacement reason, and routing in one submission.
Collect the record name and exact printed name as distinct fields.
Show different follow-ups for new, missing, damaged, and changed cards.
Use department, campus, location, or requester type to sort queues.
One starting point
Use one flow or separate versions when fields, fulfillment, and reviewers differ.
Capture employee number, department, manager, start date, location, printed name, and photo before the first day.
Ask for student number, program, campus, expected graduation term, photo, and preferred collection point.
Record when and where the card was last seen and route the report for the organization's separate deactivation process.
Collect damage evidence or changed print details so the reviewer can see what must differ on the replacement.
Build the workflow
Generate the intake, edit its questions, and connect reviewer notifications.
Name the requester groups, identity fields, replacement reasons, photo rules, locations, and fulfillment options that apply.
Make record numbers required, add your real department or campus choices, and show loss, damage, or update questions only when relevant.
Notify the appropriate HR, registrar, security, or card-office inbox and give the requester a clear confirmation of what happens next.
Use consistent reason, location, and requester-type answers to sort incoming work and prepare printing or pickup outside the form.
Request channels compared
Card intake should preserve identity data, print details, files, and request reasons.
Field guide
Match the person to a record, understand the request, review the image, and plan fulfillment.
Requester and cardholder
Separate requester contacts from cardholder identity when someone submits for another person.
Request type
Start with a reason choice and show only its relevant follow-ups.
Printed details
Ask separately for the printed name and any approved role, program, or identifier.
Card photo
Place framing, background, format, and size guidance beside the upload.
Review and routing
Use fixed choices for campus, department, card type, and reason to support sorting.
Fulfillment
Collect contact and fulfillment preferences, then confirm receipt without promising timing.
Related tools
Build nearby identity, onboarding, access, registration, and reporting workflows.
Collect access-area and sponsor details when physical access is reviewed separately from card printing.
Open toolGather core employee record details that can feed onboarding and internal administration.
Open toolOrganize the tasks around a new employee, including the request for a workplace card.
Open toolCollect enrollment details before a student reaches the campus card workflow.
Open toolRecord missing-property details when a broader lost-and-found report is also appropriate.
Open toolBring related new-hire information into a structured paperwork intake.
Open toolFAQ
Practical answers for HR, registrar, security, and campus card teams setting up request intake.
It is structured intake for a first card, replacement, or printed-information update. Identity details, reason, photo, location, and contact preferences reach the issuing team in one submission.
Include requester contact, cardholder name and record number, department or program, location, request type, printed name, photo, and fulfillment preference. Add conditional questions for missing, damaged, or changed cards.
Yes. Identify the group first, then show employee fields such as manager and start date or student fields such as program and campus. Separate forms may suit separately owned queues.
Use a fixed reason list, then ask the relevant follow-up: last-known location, damage image, or old and new print details.
Yes. Add a file upload with the issuing office's framing, background, format, and size guidance. A reviewer can request another image when needed.
No. The form collects and routes intake; the responsible office uses its separate card system. Explain urgent reporting and deactivation steps for missing cards.
Yes. Makeform is unlimited free for generating, editing, and publishing forms. The paid tier removes the Makeform badge, so you can build and use the request flow without a submission or generation limit.
Require record number, reason, printed name, and needed photos. Use fixed location choices, photo guidance, conditional follow-ups, and a confirmation with the next step.
Replace scattered card-request emails.
