Change position information when approved structure should be different on a selected date. Structural changes can include department, job code, FTE, work schedule, reporting relationship, or another configured position field.

Before you begin

You need the Manage positions permission for every affected department. A proposed change can also require the Submit position requests permission and approval under your organization’s workflow.

Propose a change

  1. Open the position and confirm the effective date.
  2. Choose the field or action you need to change.
  3. Enter the new value and the date it should begin.
  4. Review any effect on assignments or reporting relationships.
  5. Save and submit the request when prompted.

The approved value remains in effect until the request is approved and its date arrives.

Choose a later change or a correction

Use a later dated change when the earlier value was true and the organization changes afterward. Use a correction only when the recorded value or date was wrong.

Example: later department move

A position belongs to Operations through June 30 and moves to Finance on July 1. Propose Finance beginning July 1. The June structure remains Operations.

Example: recorded department was wrong

The position was entered in Operations on April 1, but approved records show it belonged to Finance from April 1. Use the available correction process and record why. Do not add a later Finance value merely to hide the error after another date.

This distinction protects reports and activity history.

Review effects before saving

A structural change can affect more than the field being edited.

  • A department change can affect access, approval routing, reporting, job code availability, and assignment management.
  • A job code change can affect catalog reporting, pay-grade context, and labor budget rate selection.
  • An FTE change can affect vacancy, overassignment, labor budget, and request impact.
  • A work schedule change can affect schedule-based adjustments.
  • A reporting-line change can move the position in the org chart and cannot create a loop.
  • Suspend, Reactivate, and Eliminate change lifecycle through the position change approval process. Review their dates and effects alongside changes to details.

Review active and future assignments and any open request before proposing the change.

Build a multi-date change

Record each dated transition and review the complete timeline before submission. A Position change request can include a suspension and an approved reactivation together, including changed FTE on return.

For example, a position can move to 0.8000 FTE on July 1 and return to 1.0000 FTE on October 1. Review both changes as one planned sequence. Do not use an end date that accidentally leaves a gap.

For temporary withdrawal or permanent ending, see Suspend, reactivate, or eliminate a position.

Correct an identifier

Use the specific identifier action to correct an external position ID when your access permits it. An identifier correction does not replace the normal request process for structural changes.

External IDs should remain stable and unique when your organization uses them to match another trusted source. Confirm the position number and current external ID before saving a correction.

Discard a proposed value

Discard a proposed value only when it should no longer be considered. If it is part of an active request, change or close the request first as directed on the page.

Discarding a proposal does not undo an approved value. If the request was already approved, use the appropriate later change or correction based on what happened.

Keep financial work separate

Change a labor budget rate or adjustment in Labor budget. Change an employee compensation record or adjustment in Compensation. Those changes do not belong on the position form.

Verify the approved result

  1. Review the request outcome and effective date.
  2. Select the day before the change and confirm the earlier approved value.
  3. Select the effective date and confirm the new value.
  4. Review assignments, staffing, and reporting lines affected by the change.
  5. Review labor budget or forecast results after updating completes when the structural change affects them.
  6. Open Activity to confirm who submitted, decided, and recorded the change.

Discard unsubmitted changes

For an approved or scheduled position with unsubmitted edits:

  1. Open the position and review the edits you intend to abandon.
  2. Open Actions and choose Discard draft changes.
  3. Check the number of unsubmitted values listed in the confirmation.
  4. Confirm the discard.

This action removes the eligible unsubmitted edits together. Approved values and their effective dates remain unchanged. It does not cancel an approved suspension, reactivation, or elimination.

An active request can block the action. Review the linked request and use its supported cancellation or correction process instead of trying to discard submitted work.

Check the approved information after discarding and confirm the unwanted proposals are gone. Activity history records the action and reason.