Total Rewards Statement: How to Build One Employees Actually Read

Total Rewards Statement: How to Build One Employees Actually Read

Your employees think they earn their base salary. You know they earn far more. Employers pay for health coverage, retirement matching, paid leave, insurance, payroll taxes, and development budgets, and most staff never see a dollar figure for any of it. They compare your offer to a competitor's on base pay alone, and you lose value you already paid for.

A total rewards statement fixes that. It turns an invisible cost into a visible, personal number. This guide shows you what to include, where the data comes from, how to build the first version in a quarter, and the mistakes that make employees ignore it.

TL;DR

• A total rewards statement shows each employee the full annual value of their pay, benefits, time off, and development, not just base salary.
• BLS data puts benefits at 30.0% of private-industry employer compensation costs in June 2026, so base pay alone understates what you spend by roughly 40%.
• Build it in five steps: define scope, pull data, calculate, design, and deliver with a manager conversation.
• Keep it to one or two pages, show employer-paid dollars, and label every estimate.
• A statement is only as credible as your pay structure. If grades and ranges are shaky, fix them first.

What a total rewards statement is

A total rewards statement is a personalized document that adds up everything you give one employee in a year. It lists cash pay, employer-paid benefits, retirement contributions, paid time off, and other programs, each with a dollar value.

It goes by other names: total compensation statement, total rewards summary, or "your hidden paycheck." The name matters less than the job it does. It answers one question for the employee: "What is this role actually worth to me?"

Don't confuse it with a pay stub or an offer letter. A pay stub shows what hit the bank account this period. An offer letter shows base pay and a few headline terms. A statement shows the whole annual picture, and it works for current staff, not only new hires.

It also isn't a replacement for your total rewards strategy. The strategy decides what you offer and why. The statement communicates the result.

Why it matters: the numbers behind the gap

The Bureau of Labor Statistics measures what employers spend per hour worked. For private industry workers in June 2026, wages and salaries averaged $32.82 per hour and benefits averaged $14.07. Wages made up 70.0% of employer costs. Benefits made up the other 30.0%.

Run that against a real salary. Take an employee at $80,000. If benefits are 30% of total cost, total compensation sits near $114,000, because $80,000 is 70% of the whole. That leaves about $34,000 of annual value the employee may never have seen itemized. (That is a national average. Your mix will differ, so use your own figures in the statement.)

That gap creates three problems:

• Offer comparisons skew toward base pay. A candidate weighing a $5,000 salary bump elsewhere doesn't see that your retirement match is worth more.
• Benefits spend loses its retention effect. You pay for programs that nobody credits when they decide whether to stay.
• Pay conversations stall. When an employee asks for a raise, a statement gives the manager a fuller picture to work from.

What to include

Use the five elements of the WorldatWork Total Rewards model as your frame: compensation, benefits, well-being, development, and recognition. Not every element has a clean dollar value, so split the statement into two parts.

Part 1: The dollar items. These are the ones you can price.

Part 2: The non-dollar items. List these without forcing a number: flexible work, parental leave, employee assistance programs, learning budget, mentoring, and recognition programs. If you do have a budget figure, such as $1,500 a year for training, show it.

Two rules keep the document honest. Show the employer-paid portion, not the full premium. And separate actual costs from estimates, such as the value of an equity grant.

How to build one in five steps

Step 1: Define scope and audience. Start with all regular full-time employees. Decide now whether part-time and hourly staff get a version. They should, since benefits often make up a larger share of value for lower-paid roles.

Step 2: Pull the data. Work with payroll, finance, and your benefits broker. Ask each for per-employee figures, not company totals. Document the source for every line. This is where most projects slow down, so start the requests first.

Step 3: Calculate. For each employee, add cash pay, employer benefit costs, retirement contributions, PTO value, and statutory costs. Value PTO by dividing annual pay by working days and multiplying by days granted. Round to the nearest dollar. Run totals for 10 employees by hand first to catch formula errors before you automate.

