Job requisition tracker

Register

Which positions somebody has asked to fill, who is asking, and where each request has got to.

A headcount request, not a person

A requisition can be approved, refused, put on hold and closed without any candidate existing. That is why it is not stored the way a candidate is: different lifecycle, different approver, and a report that counted people and headcount requests together would be meaningless. The candidate tracker points at a requisition by its id, which is the real relationship.

No money in it

No salary band, no budget, no offer terms, no payroll. Compensation planning is a finance and HR function with its own confidentiality, and this is the operational register of what has been asked for and whether it was approved.

The rest of the pipeline

People being considered go in the candidate tracker, structured interviews in the interview scorecard, and the administrative draft of an offer in the offer letter builder. Once somebody starts, the onboarding checklist takes over.

A record of positions requested and their status. It holds no compensation planning, no budget, no payroll and no offer terms, and it makes no employment decision of any kind. CompliMaint gives no employment-law advice. Everything runs on your device.

Questions people ask

What is a requisition, as this tool means it?
An internal request to fill a position — raised by a hiring manager, usually approved by somebody who controls headcount, and closed when the role is filled or withdrawn. It exists before anybody has applied and is independent of who any individual candidate is.
Why is a requisition separate from a candidate?
Because they are different things. A requisition is a headcount request; a candidate is a person. They have different lifecycles, different approvers and different consequences, and storing them the same way is how a report ends up counting human beings and budget requests in the same column. The candidate tracker links to a requisition by its id, which is the honest relationship between them.
Does it handle salary or budget?
No. There is no compensation field, no budget, no payroll and no offer terms. Those are finance and HR functions with their own systems and their own confidentiality, and this is an operational register of what has been asked for.
Why does it ask which location?
Because a requisition belongs to the place doing the recruiting, and this product already has stable ids for facilities. Somebody hiring for one location picks it once and never thinks about it again; somebody running several gets separate lists.