Request for Employee Recruitment
Request for Employee Recruitment is a short note of a hiring request: who asked, when, for how many, and a paragraph of job description. It is the oldest of the three request screens and it has been superseded. Use Recruitment Requisition instead.
What it is for
This is the screen a client points at when he asks why there are three screens that all look like a request to hire somebody. The honest answer is that this one came first and the module grew past it.
It records the request and nothing else. There is no department, no position, no site, no grade, no business area, so the request cannot say where in the organisation the vacancy sits. Nothing downstream reads it: it does not become a vacancy, it does not reach the careers page, and no applicant can be attached to it. It is a written note that a request was made.
Recruitment Requisition does all of this and more. It carries the full organisation assignment, it goes through approval, and when it is approved it creates the vacancy by itself. That is the screen to set a client up on.
The screen has no form in the current build, so there is nothing for an HR officer to open. It is documented here because the name appears in the module's screen list and clients ask what it is.
Every field, in plain words
| Field | What it means | What to put in it | Notes |
|---|---|---|---|
| Request | The reference of the request | RFR-0001 | Must be unique. |
| Request Date | The day the request was made | 12 Jan 2026 | |
| Request By | Who asked for the hire | Rizwan Akhtar | Typed, not picked from a list. |
| Requisition Status | Where the request stands | Pick it from the list, see below | |
| Job Description | What the job is, in prose | Weaving machine operator for the night shift, Faisalabad unit. | A paragraph. There are no responsibility lines. |
| Position Date | The day the position is wanted from | 1 Feb 2026 | |
| Deadline | The date by which the hire should be made | 28 Feb 2026 | |
| Start Date | The day the successful candidate should start | 1 Mar 2026 | |
| Application Deadline | The last day applications are wanted | 20 Feb 2026 | |
| Recruitment Type | The kind of engagement wanted | Pick it from the list, see below | |
| Number of Vacancies | How many people are wanted | 3 |
Requisition Status takes one of three values:
OPOpen. The request is still live.CLClosed. The request has been dealt with or abandoned.DDDropdown. Present in the list but carrying no meaning for a request. Do not pick it.
Recruitment Type takes one of four values:
FTFull-Time. The ordinary permanent hire.PTPart-Time. Fewer hours than a full-timer, on the payroll.CONContract. Engaged for a fixed term.INTInternship. A trainee placement.
How to configure it
- Do not. Set the client up on Recruitment Requisition, which carries the organisation assignment and creates the vacancy for you.
Scenarios
"Which of these three screens do we actually use?"
Recruitment Requisition for the request, because it carries the department, position, grade and timeline, it goes through approval, and once approved it creates the vacancy. Recruitment Project is that vacancy, the thing candidates apply to. This screen is neither and is not used.
What it is connected to
- Nothing reads it, and it writes to nothing.
- Recruitment Requisition replaces it.
If something looks wrong
- "We cannot find this screen in the menu" - it has no form in the current build. Use Recruitment Requisition.
- "A request we entered here never became a vacancy" - it was never going to. Only an approved Recruitment Requisition creates a vacancy.