Step 4: Design the document. Aim for one page, two at most. Lead with the total number. Show a simple breakdown by category, ideally a single bar or a short table. Put the footnotes at the bottom: reporting period, data sources, estimates.

Step 5: Deliver it with a conversation. Don't just email a PDF. Brief managers first, give them a three-line talking script, and release statements at a predictable time, such as the start of open enrollment or right after merit decisions. A statement that arrives with no context gets filed away.

Where job evaluation fits in

A statement shows what you pay. It doesn't say whether you pay fairly. If two employees in the same grade see very different totals and nobody can explain why, the statement exposes the problem instead of solving it.

That is why your pay structure matters. Jobs scored against weighted compensable factors land in grades, grades carry ranges, and the statement then shows where each person's base pay sits within the range. You can add that context to the document as a single line, such as "Your pay sits at the 62nd percentile of your range." Only do this if your ranges are defensible. Otherwise, you're printing questions you can't answer.

If you haven't set the principles behind your pay decisions, start with your compensation philosophy and your broader compensation strategy. A statement works best when it reflects a position you've already taken, such as "we pay at market median and invest heavily in benefits."

PointFactors scores jobs against weighted compensable factors, so the grades behind every statement are documented and consistent. See how it works in a demo.

Common mistakes

• Using total premium instead of the employer share. Showing the full $22,000 family health premium when the employee pays $6,000 of it overstates your contribution, and employees notice.
• Printing a number nobody can verify. If an employee can't trace a line to a source, trust drops. Footnote everything.
• Including too much. A six-page document hides the headline. Keep detail in an appendix or online view.
• Ignoring the manager. Managers get the first questions. If they can't explain the statement, employees won't believe it.
• Releasing it once and stopping. Send it every year, on the same date, so employees can see the change.
• Hiding unfavorable truths. If your benefits are thin, a statement won't hide it. It will show the gap, so pair it with a plan.

Measuring whether it worked

Track three things in the first year: survey results on "I understand my total compensation" (aim for a 15-point gain), the number of benefits-related questions HR receives at open enrollment, and voluntary turnover among employees in their first two years. Don't claim the statement caused any change on its own. Treat these numbers as signals and compare them to the prior year.

FAQ

What's the difference between a total rewards statement and a total compensation statement? Most teams use the terms interchangeably. "Total compensation" tends to focus on dollars: pay, benefits, and equity. "Total rewards" is broader and adds non-cash items like development, flexibility, and recognition. Pick one name and stay consistent.

How often should we send it? Once a year, on a fixed schedule. Many employers pair it with open enrollment or the merit cycle. Update it mid-year only for a major change, such as a new benefit or a promotion.

Should we include the employer's payroll taxes? You can. They are a real employer cost tied to each employee, and BLS counts legally required benefits in its compensation figures. Some employers leave them out because employees don't see them as a perk. Whichever you choose, label it.

Do we need software to do this? Not for a first version. A spreadsheet with one row per employee and a mail merge works for a few hundred people. Beyond that, an HRIS or a dedicated tool saves time and reduces errors.

How do we handle equity or bonuses that vary year to year? Show the target and the actual separately. For equity, show grant value at grant date and flag that it is an estimate, not guaranteed pay.

Can a total rewards statement help in pay transparency situations? It helps with internal communication, but it doesn't replace posted pay ranges where the law requires them. Treat them as separate tools: ranges go in job postings, statements go to existing employees.

Who should own the project? Compensation or total rewards usually leads, with payroll, finance, and benefits as data partners. Name one owner. Projects with shared ownership stall at the data step.

Next steps

Pick 10 employees across three grades. Build their statements by hand this week. You'll find your data gaps fast, and you'll have a working prototype to show leadership. For the foundations behind it, read our guides to total rewards and salary structure. For the underlying data, see the BLS Employer Costs for Employee Compensation program.

A statement is only as strong as the structure under it. PointFactors gives you consistent, documented job grades so your pay story holds up. Start free or see pricing.

Justin Hampton is founder and CEO of PointFactors.