Recruitment

End-user documentation

Recruitment

Applicant tracking and public job portal for job postings, applicants, statuses, pipeline, interviews, offers, resumes, consent, and hiring reports.

Purpose and What Problem This Solves

The Recruitment module brings job postings, applications, screening, interviews, offers, comments, resume files, and applicant consent into one hiring workflow. It helps hiring teams move faster while keeping applicant data and decisions traceable.

Who normally uses this module

What You Can Do Here

• Create job postings, categories, public job portal content, and application forms.
• Receive applications with resume files and Data Privacy consent.
• Move applicants through screening, interview, offer, hire, reject, or hold stages.
• Record interviewer notes, comments, statuses, labels, and remarks.
• Review hiring pipeline performance and open-position activity.

Core Concepts and Terms

Learn these words first. Most user mistakes happen when a beginner opens a form without knowing what the record represents.

Beginner Quick Start

Use this first-run path in a training database or with a supervised account before handling live records.

1. Create job categories, statuses, labels, and public portal settings.
2. Publish one job posting with clear requirements and application instructions.
3. Submit a test application through the public portal and confirm consent capture.
4. Move the applicant through screening, interview, and offer stages.
5. Review reports and tune the hiring workflow before wider use.

Standard Operating Procedures

These SOPs describe the routine operating pattern. Your company policy may add approvals, attachments, or segregation-of-duties controls.

Publish a job opening

1. Confirm headcount approval, role title, location, employment type, salary guidance if allowed, and hiring manager.
2. Write responsibilities and requirements in plain language.
3. Publish the job and verify it appears correctly in the public portal.
4. Share the posting through approved channels and monitor incoming applications.

Screen applicants

1. Open each new application and review resume, answers, consent, and required documents.
2. Apply labels or status based on documented criteria.
3. Move qualified applicants to interview and record rejection reasons for declined applicants.
4. Avoid storing sensitive notes that are not job-related.

Manage interviews and offers

1. Schedule interviews and brief interviewers on evaluation criteria.
2. Collect notes and outcomes after each interview.
3. Prepare offer only after required approvals.
4. Record accepted, declined, or withdrawn outcomes and close the pipeline cleanly.

Industry Notes and Good Practice

• Hiring data is sensitive. Keep notes factual, role-related, and appropriate for audit.
• A good job post explains outcomes, requirements, and process clearly enough for applicants to self-assess.
• Pipeline stages should represent real decisions. Moving candidates casually makes hiring reports unreliable.
• Consent capture matters for public applications. Keep privacy language current and visible.

Controls, Data Quality, and Review Checklist

Use this checklist during onboarding, monthly review, and process audits.

• Every job posting has owner, status, category, requirements, and application instructions.
• Applicant records include consent evidence before processing.
• Rejected or withdrawn candidates have appropriate reason codes or notes.
• Interview and offer stages are updated promptly so reports match reality.

Related ERPat areas

FAQ and Troubleshooting

Why is a job not visible publicly?

Check posting status, portal configuration, publish dates, category, and module enablement.

Can applicants apply without logging in?

The public portal supports applicant intake according to configured flow and consent requirements.

Should interview notes be private?

They should be permission-controlled and job-related. Avoid personal or irrelevant comments.

What should beginners monitor daily?

New applicants, interview schedules, stalled pipeline stages, and offer approvals.

ERPat Recruitment user guide. This static HTML page is documentation-only and does not change module routing, permissions, or runtime behavior.