Skip to content

Recruitment

Hire with a process everyone can follow

A department asks for headcount, the request is approved, and a requisition opens. Candidates apply on your careers site, move through the stages you define, and an accepted offer becomes an onboarding list and, finally, an employee record — without retyping anything.

  • Approved manpower requests
  • Configurable pipeline
  • Careers site on your address
A hiring panel meeting around a conference table with laptops.

Recruitment analytics

Measure the funnel the honest way

Applications that reached each stage
Funnel
Counted from stage events, not from who happens to sit in a stage today.
Measured to offer acceptance
Time to hire
Not to the joining date, which depends on notice periods.
Where candidates came from
Sources
Alongside ageing, offer and interview reports.

What goes wrong today

Hiring that lives in inboxes

  • CVs scattered across mailboxes

    Nobody can say how many people applied, who was rejected, or whether the same person applied twice under different emails.

  • Headcount approved by corridor

    Roles are advertised before the budget holder agreed, and finance learns about the hire from the first payslip.

  • Everything typed twice

    The accepted candidate's details are re-entered into the HR system, with new typos and lost qualifications.

The lifecycle

Every step is an explicit, permissioned action

Nothing advances on a timer.

  1. Manpower request

    A department asks for headcount; approval follows your workflow and raises the requisition.

  2. Requisition and posting

    Build from a versioned job template and publish to the careers site or other channels. Confidential roles are never shown publicly.

  3. Applications

    Candidates apply online; resumes in PDF, Word or text are parsed to pre-fill the profile.

  4. Pipeline

    Screening, shortlisting, assessment and interview stages that you configure and reorder.

  5. Checks

    Background and medical checks recorded against the application.

  6. Offer

    Offer letters merged from templates, approved, sent and answered online by the candidate.

  7. Hire

    Accepted offers raise onboarding tasks and convert to an employee record.

Capabilities

The details that keep hiring tidy

  • Candidates separate from applications

    One candidate profile — education, experience, certifications, languages, skills, references — can apply to several roles.

  • Duplicate detection and merge

    Possible duplicates are surfaced for a person to merge; two people sharing a phone number are never rejected automatically.

  • Interviews with rooms

    Schedule panels, book meeting rooms and collect scored feedback on fixed competencies, so reports compare like with like.

  • Assessments

    Assign assessments to applicants and record scores as part of the pipeline.

  • Public tracking

    Applicants check progress and respond to offers with their reference and email; the careers site never reveals internal details.

  • Authority-based permissions

    Publishing a role, moving a candidate, approving an offer and merging records are separate rights from editing a row.

Offers

Offer letters candidates can rely on

Offer letters are merged from your templates with the package from the requisition, go through approval, and are frozen once sent: the candidate decides against a specific letter. Candidates accept or decline online.

  • Approval before sendingOffers follow the approval workflow you configure.
  • Frozen once sentThe resolved letter is stored, never re-rendered from a changed template.
  • PDF snapshotA PDF copy is kept with the application.
Members of an HR team discussing candidates around a table.

Recruitment questions

Bring your next hire into one system

See a requisition go from request to employee record in a live walkthrough.

  • Approved headcount
  • Careers site
  • No retyping at hire