Review and apply plan changes

Review and apply work directly from the change list on Changes. Applied rows remain in the list. Direct application records an authorized administrative decision; it does not create reviewer tasks or record approval on behalf of departments.

Excluded items and independent work

An item marked Excluded from results cannot be selected for application. Its proposed value remains visible, but the planned outcome uses current approved information in its place. Review the explanation and edit or remove the item. Required companions and dependent changes may also be excluded.

You can review and apply independent eligible changes while excluded items remain in the plan. Reviewing the whole plan selects usable changes; excluded items stay out. Always check the selected-change list before confirming. An application keeps its exact reviewed selection, and later changes require a new review.

Before you begin

You need Manage plans to prepare the selection and the underlying viewing permissions for every selected change. Direct application separately requires Apply plan changes and authority over every affected department, effective date, and kind of official information. Planning access alone does not grant permission to change official positions or pay. An authorized administrator may apply changes they prepared, with a required business reason.

Keep private pay information out of general names and conversations. If a required companion is outside your access, ask an administrator to arrange review by someone authorized for the complete work.

Choose the changes to apply

1. Open Overview and check the baseline, outcome, and calculation status.
2. Open Changes. For one change, choose its Review & apply link.
3. For several changes, check their rows and choose Review selected changes.
4. Review the complete selection, effective dates, before/after values, and required companions.
5. Check existing approval requests, which will close, and which of their proposed changes will remain unapplied.
6. Enter the required application reason and choose Apply selected changes when your permissions and the current checks allow it.

A prepared or queued application is accessible from each included change’s review link. A selection containing several changes always opens that complete set; opening one row does not narrow it.

Select across pages

Select visible changes checks the available rows on the current page. When the filtered list spans several pages, Select all matching changes selects the available changes across those pages. The count identifies selections outside the current page or filter. Changing a filter does not silently drop earlier choices; Clear selection removes them. Review selected changes becomes available when you select at least one change.

Selections are tied to the changes you saw. If the plan changes, reload and select the current work again. Applied, withdrawn, already-official, or otherwise unavailable work cannot be selected for another application. The final review checks the exact set again.

Required companions

A business change may contain several fields or dates, such as a hire with pay or a pause and return. Those parts stay together. The review also adds genuinely required work, such as a proposed position needed by a new assignment, and explains it in Why included.

Inspect all required companions before confirming. If any selected change fails a required check, none of that application becomes official.

Read costs, impacts, and status together

The default All changes list includes Planned and Applied work. Pending rows show the current baseline and planned values; applied rows show the saved before and applied values. Open View application for the original values and decisions.

The review’s Before this change includes earlier selected operations on that target, not unselected plan work. For example, a September return after a selected July suspension starts from Suspended. Sorting the table does not change the business sequence.

Rates identify their units and basis. An assignment or adjustment end date is its first excluded day. Future-dated applications retain their effective dates rather than taking effect early.

Choose Withdraw change from the row’s other actions to remove unapplied work. Required parts stay together and affected unfinished reviews close. Applied changes require a new effective-dated correction.

Create an ordinary position request

If the position change needs departmental review instead of direct administrative application, choose Create approval request beside that position. The normal request form opens with the proposed changes filled in. Review the dates, reasons, and required files, then submit explicitly.

Each request contains one position and follows the ordinary approval process, including both departing and receiving departments for a transfer. A plan does not create requests in bulk or wait for a group of requests to approve. Final approval applies the submitted position changes through the ordinary process. Changes across several positions that must apply together belong in a direct plan application.

Check active requests for each position

The position’s details in the plan show active requests you may view, with links and their current review stage. An active request may concern different work; its presence alone does not mean the plan will close it.

The application preview uses only the changes selected for application. It identifies requests whose proposals will be fulfilled, superseded, or affected enough to require fresh review. Different effective dates can still overlap when an earlier value continues into a later period. Unrelated requests stay open.

For example, request #123 proposes a transfer, an FTE increase, and a title change. The selected plan application includes the transfer and FTE increase. Its confirmation explains that #123 will close and the title change will remain unapplied. The application does not silently submit or approve that remaining change.

When an application closes a request

An overlapping request closes as a whole, even when only part of its proposal is applied. Its remaining review tasks stop. If review finished but application had not succeeded, the old request cannot later apply the superseded proposal.

