Move an applicant from interest to personnel
- 1
Create an Application Hub and set its type, dates, branding, and reviewer access.
- 2
Build pages, sections, fields, follow-up questions, and stages.
- 3
Publish the Hub and share its public link.
- 4
Triage submissions, assign reviewers, and resolve Smart Scan flags.
- 5
Schedule interviews through availability pools, score them, and request references.
- 6
Record the decision: approve, deny, or conditionally approve.
- 7
Convert the approved applicant into personnel, then assign an Onboarding program.
Choose a step-by-step task guide
Each guide includes prerequisites, exact actions, verification, and troubleshooting—not just a feature summary.
Module capabilities
- Branded public Application Hubs across 17 hub types
- Form builder with about 40 field types, drag-to-reorder, show/hide follow-ups, email verification, and field sensitivity levels
- Save-and-resume and document uploads for applicants
- Submissions with filters, tags, priority, stages, and internal or applicant-visible notes
- Reviewer assignments with deadlines, a To-review queue, recommendations, and majority votes
- Interview availability pools applicants book themselves, weighted scorecards, and no-show tracking
- Reference questionnaires and single-use document replacement links
- Smart Scan: rules-based (not AI) completeness and document checks that raise flags for reviewers
- Applicant email with 14 template types, variables, attachments, and a delivery log
- Conversion that creates the account and assigns role, station, and supervisor
Before your department relies on it
- 1
Define stages and decision authority before building forms.
- 2
Mark sensitive fields and limit who can view them.
- 3
Set reviewer counts and deadlines.
- 4
Test the public form, email verification, save-and-resume, and phone layout.
- 5
Plan interview and reference follow-up; reminders are not sent automatically.
- 6
Publish an Onboarding program before your first conversion.
Portal destinations
These destinations appear only when the module is enabled and your roles grant the required access.
| Area | Portal path |
|---|---|
| Submissions | /officer-hub/applications/submissions |
| Submission detail | /officer-hub/applications/submissions/:id |
| To review | /officer-hub/applications/review-queue |
| Interviews | /officer-hub/applications/interviews |
| Interview pools | /officer-hub/applications/interviews/pools |
| Hubs | /officer-hub/applications/hubs |
| Hub builder | /officer-hub/applications/hubs/:id |
| Templates | /officer-hub/applications/templates |
| Reports | /officer-hub/applications/reports |
| Settings | /officer-hub/applications/settings |
| Public application | /apply/:org/:hub |
| Applicant portal | /applicant |
Associated modules
Required modules must be enabled first. Related modules exchange data or extend the workflow when both are available.
Dependencies
RequiredCoreAnswers before you get stuck
Is this the old Applications Flow?
Yes. Applications Flow is now called Recruiting.
Does Smart Scan use AI or make decisions?
No. Smart Scan is rules-based. It raises flags for reviewers, who decide.
Do applicants need a portal account?
No. They use the public form and an email-code applicant portal.