ANTE User Manual

Hiring Settings

HR → Hiring → Settings (the last item of the Hiring menu) holds the set-up every job posting starts from. The list on the left holds every set-up screen, grouped by what it sets up (Job Postings, Pipelines, Screening & Interviews, Requests & Talent Pool, Automation) in the order you set them up; the one you pick opens on the right and its address keeps the section, so a link opens the same one. You see only the screens your role gives you access to.

Tip

New to Hiring? Set Up the Hiring Module walks through every section on this page with one example company, and Run Hiring Day to Day then uses it to hire.

Saving, and the pinned Save row

Each section puts its actions in the title row at the top of the panel, which stays in place: Discard and Save, with Save the one filled button. Both stay off until something changed; Save can also be off with the reason on hover. A dot on the list entry marks unsaved changes, and if you leave the section, move to another page or close the tab with unsaved changes Ante asks first, so nothing is lost without a word.

Job descriptions

The company's library of job descriptions, which every job posting is built from. It has two views: Library (the list) and Template (only for people with Hiring settings access). The list shows job title, position, department, job grade, employment type, version and how many postings use it (Used In), with New Job Description. A Filter pill (department, employment type, job grade) and a search box sit above it; a filter is offered only when the library holds at least two different values for it. When no filter is offered, the bar is not drawn and a search icon sits in the title row beside New Job Description: it opens into the search field, stays open while it holds text, and Esc clears and closes it. The ⋯ menu on a row offers Create Posting, Edit, Duplicate and Delete, each only for people who hold that permission. A job description that was ever posted stays in the library: Delete is greyed out and says why. A job description has three tabs: Document (the printable page, with Download PDF), Edit and Version history.

Job Title*
The name of the role.
Position, Department, Job Grade, Employment Type
Picked from the company lists; the job grade also gives the posting its hiring budget rate.
Description sections
The sections of the template (summary, responsibilities, qualifications and so on), each text or a list of lines.

The JD Template

The fields every job description uses, with a live preview. Built-in fields can be hidden, not deleted; you can add custom fields (text, long text or list).

Label
The heading printed for the field; leave a built-in label empty to use the standard one.
Type
Text, Long text, Number or List (custom fields).
Visible
Whether the field appears on job descriptions.
Required
Whether it must be filled.
Applicants
Whether it is shown to applicants (Show to applicants).

Drag the rows to set the order they print in; a custom field's ⋯ menu has Delete field. Save keeps the template.

Version History

Every save that changes the content keeps that version, numbered 1, 2, 3 and so on. A save that changes nothing keeps no new version. The Version history tab lists them, newest first:

Version
The number. The newest is marked Current.
Saved
When it was saved, and by whom.
What changed
The parts that differ from the version before, for example "Changed: Responsibilities", or "Restored from version 1".
Posting no. / Postings built from it
The job postings made from exactly this version.

Click a version to read it. Compare with current shows only what differs: lines the current version added are green with a +, and lines it removed are red and struck through. The parts that didn't change are named in one line underneath.

Restore this version (for people who can edit job descriptions) saves the old content again as a new version. For example, restoring version 1 of a job description at version 3 makes version 4, which reads like version 1. Nothing is deleted: versions 1 to 3 stay in the history, and postings keep the version they were built from. A position, department or job grade removed since then is left empty.

Some older versions were saved before version history existed, so they are not listed; a version a posting was built from is always kept.

Hiring Pipelines

The company's pipelines: each is a set of stages a posting starts from. A new posting takes a copy of the pipeline you pick. Changing a pipeline later never changes a posting that is pending approval, published or closed. A posting still in Draft follows its pipeline once more when it is published or submitted (see Job posting).

List
Name, number of stages, typical length in days, the postings using it and which hiring type it is the default for. New pipeline asks for a name and what to start from (Blank, or a copy of an existing one). Each row can be renamed, duplicated or archived, and Show archived lists the archived ones (Restore brings one back; an archived pipeline is read-only and cannot be picked).
A pipeline
Open a row for its stages in order (at most a fixed number). Each stage shows its Form, an optional Document it prints, Filled by (Applicant, HR, Interviewer, Clinic or Approver), Moves on (today HR decides; nothing moves people automatically) and a linked workflow. Hired is where every pipeline ends, not a stage.
Its workflow (Open in Process Builder)
Every pipeline keeps a workflow behind it, in step with this screen: one step per stage, saved when you save the pipeline. Open in Process Builder (beside Rename) opens it, to add what this screen doesn't set, such as an approval. A step added there shows here in its place as a greyed, read-only row, for example "Approval: department head (added in Process Builder)"; saving the pipeline keeps it. If the workflow was saved in the Process Builder after you opened the pipeline, Save asks you to Reload first. A Hiring workflow with stage steps that was installed or built in Processes shows in this list as a pipeline too.
Default for
Batch or Individual: new postings of that kind start from this pipeline. There is one pipeline per kind; picking it here takes it from the other.

