Applicant tracking

Applicant tracking system for Pakistan’s growing teams

Keep each job applicant connected to the role, CV, interview and hiring decision. OPleo gives Pakistan’s SMEs a recruitment pipeline inside the same workspace as their people operations.

An applicant tracking system should answer three practical questions: who applied, what happens next, and who owns the decision? OPleo tracks those handoffs through applied, screening, interview, offer, hired and rejected stages, with public application pages and private hiring records.

From an open job to a reviewed hiring decision

A candidate tracker is only useful if incoming applications and interview decisions reach the same record. Start with a job opening rather than a separate list of CVs: each application, interview and offer can be related to that role.

For example, a software house hiring an engineer and an operations coordinator needs to distinguish which role each applicant wants, which interview is scheduled and which offer is still awaiting a response. This is a workflow example, not a customer outcome.

Create and share the opening

Set the title, department, location, employment type, hiring manager, openings and target hire date. Open roles have a public careers URL; draft, on-hold and closed roles have distinct statuses.

Receive the candidate’s application

An applicant submits name, email, optional phone and cover note, plus a validated CV. The public form does not require an OPleo account, and the application becomes a candidate record for that job.

Screen and record context

Review the CV alongside candidate source, experience and notes. Move the applicant to Screening when the hiring team is ready, rather than treating a score as a hiring decision.

Interview, offer or close

Schedule an interview, record feedback and recommendation, then prepare an offer or record rejection. Keep the decision in the candidate stage so the next reviewer can understand the current position.

Applicant status tracking that keeps the next action visible

The candidate pipeline displays Applied, Screening, Interview, Offer and Hired columns. A candidate’s stage selector also supports Rejected. Stage labels describe the current record; they do not replace interviews, references or the hiring manager’s review.

Supported OPleo candidate stages and a suggested review routine.
StageHiring team’s actionWhat to check
AppliedReview the role-linked applicationCV, contact details and job fit
ScreeningRecord screening notesExperience and requirements that need verification
InterviewSchedule and collect feedbackInterviewer, format, date and recommendation
OfferPrepare and review the offerRole, annual amount, currency and start date
Hired / RejectedRecord the outcomeCandidate stage and outstanding follow-up

What the candidate portal actually includes

Candidates use the public application page and, when invited, token-protected response pages for interviews or offers. Interview and offer emails use the organisation’s configured recruitment sender and SMTP settings. The response links expire and expose the specific action rather than private workspace records.

This is not a permanent candidate account with a dashboard of every application. An interview response can record confirmation or a decline; an accepted offer updates the candidate stage to Hired. Do not assume that accepting an offer automatically creates an employee, issues a contract or completes onboarding.

Before choosing recruitment software for your SME, test the application file types, your hiring stages and your organisation’s email configuration. Keep real CVs and candidate details out of public product demonstrations.

Start with one role and a complete hiring loop

Use a representative vacancy to validate the ATS before moving your current hiring list. Agree the job owner, stage meanings and interview reviewer. Test one application, a CV review, an interview record and an offer response with fictional data.

Then decide how existing applicants will be entered and how duplicate or stale records will be handled. A public job page supplies an intake path; it does not establish job-board distribution, automatic CV parsing, background checks or interview-video hosting.

Bring to the demo

A redacted role description, the interview stages your team uses, who sends invitations and who approves offers.

Define the onboarding handoff

After hiring, confirm the employee’s designation, department, supervisor, joining date and portal email in employee management. Validate the handoff instead of assuming an automatic candidate-to-employee conversion.

Inside the product

See the actual OPleo product screens

Captured from OPleo’s product components with fictional demo records. These are product views, not customer results; each capture shows a separate workflow state.

01 — Create the job

OPleo job opening form with title, department, location and employment type
The real job form records the role, hiring manager, openings and target date. Fictional demo inputs; no job was published during capture.

02 — Receive an application

OPleo public application form with contact details, cover note and CV upload
Candidates apply through an open role’s public page without a workspace account. The form accepts PDF, DOC or DOCX CVs up to 5 MB.

03 — Find the applicant in the pipeline

OPleo recruitment pipeline with a fictional applicant in the Applied stage
Role-linked candidates appear in the hiring pipeline. Each card has a CV link and a stage selector.

04 — Track a stage change

OPleo pipeline showing a fictional applicant in the Screening stage
The Screening state shown with demo data. Stage changes are made by the hiring team; OPleo does not make the hiring decision.

05 — Plan an interview and review

OPleo interview scheduling form with interviewer, date, format and feedback fields
Interview records keep the candidate, role, interviewer, schedule, recommendation and feedback together. Email sending requires recruitment sender configuration.

06 — Record the hiring outcome

OPleo hiring pipeline with a fictional candidate in the Hired stage
The Hired state shown with demo data. Rejected is also a supported stage. Accepting an offer response updates the candidate to Hired; employee onboarding remains a separate step.

Check fit before switching

  • The pipeline supports the documented stages; custom stages and external job-board integrations must be confirmed before purchase.
  • Public applications and response links are distinct from a permanent candidate login portal.
  • Hiring decisions and interview assessments remain the team’s responsibility. Candidate scoring is not a substitute for review.

Questions about applicant tracking

Is OPleo an applicant tracking system for Pakistan?

OPleo supports job openings, public applications, role-linked candidates, interview records and offers in a Pakistan-focused people-operations workspace. Validate your hiring workflow and sender configuration before adopting it.

Can candidates apply without registering?

Yes. An open job’s public page accepts candidate details and a CV without an OPleo workspace account.

Which CV formats can applicants upload?

The application form accepts PDF, DOC and DOCX files up to 5 MB, with server-side type and size validation.

Can we track interview stages and applicant status?

Yes. Candidates can be recorded as Applied, Screening, Interview, Offer, Hired or Rejected. Interview records hold the interviewer, date, time, format, feedback and recommendation.

Does OPleo have a candidate portal?

It provides public job application pages and expiring interview/offer response pages. It does not provide a permanent candidate account with a full application-history dashboard.

Does Hired automatically create an employee record?

Do not assume automatic onboarding. Offer acceptance updates the candidate stage; employee records, reporting lines and portal access need a separate verified setup.

Bring your real workflow to the demo

Use a redacted example, your attendance setup and the decisions your team needs to make. We can review fit before you move live records.

Request a workflow demo