An employee recognition tracker template is the cheapest recognition program there is: a spreadsheet, one row per thank-you, and a second tab that adds them up. No budget request, no vendor demo, no IT ticket. Plenty of teams run on exactly this for a year or more, and it works right up until the moment it quietly stops working.
There's no file to download here. The layout below takes about ten minutes to rebuild in Excel or Google Sheets, and typing it yourself means you'll understand every column. We'll cover the log tab, the monthly rollup, three formulas written out in full, and the five things no spreadsheet can do, so you recognize "outgrowing it" before it happens.
The Log Tab: One Row per Recognition
Tab one of the recognition tracker is the raw log. Every recognition gets a row and nothing is ever deleted. Eight columns cover everything the rollup needs:
| Column | Header | What goes in it | Example |
|---|---|---|---|
| A | Date | The day it was given, as a real date cell, not text | 2026-10-14 |
| B | Giver | Who said thank you, from a dropdown of names | Priya N. |
| C | Recipient | Who received it, same dropdown. One person per row | Marcus T. |
| D | Team | The recipient's team, looked up from a People list | Support |
| E | What they did | One or two specific sentences | Stayed on the Friday outage call until the customer was back up |
| F | Value / hashtag | The company value it demonstrates, from a short fixed list | #customerfirst |
| G | Reward / points | Points awarded, or the dollar value of any reward. Zero is fine | 25 |
| H | Public? | Yes if it was shared with the team, No if it stayed private | Yes |
Three rules keep this tab honest. Date is a real date, because every formula below filters on it. Giver and Recipient use data validation (Data → Data validation in both tools) pointing at a People tab, so "Marcus", "Marcus T." and "marcus t" can't become three different people. And if one thank-you goes to three people, that's three rows. It's the only way the counts come out right.
Column F deserves a few minutes of thought. Keep it to six or eight values, written as hashtags so they stay short and consistent, and don't add new ones mid-quarter. Employee recognition hashtags has a tested starter set.
The Monthly Rollup Tab
Tab two is where the log becomes something a manager will actually read. Put the month's start date in cell H1 and its end date in H2, then list every person from the People tab down column A. The rest of the row is formulas:
| Column | Header | What it answers |
|---|---|---|
| A | Name | Everyone on payroll, not just people who appear in the log |
| B | Received this month | How many rows name them as Recipient in the window |
| C | Given this month | How many rows name them as Giver in the window |
| D | Last recognized | The most recent date they received anything, ever |
| E | Days since | Today minus column D |
Below the people rows, add a summary block: total recognitions, people who gave at least one, people who received at least one, the givers-to-receivers ratio, and the count sitting at zero. Then a small table with one row per team and the same Received and Given counts. That's the whole rollup. To go further, the employee recognition dashboard post defines eight metrics you can layer on this exact log.
Three Formulas That Do the Work
All three work in Excel and Google Sheets. Row 2 is the first person; copy each formula down. The log tab is assumed to be named Log.
1. Recognitions per recipient this month (COUNTIFS)
In words: count the rows in the log where the Recipient matches this name and the Date falls inside the month. In cell B2:
=COUNTIFS(Log!C:C, A2, Log!A:A, ">="&$H$1, Log!A:A, "<="&$H$2)
Column C is the same formula with Log!B:B (Giver) in place of Log!C:C. The dollar signs lock the month cells as you copy down; change H1 and H2 and the whole tab recalculates for another month.
2. Last recognized (MAXIFS)
In words: the largest date in the log where the Recipient is this person. In cell D2, formatted as a date:
=MAXIFS(Log!A:A, Log!C:C, A2)
Someone who has never been recognized returns 0, which displays as a date in 1899 or 1900. Wrap it so it reads clearly instead: =IF(MAXIFS(Log!A:A, Log!C:C, A2)=0, "Never", MAXIFS(Log!A:A, Log!C:C, A2)). Then E2 is simply =IF(D2="Never", "", TODAY()-D2). Sort by column E descending and the top of the list is the people you've forgotten. MAXIFS exists in Google Sheets and Excel 2019 or later; on older Excel, =MAX(IF(Log!C:C=A2, Log!A:A)) entered as an array formula does the same job.
3. Givers-to-receivers ratio
In words: how many distinct people gave at least once, divided by how many distinct people received at least once. In the summary block:
=COUNTIF(C:C, ">0") / COUNTIF(B:B, ">0")
A ratio near 1 means recognition flows in both directions across the company. Well below 1 means a small group of enthusiasts is doing all the thanking. Well above 1 means lots of people give but it all lands on the same few names, which is the pattern fixing recognition inequality is about. The zero count next to it, =COUNTIF(B:B, 0), is the number that should make a manager wince, and it's the one most tools never show.
Ten Minutes of Polish on the Tracker
- Conditional formatting on the Days Since column: amber past 45 days, red past 90. Format → Conditional formatting in Sheets, Home → Conditional Formatting in Excel.
- Freeze the log's header row.
- Protect the rollup tab so nobody types over a formula.
- A form on the front. Google Forms or Microsoft Forms can write straight into the log tab, turning "open the spreadsheet" into "tap a link". Far more people will bother.
If you also track headcount, the employee turnover rate formula in Excel post uses the same monthly-tab style, and the two sheets sit nicely side by side.
Five Things a Spreadsheet Can't Do
This employee recognition tracker is genuinely useful. It also has a ceiling, worth naming before you hit it.
- Nudge anyone. The sheet can show that Marcus hasn't been recognized in 70 days. It can't tell his manager. Someone has to open the tab, notice, and act, and that someone is usually one HR person who eventually changes roles. Programs die here more than anywhere else; why recognition programs fail has the pattern.
- Enforce fairness. There's no budget per giver, so one generous manager can hand out forty rows a month while a quiet team gets none. Tools that give everyone the same monthly allowance make giving a deliberate act rather than a mood.
- Be timely. Recognition works best within hours of the thing it's recognizing. A log filled in on the last Friday of the month is a record, not a moment. Gallup and Workhuman found inadequately recognized employees are about twice as likely to say they'll quit within a year, and "inadequately" includes "late".
- Make it public. Column H records whether a thank-you was shared. It doesn't share it. Peer recognition gets most of its power from being seen by the rest of the team, which a private sheet structurally can't provide.
- Fulfil rewards. Column G records 25 points. Converting those into a gift card, charging it, and sending it is a monthly chore someone does by hand, with a receipt they have to file.
When to Outgrow the Template
Signs it's time: a couple hundred rows a month, the same three names filling the Giver column, or the rollup's "last updated" date slipping. The fix is usually not a better spreadsheet. It's moving the act of giving to where people already are, and letting the tracking happen as a side effect.
Disclosure: Propsly is ours. It runs in Slack, and every /props +25 @marcus stayed on the outage call until the customer was back up #customerfirst writes a row with exactly the columns above: date, giver, recipient, message, hashtag, points, and it posts to a public feed channel automatically. The free tier covers unlimited users, 200 props per person per month, leaderboards and the feed, which handles nudging, fairness, timeliness and public visibility. The Pro tier at $50 a month flat adds analytics (engagement gaps, concentration, team breakdown) and automated monthly gift-card rewards, the fifth item. If your team isn't on Slack, or you want something free that isn't ours, free employee recognition software compares the options honestly, and measuring recognition program success explains what to watch whichever route you take.
Common Questions About the Employee Recognition Tracker Template
Should the tracker be visible to everyone or just managers?
Split it. The log can be open to all; it's a list of nice things people did. The rollup, especially the zero list and Days Since column, belongs with managers only. Publishing who got nothing turns a prompt into a shaming ritual.
Can I use the same employee recognition tracker in Excel and Google Sheets?
Yes. COUNTIFS, MAXIFS, COUNTIF and TODAY behave identically in both. The only differences are menu locations for data validation and conditional formatting, and that MAXIFS needs Excel 2019 or Microsoft 365.
How do I handle a thank-you given to a whole team?
One row per member, with the same date, giver, text and hashtag. It's tedious, which is why team recognition gets underreported in spreadsheets, and why tools that expand a group mention into individual records earn their keep.
Do I need the points column if we don't give rewards?
Keep it at zero. It costs nothing, and the day someone proposes a rewards budget you'll want a year of history showing how points would have landed.
The Short Version
An employee recognition tracker template is two tabs: a log with Date, Giver, Recipient, Team, What they did, Value, Points and Public, and a monthly rollup driven by COUNTIFS, MAXIFS and a givers-to-receivers ratio. Dropdowns for names, one row per recipient, a form on the front. Watch the zero count and Days Since. When "last updated" starts slipping, the problem isn't the formulas; recognition needs to happen where people already talk.