Hiring documents

The printable documents a pipeline stage can produce, one row each, with its number format and prefix, whether it is printed then scanned back, and how many pipeline stages use it. Open a row to preview it. The list is read-only; each company's numbering is set in Settings › Documents › Numbering, and a numbered print is made from an application's page.

Pipeline Defaults

What every new posting starts with. Changing a default never changes a posting already made, and each posting can change its own copy.

Default Stages
The stages added to a new posting, in order (each interview round is its own stage). Pick a Stage Type and press Add Stage; each stage has a Label, a Cost Model (No cost, Staff time, Reviewer time or Fixed fee), Open (days) (start to cutoff, counting both days; empty means 7), Review (days) (after the cutoff for HR to finish; empty means 0) and Visible to applicants. A posting's Fill dates lays the stages out from Open and Review.
Approval: Postings need approval before publishing
A company rule, never a tick on each posting: Off, All postings or By hiring type (switch on Batch postings need approval, Individual postings need approval or both). When approval is needed, Approved by picks a workflow whose approval step decides, or Built-in levels, and the Approval levels below stay as the fallback: any one approver on a level approves it, and levels go in order. The rule is checked when a posting is submitted; a posting already submitted keeps its approvers. Only someone who can approve postings can change it.
Allowed Start Days
Under Deployment / Start Days: the days of the month a hire may start; empty means any day.
Default Panel Method
Average (the stage score is the average of the interviewers' scores), Separate (each interviewer's score side by side; their average ranks) or Consensus (the panel agrees one score, entered by the lead interviewer or HR) for new interview stages. Each stage can change it.
Offer answer window (hours)
1 to 720 (24 is common). When it passes, the offer expires.
Offer Approval
Offers need approval before sending, with its levels and Approved by (a workflow, or the built-in levels). New postings start with this and each posting can change it. Only an offer approver can change it.
Promotion
Promotion needs a workflow: when on, pick the Workflow. A candidate can then be promoted to employee only once that workflow is complete, or at its Promote to Employee step. Only an offer approver can change it.
Pre-employment requirements
The items recorded on the "Offer & Pre-employment" workflow step: each has a Requirement name, a Kind (Tick, Text or Date), Required and Government number (shown masked; full numbers need HR records access). Required items must be done before that step can be submitted, and Promote to Employee is refused while one is missing. Until you change it, the built-in list is shown.
Detailed application documents
The documents (Document, Required) each Detailed application stage starts its form with, as file questions. Edit a posting's form to change one stage.
Medical classification
The company's medical scale, best first: each Class can be marked Stops the candidate (the result is Not cleared) or Deployable with a note (clearing needs an accommodation note). The built-in scale is A–D (D stops; B and C need a note). Only someone with Medical access can change it.
Keep Unsuccessful Applicants (Months)
Under Applicant Data: 6 to 120, default 24. How many months unsuccessful applicants are kept after their last activity: the period the consent text promises applicants. Ante never deletes applicant data on its own. Once this period is up, an unsuccessful applicant (rejected, withdrawn or on a closed posting, and not in the Talent Pool) shows under Due for removal, next to the Talent Pool members whose Keep until date has passed, and HR removes each one there by hand. When personal data is removed, counts by posting are kept for reports.
Consent Text
The consent applicants accept on the form; empty uses the built-in text, and {months} is replaced with the retention months.
Talent Pool: Review After (Months)
1 to 24, default 12: how long a Talent Pool entry is kept (its Keep until date) before it shows as Due for removal; renewing consent restarts it. With Ask applicants to agree to be kept for future openings on, the Consent Line (empty uses the built-in text) is an optional tick box under the privacy consent; without it no new applicant can be held in the Talent Pool.
Retention
Read-only (Hiring settings access): who is past the retention period today, to be removed by hand. Ante deletes nobody automatically. It shows Applicants past the retention period, Their applications, Their files, Protected by the Talent Pool and the pool entries past or near their review date. Review and remove opens the Talent Pool's Due for removal list, where each person is removed with Remove their data.

Fill dates counts working days: the company's rest days, holidays and days off (from Time & Attendance) are skipped, and no start, cutoff or end lands on one. If the calendar cannot be read, it counts plain calendar days and says so.

Example: a stage with Open 5 days and Review 3 days, starting Wed 11 Nov 2026 (Saturday and Sunday are rest days, no holiday)
Stage starts (09:00)Wed 11 Nov 2026
Open: 5 working days, both ends counted (11, 12, 13, 16, 17 Nov)+ 5 working daysCutoff Tue 17 Nov 2026, 17:00
Review: 3 working days after the cutoff (18, 19, 20 Nov)+ 3 working daysEnds Fri 20 Nov 2026, 17:00
Next stage starts (Sat 21 and Sun 22 are rest days)Mon 23 Nov 2026, 09:00

