Purpose and context
Explain the invitation before asking.
State the purpose, audience, voluntary nature, and handling before the choices.
- Organization and invitation stage.
- Reviewed purpose and privacy text.
- Contact route for questions.
Describe your applicant or employee invitation. Makeform creates a voluntary form with reviewed introductory text, veteran-status choices, a prefer-not-to-answer option, and restricted HR routing.
Route authorized HR notifications to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a prompt, tailor the wording, and review the form against current instructions before publishing.
Audience
Job applicants completing a voluntary invitation
Format
Short standalone form with neutral choices
Prompt size
260 chars
Example form structure
Short standalone form with neutral choices
Applicant name or applicant ID
Job requisition ID
Veteran status selection
I prefer not to answer
Invitation date
Suggested routing tags
Applicant invitation
Employee update
Restricted HR review
Keep veteran-status responses out of recruiter review views and include a clear option to decline self-identification.
Step 1
Invite
share reviewed purpose and voluntary notice
Step 2
Respond
choose a status or prefer not to answer
Step 3
Restrict
route responses to authorized HR staff
Step 4
Review
track invitation stage and notice version
A careful HR workflow
Explain the invitation, offer a genuine choice, and control who can see the answer.
Place current, approved purpose and privacy wording before the response choices.
Include prefer not to answer; avoid unnecessary service dates, discharge details, or documents.
Route status answers to designated HR staff, not hiring managers or general recruiter inboxes.
Match the invitation stage
Start with the closest stage, then insert wording your organization has reviewed.
Use candidate and requisition IDs while keeping responses outside recruiter evaluation views.
Match the candidate record without mixing status data into offer or selection questions.
Let employees update a response without reopening unrelated personnel fields.
Branch by respondent type and route to the authorized HR owner.
Build the invitation
Generate the structure, check each choice, and test every destination before inviting responses.
Specify applicants, post-offer candidates, or employees and the identifiers HR needs.
Insert approved language, confirm category labels, and clearly offer prefer not to answer.
Choose the restricted HR destination and omit status values from broad alerts.
Test every path and notification, then record the notice version displayed.
Dedicated form vs general application
A dedicated form makes choices, version, and routing easier to inspect.
Field guide
Use current wording reviewed for your organization, because definitions and notices can change.
Purpose and context
State the purpose, audience, voluntary nature, and handling before the choices.
Record matching
Use an identifier and needed context without creating a second application or requesting military documents.
Response options
Present understandable choices and required definitions without improvising or combining labels.
Data separation
Announce new submissions without copying status into channels that do not need it.
Conditional flow
Reveal matching identifiers and context after asking whether the person is an applicant or employee.
Version and review
Store the notice version and date, then retest after wording or routing changes.
Related tools
Use separate forms for applications, onboarding, employee information, and HR review so voluntary veteran-status data does not have to carry unrelated tasks.
Collect qualifications and role-specific application details in a separate candidate workflow.
Open toolGive interviewers a structured place to record job-related assessment criteria.
Open toolGather operational onboarding details without mixing them into the status invitation.
Open toolOrganize the broader new-hire packet around a dedicated paperwork intake.
Open toolLet employees update ordinary personnel details through a distinct request.
Open toolStructure authorized HR fact collection when a separate workplace review is required.
Open toolFAQ
Practical answers for HR teams building a voluntary applicant or employee invitation.
It lets applicants or employees voluntarily select an approved veteran-status choice or decline to answer. It can also record the invitation stage and notice version while routing responses to authorized HR staff. Use your organization's current reviewed wording and process.
A separate workflow makes access boundaries clearer because status need not appear beside qualifications. If embedded in an application system, configure views, alerts, exports, and permissions so hiring decision-makers do not receive the answer outside your reviewed process.
Use current categories and definitions approved for that invitation stage, plus an appropriate alternative and prefer not to answer. Check archived labels before reuse, and avoid unnecessary service-detail questions.
Present participation as voluntary and provide an obvious prefer-not-to-answer choice. Do not force a veteran category. Test that declining follows the same submission path, and use reviewed notice text to explain how nonresponse is handled.
Use a dedicated HR destination, keep status out of broad alerts, and inspect connected sheets and automations for unintended recipients. A neutral alert can announce a submission. Test configured access with representative roles before launch.
Yes. Conditional logic can show candidate and requisition fields or employee and department fields. Keep notice wording accurate for each branch. Separate links may simplify ownership or reporting; the builder supports either structure.
Yes. Makeform provides unlimited free forms and responses for generating, editing, publishing, and testing. The paid tier removes the Makeform badge. Review wording, choices, permissions, and integrations before live use.
Test every choice and branch. Confirm required fields do not force disclosure; inspect emails, sheets, and automations; verify intended recipients; check mobile readability and accessibility; and confirm notice version. Retest after wording, destination, or permission changes.
Build a clearer voluntary invitation.