Every year around this time, small-business owners start asking some version of the same question: should we do bonuses this year, and how much? The instinct is generous. The execution is usually improvised — a number that feels right, decided in December, handed out with a nice note. And then something strange happens. People who got a bonus are unhappy. Someone compares amounts. Someone assumes last year's number was a floor. Someone who worked hardest got the same as someone who didn't, or got less and was never told why. The owner spent real money and bought resentment with it.

The money isn't the problem. The problem is that an undesigned bonus asks each person to guess what it means — and people fill that silence with the least flattering explanation available. A bonus that works is one where everyone who receives it could explain, in a sentence, why they got what they got.

Decide what the bonus is for

Before any number, pick the purpose. There are really only three, and they lead to different designs:

Mixing the purposes is where resentment starts. A bonus announced as “sharing our good year” that turns out to vary wildly by person reads as favoritism, even if the differences were deserved. Choose one purpose for the company-wide bonus, and handle anything else separately and on purpose.

A formula you can say in one sentence

Whatever the purpose, write the rule down before you calculate a single amount, and make it short enough to say out loud. “Everyone employed through year-end receives the same percentage of base pay, prorated for start date.” “A shared pool, split by a common percentage, adjusted up or down one step based on the year's review rating.” If you can't say it in one sentence, you can't apply it consistently, and you won't be able to explain it when someone asks.

Decide eligibility in the same sentence: who's in (full-time, part-time, recent hires, people who've given notice), and how partial years work. These edge cases are where most bonus disputes live, and they're far easier to settle as a rule in October than as a judgment call about one person in December. Then apply the rule to everyone and read the list. If an outcome looks wrong, fix the rule and re-run it — don't hand-edit one person's number, because a hand-edited number is the one somebody eventually finds.

Tell people before the check lands

The worst way to announce a bonus is to let payroll announce it. Say it first — to the team, what the bonus is for and how it's calculated; then to each person, what theirs is. A short individual note is enough: the amount, the rule it came from, and one specific sentence about their year. The specific sentence matters more than the amount, which is why it's worth the time.

Just as important: say what the bonus isn't. If it depended on this year's results, say so plainly — “this reflects this year; next year's depends on next year.” Otherwise the amount quietly becomes an expectation, and the first lean year feels like a pay cut to people who were never promised anything.

The payroll part people forget

A bonus is wages. It runs through payroll with withholding, not as a personal check or an envelope of cash, and non-cash gifts with real value can carry the same treatment. The exact handling depends on your payroll setup and your state, so the practical rule is simple: tell your payroll provider or accountant what you're planning before you promise a net amount to anyone. The second-most-common bonus complaint, after “why did they get more,” is “why is my check smaller than you said.”

Keep bonuses from doing salary's job

One pattern deserves its own warning: using a bonus to paper over base pay that has fallen behind. It's tempting — a one-time payment feels safer than a permanent raise. But the person underpaid all year is still underpaid in January, and a bonus used as a patch tends to surface later as a pay-compression complaint with interest. If someone's base pay is wrong, fix it through the salary range conversation. Keep the bonus for what it's for.

The bottom line

A year-end bonus is a message with money attached, and the message is what people remember. Choose one purpose. Write a rule you can say in one sentence, with eligibility settled in advance. Apply it to everyone and read the list before you pay it. Tell the team, then each person, before payroll does — including what it isn't. Run it through payroll properly. And never use it to avoid a raise someone has earned. Done this way, the bonus buys what you meant it to buy: people who know exactly why they were thanked.

— Tom

Bonuses people can explain back to you

HRByDesign keeps the bonus rule, the eligibility list, and the individual letters in one place — so the formula is applied the same way to everyone, and the conversation happens before payroll does.

See how HRByDesign works →

About the author

Tom Christian is the founder of HRByDesign, an AI-native HR platform built for SMB and growth-stage HR managers running the function alone.

He has spent twenty years inside people operations, training, and QA at scale — Guardian Life, ConnectiveRx, and Horizon Blue Cross Blue Shield's Service Division. He writes about HR-of-one survival, compliance that actually applies to small employers, the automation/judgment line, and the operating discipline of running an HR function without a department.