The original submitted information, files, explanations, and decisions remain available under their usual access rules. The request and the plan application link to one another and record the administrator, time, reason, and outcome of each proposed change:

For example, applying 0.8 FTE when a request proposed 1.0 FTE supersedes that proposal; it does not fulfill it. Choose Create request for remaining change when an unapplied proposal is still needed. Review its values against the updated position and submit a new request for fresh approval. Prior approvals do not carry forward.

If changes must happen together to form a valid operation, the selection cannot leave out a required part. Merely placing several proposals in one approval request does not make them inseparable.

Shared rates and other sources

Budget, compensation, and staffing changes each require the relevant management permissions. A shared rate needs permission for every department it affects. It does not acquire position approval merely because it is in a plan.

When a rate is selected with position changes, the administrator needs authority for the entire selection. Every required part applies together. Independent changes can be selected and applied separately.

Check workforce requirements

Workforce rules check the exact selected work. Unselected savings or staffing cannot offset its effects. A configured blocking breach or unknown result prevents application; a warning follows the configured policy.

Wait while requirements are being checked. Resolve a blocked result or use the offered retry action after a stopped check. Current information and requirements are checked again at application.

Apply selected changes

Open the prepared selection, inspect the complete work and the affected requests, enter the required reason, and choose Apply selected changes. Background progress does not mean some rows have become official: all selected changes and request closures succeed together, or none do. If the request or relevant information changes after the confirmation page opens, review the updated consequences before continuing.

You may leave and return through the originating change. After success, every included row says Applied and opens the same recorded application. The baseline refreshes automatically and the outcome contains only remaining proposed changes. Retrying a completed application does not duplicate its effects.

Application notes

An application reason is always required. Explain the business authority and intended outcome, including why overlapping requests should close. The reason stays with the application and is available to people authorized to review its complete selection.

The reason stays with the application even if it fails. Completion links back to that initiating action. A new retry explanation belongs to the retry; it does not replace the earlier reason.

Applying changes after a rejection

A previous rejection remains a rejection. Applying overlapping rejected changes requires the explicit Override rejection and apply action and a reason. The application records the administrator’s exceptional decision and retains the rejection and its explanation. It never converts that reviewer decision into approval.

Direct application and an override cannot bypass record-management permissions, information that has changed, valid dates, required related changes, capacity, or blocking workforce rules.

Resolve changes made during review

Changed official values, dates, effects, or request outcomes can mean a prepared selection no longer matches the intended work. Inspect the message, return to Changes, and review the current selection and its consequences again. Previous applications and request decisions remain in history.

An exact proposed change made elsewhere is Already official, not an application from this plan. If an applied change is later reversed, propose and review a new change to make it again.

Understand progress

Cancel remaining work

Canceling an unfinished application preserves its history and does not undo applied changes or close a position request. Request closure occurs only with a successful overlapping application. Archiving a plan makes its retained baseline and outcome read-only. A correction to official information requires new authorized work.

Retry stopped work

Plans update automatically when approved information changes. Earlier complete results remain visible while the latest changes are calculated. An indicator identifies results that may be out of date. Updates retry automatically after interruptions; you can leave the page and return later. Wait for current results before applying the latest changes. Issues such as missing employee pay have their own View issue link and correction instructions.

For other stopped work, read the message and use the offered recovery action. Calculation retries do not apply changes again. Application retries recheck current authority and requirements. Another manager may continue stopped preparation only with the required authority and explanation.

Optional practice: make the reviewed salary increase official

Use prepared practice records. In 2027 pay review, review Avery’s $63,000 annual salary from January 1, 2027. Confirm the assignment, pay type, date, and $75,600 yearly compensation, enter an application reason, then apply with the required authority. No position approval request is created.

After refresh, baseline and outcome both show $75,600 compensation if nothing else remains planned. Avery’s Applied row retains the original $60,000 salary and new $63,000 value. Staffing stays 1.0 FTE and budget $84,000.

When a position stops being used

Review assignment participation and reporting-line consequences with a suspension or elimination. Suspension keeps assignment dates and pauses staffing participation. On return, the same assignments participate again within their recorded dates. Elimination ends affected assignments and cancels starts on or after the elimination date. Employee and pay history remain available; continuing pay requires a separate decision to change or end it. See Position action rules.