ANTE User Manual

Manpower Requests

Manpower Requests is where a department asks for people. The department head raises a request, it is approved, and HR turns approved requests into a job posting. The department then follows how far the hiring got without being able to change it. For anyone who can open Recruitment it is the Requests tab of HR → Hiring → Recruitment; someone who only raises or approves requests gets the same list as its own page, HR → Hiring → Manpower Requests.

Info
Three permissions decide what each person sees. Manpower request access (HR) sees every request and attaches them to job postings. Raise for own section lets a department head raise requests for the departments they head (and every department below) or belong to, and see those departments' requests. The head of a department is whoever holds its top position on the org chart. Approve/Reject decides requests and sees every request once it has been sent for approval.

The request list

One list, with the request number, position, department, headcount, needed-by date, reason, status, the posting it went to (a link) and how many that posting has hired. Click a row to open the request.

Status pills
Waiting approval, Approved, Needs a posting (approved and not on a posting yet), On a posting, Rejected, Draft and All (the default), each with its count. The chosen pill is kept in the page address.
Visible filters (eye button)
The eye button at the end of the pills opens Visible filters: tick or untick a pill to show or hide it, at once. Rejected and Draft start hidden so the pills and the search fit on one line; All is always on. Your choice is remembered on any device you sign in from. A hidden pill is still reachable: a link to it shows it while it is selected, and hiding the selected pill switches the list to All. Counts never change.
Filter and search
The Filter narrows by department and reason; the search box finds a position, department or request number. Active filters show as chips you can remove.

Opening a request shows the position as the title with the request number under it, then the department, headcount, needed-by date, reason and who raised it, the notes, the job posting with Hired 8 of 10 as a bar (and its applications and status), an Approval levels card with each level's approvers whenever the request has levels (whatever its status), and a History timeline, newest first. While it waits, a note at the top says which level it is at and who approves it (or that it is being approved in the approval workflow); a rejected request shows the reason there. People with offer access also see the request's monthly budget per opening (with the job grade or the reason for an override) and the posting's budget.

Raising a request

  1. Open the Requests tab (or HR → Hiring → Manpower Requests) and click New request
    The form opens.
  2. Fill in the request
    Department*
    The department that needs the people. A department head only sees their own departments; HR sees all of them. Departments come from Settings → Departments, with their level name (for example Section).
    Job description
    Optional. Pick the position's job description when there is one: HR uses it to build the job posting, and the position name follows it.
    Position*
    The position you need, e.g. Line Engineer.
    Headcount*
    How many people (1 to 500).
    Needed by*
    The date the people should start. It can't be in the past when you submit.
    Reason*
    New position, or a replacement.
    Notes
    For a replacement, who is being replaced; anything else the approvers should know.
  3. Click Create request, then Submit for approval
    The request gets its number (MR-2026-0001) and goes to its approvers. While it waits it can't be changed; Withdraw takes it back to a draft.
What each status means
StatusWhat happens next
DraftThe section can change, submit or delete it.
Pending approvalThe approvers decide it. The person who raised or submitted it never approves it.
ApprovedHR can create a job posting from it.
RejectedThe reason is shown. Revise puts it back to a draft so it can be changed and sent again.
PostedIt is filled by a job posting; the section sees the posting and how many applied and were hired.

Approving a request

Approvers get a notification and open the request. Approve moves it to the next level, or to Approved on the last one; Reject asks for a reason. With an approval workflow, the decision is made in the workflow's task instead, and the request follows it.

Tip
Nobody approves their own request, even with full access.

Creating a job posting from requests

  1. Open an approved request and click Create job posting from this request
    The new posting form opens with the request ticked, its job description chosen, the openings set to its headcount and Hire by set to its needed-by date (you can change it).
  2. Tick any other approved requests the posting fills
    The form offers the approved requests for the same role as the job description, and only to people with Manpower Request access. Several requests can fill one posting (for example two sections asking for the same position). The openings follow the sum of their headcounts until you type your own.
  3. Create the posting
    The ticked requests become Posted. While the posting is a draft, its Overview tab lists them and Edit changes which ones it fills; a request taken off goes back to Approved. Deleting the draft posting frees its requests too.
Example: two requests, one posting
Requests tickedOpenings proposed
MR-2026-0001 · Section A · 2 × Line Engineer2
MR-2026-0001 (2) + MR-2026-0002 · Section B · 3 × Line Engineer5

Settings

HR → Hiring → Settings → Manpower requests (Hiring settings permission; the standalone Manpower Requests page also has a Request settings button) decides how requests are approved and whether postings need one.

Approved by
Built-in levels (the default) or one of your approval workflows. Only a manpower request approver can change it.
Approval levels
With built-in levels: the levels in order, any one approver on a level decides it. With no levels, anyone holding the approve permission can approve (never the person who raised it). The levels are fixed on each request when it is submitted.
Postings need an approved manpower request
Off, Warn or Required (see the table below). Applies to new postings.
Remind when an approved request has no posting after (days)
Approving a request never creates a job posting by itself: HR still clicks Create job posting from this request. When an approved request has had no posting for this many days (1 to 90; 7 until you change it), everyone with Manpower Request access gets one notification, and the request shows in the Resolution Center as "request waiting for a posting", with a Create job posting button (filled in from the request). The case goes away once a posting uses the request. Leave the field empty for no reminder.
Example: remind after 7 days
Request approvedOn 10 Nov
2 Nov, no posting yetWaiting 8 days: a notification and a Resolution Center case.
6 Nov, no posting yetWaiting 4 days: nothing yet.
2 Nov, used by a postingNothing: the posting is being made.
Postings need an approved manpower request
SettingA posting with no request attached
OffIs submitted as usual.
WarnShows a warning on the new-posting form and the posting, and can still be submitted.
RequiredThe new-posting form will not create it, and it cannot be submitted, until an approved request is attached.

How It Connects

Set up first

  • Hiring — the job descriptions a request can name, and the Hiring settings permission for the request settings.

Feeds into

  • Hiring — approved requests become job postings, whose applications and hires show on each request.
  • Hiring Reports — counts the applications of the postings the requests created.