Criteria Lock in Compensation Cycles: Why It Matters and How It Works
Quick Answer: Criteria lock is a compensation governance mechanism that makes increment criteria immutable once published to employees. After a cycle goes live, no changes can be made to scoring criteria, thresholds, or weights. This prevents mid-cycle adjustments that could advantage or disadvantage specific employees, and protects the company against pay discrimination claims.
If employees can see the rules change after they start working toward them, the rules are not rules. They are suggestions. And suggestions do not build compensation trust.
Criteria lock is the technical mechanism that turns increment criteria from suggestions into commitments. It is the natural complement to compensation budget simulation — simulation validates the cost before publication; lock enforces the commitment after.
What Is Criteria Lock?
Criteria lock is a feature in compensation management software that prevents any modification to increment criteria after a cycle has been published.
“Published” means the moment employees are notified of the active cycle and given access to view the criteria. From that point:
- No threshold adjustments are possible (e.g., changing the Tier 1 cutoff from 80 to 85 points)
- No weight changes are possible (e.g., shifting performance from 40% to 50% and reducing tenure from 20% to 10%)
- No criteria additions or removals are possible
- No tier structure changes are possible
The lock is enforced at the database level, not just the UI. In MeritCyc, Firestore security rules block all writes to locked cycle documents, regardless of user role. Even a super admin cannot edit locked criteria — the only resolution is to cancel the cycle and create a new one, which generates a full audit log entry.
Why Criteria Lock Matters for Employee Trust
The trust mechanism is simple: employees need to know what they are working toward, and they need to know it will not change.
When criteria can be adjusted mid-cycle, three things happen:
First, employees who are on track lose confidence — they do not know if the threshold they are meeting will still exist at evaluation time.
Second, employees who advocate for threshold changes create an unfair dynamic — some employees know about the change, others do not.
Third, if a change benefits certain groups or departments disproportionately, the company has a discrimination exposure even if the intent was innocent.
Criteria lock eliminates all three scenarios by making mid-cycle changes structurally impossible. See how criteria lock works in MeritCyc.
Why Criteria Lock Matters for Finance and Legal
Finance and legal have a different reason to care about criteria lock: budget and compliance.
When the CFO approves an increment budget based on a budget simulation, that approval is conditioned on specific criteria and thresholds. A mid-cycle criteria change can invalidate the financial model — moving a threshold from 85 to 80 can double the number of qualifying employees and double the budget exposure.
From a legal standpoint, in jurisdictions with pay equity legislation (EU Pay Transparency Directive, UK gender pay gap reporting, US state-level salary transparency laws), companies must be able to demonstrate that compensation decisions were made on consistent, pre-defined criteria applied equally across the workforce. Mid-cycle changes break that demonstrability.
How Criteria Lock Is Implemented in MeritCyc
MeritCyc enforces criteria lock at three layers:
Layer 1 — Firestore security rules. The cycle document in Firestore has a lockedAt field set at publication time. Security rules block all write operations on criteria sub-documents once lockedAt is populated. This enforcement happens server-side, not in the UI.
Layer 2 — Cloud Function gate. All cycle update functions check for lock status before processing. Any edit request on a locked cycle returns a 403 with the error code CYCLE_LOCKED.
Layer 3 — UI enforcement. The criteria builder UI removes all edit controls and displays a lock icon with the lock timestamp when a cycle is in locked status. The only visible action is “Cancel Cycle” — which requires confirmation and generates an audit log entry.
What Happens When Criteria Need to Change?
Legitimate situations arise where criteria genuinely need adjustment. A data feed breaks. A department changes scope. A regulatory requirement shifts.
The correct response is never to unlock criteria. The correct response is:
1. Cancel the active cycle (audit logged, employees notified)
2. Create a new cycle with the revised criteria
3. Run budget simulation on the new criteria
4. Publish and lock the new cycle
This process is transparent, auditable, and honest. Employees know a change was made and why. Finance reviews the new budget model. The new criteria are just as locked as the original.
FAQ
Can criteria lock be overridden by an admin?
In MeritCyc, no. Criteria lock is enforced at the Firestore rules level, not the application level. No role — including platform admin — can write to a locked cycle document. The only action available is cycle cancellation followed by new cycle creation.
What is the difference between criteria lock and approval workflow?
An approval workflow requires a second person to approve criteria before publication. Criteria lock prevents modification after publication. Both are needed in a complete governance model: approval ensures the right people agreed to the criteria; lock ensures those criteria cannot change once agreed.
Does criteria lock apply to the scoring period or just the criteria themselves?
Lock applies to the criteria definition — the weights, thresholds, and measurement rules. Scores submitted by managers are not “locked” in the same way; HR can override scores with justification until the cycle is finalized. The distinction is between the rules (immutable) and the results (reviewable until finalization).
Try MeritCyc
Run your increment cycle with MeritCyc
Budget simulation, criteria lock, and increment stories — built for 50–500 employee companies.
Start Free Trial