Applicant fields

The lists behind the standard questions on application forms (school, course, graduation year, home province, gender).

Schools
Applicants pick one, or type one under Other. A Tier (1 = top, whole number 1 to 99) and a Technical school flag help screening; Applications and the Talent Pool filter by School tier under More filters, and Reports has a School tier card. A school the applicant typed has no tier.
Courses
Picked the same way; the Field (for example Engineering) groups courses in reports.
Import Excel
Names already on the list (any case) are updated, new names are added. Download the template for the columns.
Active
Inactive entries stay on the list but are not offered on new forms; removing one never changes answers already given.
Gender
Visible to HR only, never to interviewers. Set the Options (one per line, at least two) and Allow gender on application forms (off: gender is never asked on the public form).

Sourcing channels

The channels a sourcing link can be tagged with: the built-in ones plus your own (Add Channel). A channel can be renamed, and hidden from the picker; a hidden channel stays on its links and in reports. Referral can be renamed but not hidden, because its links credit the referring employee. The list shows how many links use each channel.

Talent pool

Keep records for (months)
How long a person stays in the talent pool after being added; on that date they become Due for removal. Applies to new entries.
Remind HR before expiry (days)
The Days left badge turns amber that many days before, so HR can renew consent or let the person go. Applies now.
At expiry
What Remove does to an expired record: Anonymise (keeps report counts) or Delete. HR still presses Remove: nothing is deleted on its own.
Ask for consent again
On Renew, the candidate is asked to agree again before the Keep until date moves.
Invite message
The text Invite to apply starts from, with the placeholders {{name}}, {{posting}}, {{link}} and {{company}}; HR can change it before sending. Empty goes back to the built-in text.
Example: keep 12 months, remind 30 days before
Added to the pool1 Mar 2027
Keep records for+ 12 months1 Mar 2028
Days left badge turns amber− 30 days30 Jan 2028

Interview guides

Reusable interview questions and optional scoring criteria. A guide has a Name, a Description (when to use it), its Questions (at least one) and optional criteria. Each save raises its version. An interview stage copies a guide: edits on the stage stay on that stage, the stage says when the library has a newer version (Update from library), and criteria are copied only while nobody has scored the stage. Deleting a guide never changes stages that copied it. The same library is the Interview questions tab of Interviews.

Keyword dictionaries

Word lists that score free-text answers during screening. A dictionary has a name, a role tag and concepts: each with a Weight (whole number 1 to 100) and comma-separated Synonyms (at most 300 concepts, 30 synonyms each). Each concept matched in an answer adds its weight once; whole words, any case, plurals count. Saving a dictionary rescores the screens that use it. One used by an open posting cannot be deleted.

Example: an answer scored with the Accounting dictionary
Concept (weight)Found in the answerPoints
Accounts Payable (10), synonym APYes, written as "AP"10
Reconciliation (5)Yes, "reconciliations"5
Audit (8)No0
Keyword total15

Manpower requests

Who approves a request (Approved by: a workflow or the built-in Approval levels), and Postings need an approved manpower request: Off, Warn (a posting without an approved request can still be submitted, with a warning) or Required (it cannot be submitted), for the company; and the reminder (Remind when an approved request has no posting after (days), 1 to 90, empty for none): HR is notified and the request appears in the Resolution Center. The fields are explained on the Manpower Requests page.

Automatic starts

Workflows that start by themselves, once per person. Both are off until HR switches them on; one Save in the section's title row saves the changes.

When an offer is accepted, start
The switch and the workflow to start for the candidate the moment they accept their offer (for example Pre-employment). The company's installed standard workflow is pre-selected; only active per-person Hiring workflows can be picked, and switching on needs one.
When someone is promoted to employee, start
The same, started for the new employee right after Promote to Employee (for example Promote + onboarding, whose first step is then already done).
Warnings on a row
If the picked workflow was deleted, archived or is not active, the row says so and nothing would start: pick another or activate it in Processes. If the last automatic start didn't happen, the row says why. The application's History notes each automatic start, and each one that didn't happen with the reason.

How It Connects

Set up first

  • Organization and roles — positions, departments, job grades and the approvers named here come from the company records.

Feeds into

  • New Job Posting — a posting is built from a job description and copies a pipeline, applying the approval rule and start days.
  • Job Posting — each posting keeps its own copy of the stages, dates and interview guides.
  • Talent Pool — the talent pool rules decide how long people stay and when HR is reminded.
  • Manpower Requests — the request rules decide who approves requests and whether postings need one.
  • Hiring Reports — school tiers and sourcing channels set here are the report breakdowns.