Describe the posts you need to fill and the qualifications each one requires. Makeform turns your brief into an online security guard application form with license details, relevant experience, availability, references, and focused screening questions.
Route applications to Slack, Google Sheets, and Zapier.
Sample prompts for the builder
Choose a complete prompt, adapt it to your hiring workflow, or send it to the Makeform builder. The structure shown is a planning example, not a live generated result.
Audience
Applicants for commercial property and access-control posts
Format
Mobile application with license, experience, and shift questions
Prompt size
372 chars
Example form structure
Mobile application with license, experience, and shift questions
Contact details and preferred work area
Guard license type and expiration date
Relevant security and customer-service experience
Which shifts can you regularly work?
Resume and training documents
Suggested routing tags
License review
Interview review
Availability match
Collect the license type, issuing jurisdiction, identification number, and expiration date separately. Recruiters can then review role requirements without interpreting one crowded answer.
Step 1
Apply
candidate submits qualifications, history, and availability
Step 2
Screen
recruiter checks required fields and assignment fit
Step 3
Verify
designated staff review credentials and references
Step 4
Interview
qualified candidates move into the hiring workflow
Built for guard recruiting
A generic application can miss the details that decide whether a guard can cover a post. Structured questions make credentials, shifts, travel, and experience comparable.
Separate license type, jurisdiction, number, expiration, and documents so missing information is visible before designated review.
Ask about access control, patrol, incident writing, de-escalation, or driving only where those skills matter.
Collect shifts, event dates, start date, location, and travel range in structured inputs.
Role-specific versions
Publish focused versions when duties, credentials, locations, or schedules differ, keeping irrelevant questions hidden.
Focus on access control, visitor service, reporting, location, and shift coverage.
Reveal employer-defined permit and training questions only when relevant.
Add driving details, travel radius, overnight routes, reporting, and transportation.
Collect event dates, evening availability, crowd experience, duties, and locations.
Build the application
Describe the assignment and screening criteria, generate a form, and review each question before sharing it.
Name the location, designation, duties, credentials, shifts, travel, and reviewer.
Show permit, driving, event-date, or document questions only for relevant roles.
Notify recruiters, label responses by role and availability, and limit access to hiring staff.
Use defined review statuses and record follow-up without making candidates resubmit details.
Choose the intake method
Each can start hiring; they differ in how much structured information is ready before screening.
Field guide
Organize the form around the decisions your hiring team actually makes. Six clear sections give candidates context and help reviewers distinguish missing information from a mismatch with the post.
Candidate profile
Collect identity, contact, work area, role, and start date. Show the assignment's location, schedule, and duties first.
Licenses and training
Use separate fields and your hiring team's terminology. A designated reviewer can then check submitted information.
Experience and skills
Ask candidates to describe work resembling the post, not only years of experience.
Schedule and mobility
Separate recurring shifts from event dates, and capture mobility for posts across several sites.
History and references
Use repeatable history entries and collect references in consistent fields.
Review and acknowledgment
Let applicants review answers, add context, and confirm submission. Explain next steps without promising an outcome.
Related tools
Connect intake with references, credential review, scheduling, availability, and general applications.
FAQ
Practical answers for security company recruiters building a consistent, role-specific candidate intake process.
It is a job application combining candidate details with structured questions about guard credentials, experience, work history, availability, travel, references, and preferred roles.
Include contact and eligibility details, role choice, guard credentials, training, experience, employment history, resume, availability, travel, and references. Branch for driving, events, or role-specific permits.
Separate credential type, jurisdiction, number, and expiration. Use your team's terminology and treat uploads as information awaiting designated review.
Yes. Begin with the role and branch. Separate versions may be clearer when duties differ, while core candidate sections remain consistent.
Offer weekday, day, evening, overnight, weekend, and holiday choices. Ask hours, start date, location, travel radius, event dates, and optional constraints.
Yes, when tied to duties such as documenting observations, resolving access mismatches, calming visitors, or escalating incidents. Define review criteria first.
Yes. Makeform supports unlimited free forms and responses, so you can generate, edit, publish, and collect applications without a form or response cap. The paid tier removes the Makeform badge.
Limit access, define statuses and owners, separate applicant details from verification decisions, preserve follow-up, and provide a recruiting contact.
Turn every open post into a focused application.
