Help Center/Plan Configurator & Compensation Models/How to approve or reject a plan version
Plan Configurator & Compensation Models•Last updated: 2026-10-20•4 min read

How to approve or reject a plan version

Reviewers record one approval per category on an IN REVIEW version, each by a different person, or reject it with a reason.

Have questions or need step-by-step guidance on this topic?

Ask AI Copilot

Step-by-Step Procedure

1

Open the IN REVIEW version

Select the plan and the version. Under "Approvals required" see which categories are "pending" and which already show an approver DID.

2

Read what you are approving

Check the "Validation findings", use "View in Composer" and use the version comparison if it differs from a previous version.

3

Choose your category

In the "approve as..." list pick a category. Only categories you hold a permission for and that are still pending are offered.

4

Enter a note and click "Approve"

An approval note is required: the button is disabled until the "approval note" field is filled. The page shows "Approval recorded." Repeat with other people until every required category is approved.

💡 Pro Tip: Duties are separated by person: whoever helped author a version cannot approve or release it. A Super Administrator is exempt, and each use of the exemption is written to the audit trail.
5

Or reject

Type a "rejection reason" and click "Reject". The version becomes REJECTED and returns to its authors, who can edit and resubmit it.

Expected Operational Outcome

Each required category shows an approver DID. When all are in, the version state is APPROVED and ready for release. A rejected version is REJECTED with a stated reason.

Troubleshooting & Failure Modes

Symptom: Message that you helped author this version
Likely Cause: Separation of duties.
Resolution: Ask someone else holding the role to approve.
Symptom: Error that each category needs a different person
Likely Cause: The same person tried to approve a second category.
Resolution: Use another reviewer for the remaining category.
Symptom: Error that the content no longer matches its hash
Likely Cause: The recorded content changed after submission.
Resolution: Reject the version, then create a corrected one and resubmit.

Was this guide helpful?

Help us refine our platform documentation