The paradox of raise decisions: most owners give raises reactively and feel generous. Most employees receive raises reactively and feel undervalued. The raise that comes only when someone asks reveals that the business wasn’t tracking their performance or the market. Both parties walk away from the conversation unsettled.
A proactive raise process is not more expensive than a reactive one. The business that reviews compensation annually and gives market-justified raises is not spending more than the one that gives raises when someone threatens to leave. It is spending the same money on different terms: the employee feels recognized rather than rescued.
Kiluma holds the compensation records and the review documentation. It does not run payroll or administer salary increases through your payroll system; those are processed in your HRIS or payroll platform. For compensation decisions with legal implications (equal pay, exempt classification, benefit implications of salary changes), consult a qualified HR professional or employment attorney. Kiluma is where the documentation and the decision rationale live.
The Raise Decision Framework gives you the structure for making the decision and documenting it. This builds on the salary work from How to Set Salaries When You Don’t Have a Compensation Team and the conversation preparation from How to Handle a Compensation Conversation Without Losing a Good Candidate or a Good Employee.
Why Reactive Raises Cause Problems
The obvious pattern: a team member performs well, no one acknowledges it in compensation, they get a competing offer, and the owner scrambles to match it. The raise happens but under the worst possible conditions.
The less visible cost is what reactive raises communicate. The team member who got a raise after threatening to leave knows that the business tracks their compensation only under threat. The team member who didn’t threaten and didn’t get a raise knows that loyalty doesn’t produce recognition. Both signals are damaging.
The deepest problem is that reactive raises produce inequitable pay. The employees who ask or threaten get raises. The employees who don’t ask, either because they’re less assertive or because they trust the business to recognize them, fall behind. Over time, the pay structure reflects who pushes hardest rather than who performs best.
A proactive review process removes the threat dynamic from the compensation conversation.
The Raise Decision Framework
The framework has three steps. Each one addresses one of the failure modes of reactive compensation management.
Step 1 establishes the review cadence
Pick a frequency for compensation reviews: annually at minimum, twice a year for fast-growing businesses. The review happens on a schedule, not in response to a request or a threat.
At each review, three questions: Where does this person’s salary sit relative to the current market? Has their performance justified staying in that position, moving up in the range, or adjusting to a new range? What is the business able to do right now?
The cadence makes compensation a business decision rather than a negotiation. The employee who knows the business reviews compensation annually doesn’t need to ask.
Step 2 documents the decision
Every compensation decision (give a raise, hold compensation, or note for next review) gets documented. Four fields: the review date, the market context, the performance context, and the decision with the rationale.
The performance context is not a performance review. It is a one-sentence note on whether the team member’s contribution has been at the expected level, above it, or below it. That note connects the compensation decision to the feedback record without requiring a formal evaluation.
The rationale makes the decision explicable. “Salary raised from X to Y: at the low end of the current market range; performance has consistently exceeded the role standard; business has the capacity” is a rationale. “They deserved it” is not.
Step 3 communicates the decision proactively
The compensation review produces a conversation, not a surprise. After the review, the owner schedules a brief conversation with each team member: what we looked at, what we decided, and why.
A team member who hears the compensation decision proactively has a different experience than one who has to ask. The first person is managed; the second person is administrated.
Even when the decision is to hold compensation flat, communicate it. “We reviewed and market is roughly aligned with where you are; we’ll look again in six months as we grow” is a conversation. Silence is not.
How the Living Library Tracks Your Compensation Review
Without a review record, compensation decisions are made from memory. The market data that was used last time is gone. The rationale for the current salary is gone. The review happens from scratch.
The Living Library is the part of the Kiluma platform that organizes and maintains the business’s compensation knowledge. When compensation reviews are added to the Compensation Review Collection, the Library tracks them: review dates, market context, decisions, and outcomes.
When the next review cycle arrives, the owner opens the platform and finds the record already current. The last review date, market context, decision and rationale, and performance note are all there. The record shows when each person’s compensation was last reviewed and what was decided.
The Conductor, Kiluma’s context-aware AI, can read the review record to prepare for the upcoming review cycle. Ask it: “Based on our compensation review records, who is due for a review, and what did the market show the last time we reviewed each position?” It reads the records and returns the preparation: review timing, prior market data, and any notes from prior conversations.
Schedule the Next Compensation Review This Week
Before a team member asks, set a calendar reminder for the compensation review cycle. Annual reviews at minimum. The reminder should fire six weeks before the planned conversation, giving time to gather market data before the meeting.
If no review has happened in the last twelve months, that is the first priority.
Compensation Decisions, Not Compensation Problems
Before this chapter’s system, compensation was handled reactively, and that reactive posture told the team something:
- Salaries were set without market grounding, creating arbitrary pay structures (How to Set Salaries When You Don’t Have a Compensation Team)
- Benefits were undescribed, leaving total compensation invisible to candidates and employees (What Benefits Small Businesses Can Actually Offer — and How to Talk About Them in Hiring)
- Compensation conversations were conducted without preparation, producing outcomes shaped by leverage rather than information (How to Handle a Compensation Conversation Without Losing a Good Candidate or a Good Employee)
- Raises were reactive and undocumented, communicating that performance isn’t tracked until it becomes a retention problem (this article)
A business with this chapter’s system has compensation decisions, not compensation problems. Decisions can be made deliberately and explained clearly; problems can only be endured. The Living Library is where the compensation record lives. Try Kiluma free for 14 days at kiluma.ai.