You can move a merit cycle off spreadsheets in about 30 days. Spend the first week auditing your current process, the second connecting data and loading your rules, the third testing with a pilot group, and the fourth training managers and launching. The key is to copy your existing rules first and improve them later, so the move doesn’t change the outcomes managers expect.
The Risks of Manual Merit Cycle Management
Spreadsheets work for a small team. As the company grows, the risks of manual merit cycle management grow with it:
- Version control. Files get copied and renamed, and nobody is sure which version is final.
- Formula errors. One broken formula can change dozens of raises without anyone noticing.
- Data exposure. Salary files get emailed, and managers can see pay outside their team.
- Budget overspend. Totals are only checked at the end, when it’s too late to fix.
- No audit trail. There’s no record of who changed what, or why.
- Lost time. HR spends weeks building files, merging them and chasing approvals.
Caribou, a Denver-based fintech company, ran into these problems. Senior leaders spent hours updating compensation data by hand in Excel and UKG, with little visibility into decisions. Moving to one system fixed that.
Before You Start: Pick the Right Time
Start at least six weeks before your next cycle opens. That gives you 30 days to move, plus time for anything unexpected. Avoid starting in the middle of a cycle.
Week 1: Audit Your Current Process
Document exactly how your merit cycle works today. You’ll use this to set up the new system and to check that it gives the same results.
- List every spreadsheet, who owns it and what it feeds into.
- Write down your merit matrix: increase guidelines by performance rating and position in range.
- Record your budget rules: total budget, how it’s split, and any separate pools for promotions or market adjustments.
- List eligibility rules: who’s in, who’s out, and how new hires are prorated.
- Map the approval chain: who reviews whose recommendations.
- Collect last year’s final results to use as a test later.
End of week 1: a written list of every rule your spreadsheet applies.
Week 2: Connect Data and Load Your Rules
- Connect your HRIS so employee data flows in automatically.
- Load salary ranges for every job.
- Load performance ratings, if you use them.
- Set up budgets by department, manager or country.
- Enter your merit matrix and eligibility rules.
- Configure what each manager can see.
Most of the errors in a move come from data, not software. Check job titles, manager assignments and salary ranges carefully this week.
End of week 2: the system holds all your employees, ranges, budgets and rules.
Week 3: Test With a Pilot Group
- Run last year’s data through the new system and compare results with last year’s spreadsheet. The totals should match.
- Pick two or three managers to try a practice cycle.
- Watch where they get stuck, and fix settings or instructions.
- Test the approval flow end to end, from manager to second-line review to HR.
- Generate a few sample employee statements and check the wording.
End of week 3: a tested setup and a short list of fixes.
Week 4: Train Managers and Launch
- Run short training sessions for managers. Thirty minutes is usually enough.
- Send a one-page guide covering how to log in, read the budget, use recommendations and submit.
- Tell managers who to contact with questions during the cycle.
- Launch the cycle.
- Track progress daily: who has started, who has submitted, and budget use by team.
End of week 4: the cycle is live and running without spreadsheets.
What Automated Merit Cycle Workflows Should Handle
When comparing tools for orchestrating merit cycles, check that the software automates the steps HR teams currently do by hand:
| Step | In a spreadsheet | With automated merit cycle workflows |
|---|---|---|
| Employee data | Exported and pasted from the HRIS | Synced from the HRIS |
| Budgets | Calculated per file | Tracked live as managers plan |
| Recommendations | Manual lookup in the merit matrix | Suggested for each employee |
| Approvals | Email chains | Submitted and reviewed in the system |
| Access | Whole files shared | Each manager sees only their team |
| Employee letters | Mail merge | Generated automatically |
| Audit trail | None | Every change recorded |
How Stello AI Fits a 30-Day Move
Stello AI rollouts take 2 weeks, which leaves the rest of the month for testing and manager training. It connects to HR systems including Workday, UKG, ADP, BambooHR, Rippling and Paylocity, and can import Excel files. Admins can launch cycles on their own: choose who’s in scope, assign managers, upload budgets, set dates and configure eligibility.
During the cycle, managers get a recommendation for every employee and see their remaining budget in real time. HR can track every manager’s progress. See how Stello AI runs a merit cycle (link to AI Compensation Planning page).
Frequently Asked Questions
What are the risks of managing a merit cycle in spreadsheets?
Version control problems, formula errors, salary data being shared too widely, budget overspend found too late, and no record of who changed what.
How long does it take to move a merit cycle off spreadsheets?
About 30 days: a week each to audit, set up, test and launch. Start at least six weeks before the cycle opens.
Should we change our merit matrix when we switch?
Not at first. Copy your existing rules so managers get familiar results, then improve them in a later cycle.
What should HR teams automate first in a merit cycle?
Employee data, budget tracking and approvals. These cause the most errors and use the most time in a manual process.
What makes a good tool for orchestrating merit cycles?
HRIS integration, live budget tracking, recommendations based on your merit matrix, approval workflows, access controls and an audit trail.
