A position request asks your organization to approve work for one position. It brings the proposed information, effective dates, reasons, and supporting files together so reviewers can decide a specific proposal. Related changes on several dates can belong to the same request; changes to another position need a separate request.

What a request can authorize

New position requests authorize draft positions. Position change requests can change details, suspend, reactivate, eliminate, or amend a scheduled action. Replacement hiring requests authorize refilling a position; they do not assign an employee or change its structure.

Request summaries and lists identify these request types. When a request includes several types, each applicable type is listed. In the comparison, Requested action describes the operation being approved; the rows below it show the proposed position fields. Not yet created means a new position has no approved baseline yet.

One request can include more than one effective date when the position changes in stages. For example, a department move can begin in October and an FTE increase in January. Review every dated change before submitting.

Employee assignments, budget rates, and employee pay have separate tasks and permissions. Do not assume a position approval also enters those records.

Follow a request from preparation to outcome

Stage What happens What to check
Prepare The requester enters the proposed work and required explanation or files Values, dates, reason, and the intended outcome
Review before submission FTE Tree shows the proposal, required steps, and relevant checks Who must review it and any missing information
Submit The submitted information is fixed for review The request exists and its status is clear
Decide Eligible reviewers act at the current step The proposal and evidence support the decision
Apply Approved changes are recorded Application succeeded and the dated records are correct

Your organization’s setup determines the steps. Every editable Position field has a required review step. Position changes include every step through the latest one required by their changed fields. New position and Replacement hiring also have their own required review. Later reviewers wait until their step is ready. Required file checks and workforce requirements can also affect progress.

Understand approval, application, and dates

Approval records the required decisions. Application makes the authorized change part of the approved records. The effective date says when that information applies. These are related events, but they answer different questions.

For example, a position increase approved and applied on September 15 with an October 1 effective date is an approved future change. September staffing still uses the earlier FTE; the new FTE applies from October 1. Check both the request outcome and the position on its effective date.

Final approval applies the complete submitted position changes together, subject to the final checks. A workforce plan can help you start an ordinary request for one position, but it does not submit requests in bulk. An authorized administrator can instead apply selected plan changes directly. See Review and apply plan changes for that separate administrative process.

Know what stays fixed after submission

Reviewers decide the submitted proposal, including its dates, reasons, files, impact, and approval steps. Later changes to organization setup or approved records do not silently rewrite it.

If the proposal is wrong, use the available correction or closing action and prepare a replacement when required. A denial is a decision on the submitted request. Administrative intervention has its own permissions and is covered in Administer an active request.

Know who needs to act

The requester prepares and follows the work. Eligible reviewers decide the current step. Organization administrators maintain access and approval setup; that role alone does not grant every record or decision permission. The requester and authors of selected changes cannot independently approve their own work through an ordinary review step.

Use the request’s status and next action to follow progress. If a workforce requirement blocks an action, inspect the target, measured result, and missing information. If the page says Checking requirements, wait for the calculation to finish before trying again. Use request troubleshooting when the next step is unclear.

Successful approval and application

For an ordinary Position request, completion means the approved dated information has been saved successfully. If saving fails, the request stays open and shows that application needs attention. Review decisions already made remain recorded. A retry or corrected request must resolve the problem before completion.

A direct plan application can close an overlapping request, including one whose review has finished but whose changes have not been applied. The request keeps its original proposal and decisions and shows which changes were fulfilled, superseded, or left unapplied. Closing a request this way does not record departmental approval.

Review a transfer across departments

Both the departing and receiving departments review a transfer. If a position moves from Operations to Sales in November and from Sales to Support in January, the department review covers Operations, Sales, and Support in that order. Sales considers both its arrival and departure. All reviewers need the complete submitted timeline and explanation.

Department responsibilities run in sequence within each department review step. A central review runs once at its configured place, whether before or after the department reviews. A person eligible for several department responsibilities in the same step can explicitly approve those responsibilities together; that approval never replaces a separate central or later step.