Where the recruitment journey truly begins
In most organisations, recruitment does not begin with a job post. It begins much earlier, at the point where a department realises the need for an additional resource. Tuhund addresses this critical but often loosely managed stage through its Resource Request Module, a dedicated submodule within the Recruitment module.
This module ensures that every hiring requirement is structured, traceable, approved and auditable from the very first step.
Who can raise a resource request
Any department head or authorised user with the required access rights can raise a resource request. This flexibility allows organisations to decentralise demand creation while still maintaining complete governance through system driven approvals.
The person raising the request can clearly define the need without being forced to finalise recruitment decisions upfront.
What information can be specified
While raising a resource request, the requester can specify:
-
Purpose of hiring
-
Required attributes such as skills, experience, location or role expectations
-
Number of candidates required
The requester may or may not specify:
-
Type of hiring such as permanent, contractual or temporary
-
Recommended salary range
This optionality is deliberate. In many organisations, salary structure, hiring model and final role definition are refined later in consultation with HR and management.
All relevant supporting documents can be attached directly to the request, ensuring context is never lost during approvals.
Structured approval workflow
Once submitted, the request enters a preliminary HR approval stage.
During this stage, HR staff can:
-
Validate and update all relevant details
-
Refine role attributes
-
Adjust or confirm salary ranges if required
-
Update the number of candidates approved
This is the last stage where edits are permitted.
After HR pre approval, the request moves through subsequent approvals which may include functional approval, management approval and budget approval depending on organisational policy.
Approvers at this stage can only:
-
Approve
-
Reject with reasons
No data modification is allowed beyond this point, preserving audit integrity.
Query based approvals and iterative clarification
Tuhund recognises that approvals are not always binary.
An approver can raise a query instead of approving or rejecting. This allows clarification, discussion and justification to happen without breaking the workflow. These discussions may go through several rounds before a final decision is taken.
If a request is rejected, it flows back to the pre approval stage. At this point, the request can either be modified or taken up for further discussion with the rejecting authority.
From request to job position in one click
Once fully approved, the resource request can be elevated to a job position with a single click.
At this stage, the system can automatically:
-
Create a job position
-
Publish it on the organisation’s public career portal
-
Post it to configured job portals
While the job position workflow is outside the scope of this article, it is important to note that the entire recruitment trail begins at the moment the resource need is raised, not when resumes start arriving.
Part of a larger recruitment ecosystem
The Resource Request Module is a submodule of Tuhund’s Recruitment module, designed to support different operational models.
1. Hiring for your own organisation
You use both the Resource Request Module and the Recruitment Module end to end, from internal approval to onboarding.
2. Outsourcing recruitment to agencies
You use the Resource Request Module internally. Instead of elevating the request to a job position, the approved request is forwarded to recruitment partners. This can be done through hard copies, automated emails or APIs.
3. You are a recruitment agency
In this case, you may not use the Resource Request Module at all. Job requirements come directly as job profiles, either entered manually or received through APIs. Recruitment then starts directly from the job position stage.
Why this matters
By formalising the resource request stage, Tuhund ensures:
-
Clear justification for every hire
-
Budget alignment before recruitment begins
-
Zero ambiguity during audits
-
Complete traceability from demand to deployment
Most importantly, it ensures that recruitment is driven by organisational need, not ad hoc urgency.
