> For the complete documentation index, see [llms.txt](https://help.smartcv.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.smartcv.co/requisitions/creating-a-requisition.md).
# Creating a Requisition
When creating a Requisition, information can include:
* Requisition title;
* Hiring Plan;
* organization;
* department;
* location;
* owner;
* target start date;
* headcount;
* employment information;
* salary range;
* business justification;
* Approval Workflow.
The exact information available may depend on your organization’s configuration.
A newly created Requisition can remain in Draft while it is being prepared.
**Draft Requisitions**
Draft status allows the Requisition owner to prepare the request before submitting it for approval.
While a Requisition is in Draft, the relevant information can be reviewed and updated.
Once the request is ready, it can be submitted for approval.
If an Approval Workflow applies, Worklife Recruit creates the required approval steps and starts the approval process.
**Submitting a Requisition for approval**
When a Requisition is submitted, its status changes to Pending Approval and the first approval level becomes active.
The appropriate approvers can then review the request.
Depending on the Approval Workflow, a level may require:
* approval from any one of the assigned approvers; or
* approval from all assigned approvers.
When the current level is successfully completed, the Requisition automatically moves to the next approval level.
When all required levels have been approved, the Requisition becomes Approved.
See Approval Workflows for a detailed explanation of approval levels and the Any One / All rules.
**Approving or rejecting a Requisition**
An approver can open the Requisition and review its details before making a decision.
The approver can then:
* Approve the request; or
* Reject the request.
Comments can be recorded as part of the approval action.
Worklife Recruit keeps the approval history so that users can see the progression of the request, including the relevant approval levels and decisions.
**Rejected Requisitions**
A rejection does not require the Requisition to be recreated from the beginning.
The responsible user can review the rejected request, make the necessary changes, and resubmit it.
This provides a practical workflow for situations where an approver requests changes rather than permanently ending the hiring request.
The new submission starts the required approval process again while maintaining the history of the Requisition.
**My Approvals**
Users who have been assigned as approvers can access My Approvals.
No special recruitment-management role is required simply because a user is an approver.
The page provides two views:
Pending Approvals
Shows Requisitions that currently require action from the logged-in user.
Users can open the relevant Requisition directly and review the request before approving or rejecting it.
**Approval History**
Shows Requisitions on which the logged-in user has previously taken an approval action.
The history includes actual decisions made by the user, such as:
* Approved;
* Rejected.
Approvals automatically skipped by the workflow are not shown as personal approval actions because the user did not make a decision.
The history can also be filtered to make previous decisions easier to locate.
**Requisition status**
A Requisition moves through statuses according to its lifecycle.
The primary statuses include:
Draft \
The request is still being prepared.
Pending Approval \
The request has been submitted and is currently going through its Approval Workflow.
Approved \
All required approvals have been completed successfully.
Rejected \
An approver has rejected the request.
The current status and approval level make it possible to see where each request currently stands.
**Approval history**
Worklife Recruit maintains the approval information associated with each submitted Requisition.
This allows users to review:
* approval levels;
* assigned approvers;
* completed approvals;
* rejections;
* comments;
* dates of approval actions;
* current pending level.
This provides transparency around how and when a hiring request was approved.
**Requisitions within Hiring Plans**
When a Requisition belongs to a Hiring Plan, its headcount and budget information can contribute to the overall progress of that plan.
This makes it possible to compare planned recruitment with actual hiring requests.
For example, HR can see how much of a Hiring Plan’s intended headcount has already been requested or approved.
See Hiring Plans for more information about plan progress, headcount, and budget monitoring.
**Requisition reporting**
Requisition information is also included in Hiring Planning reporting.
Reports can provide visibility into areas such as:
* Requisitions by status;
* Requisitions created over time;
* planned and approved headcount;
* department;
* owner;
* salary and budget ranges;
* relationship with Hiring Plans.
This provides management with a consolidated view of recruitment demand and approval progress.
**Requisitions vs Jobs**
A Requisition represents the internal request and authorization to hire.
A Job represents the actual recruitment activity and position used to attract and manage candidates.
Keeping these concepts separate allows the organization to complete planning and internal approvals before starting the candidate recruitment process.
**Related Help**
* Hiring Plans – Learn how recruitment requirements can be planned before individual hiring requests are created.
* Approval Workflows – Learn how approval templates, levels, approvers, and approval rules control the Requisition approval process.
