How it works
Give, approve, publish and report, in one place
Anyone can thank a colleague in a minute or two. Recognition that needs approval goes to the right people, then appears on a wall everyone can see. Managers see who is being missed, and HR runs the program from one console. Here is what Laurel does at each step.
Give
Thank someone in a minute or two
Give recognition is a short guided form: choose people, choose a type, and say what they did. Only types the people chosen can receive are offered, and each type says whether it needs approval.
- Recognize one person or several at once; each gets their own recognition, worded the same
- Three prompts help people say what happened rather than “great job”; messages run from 12 to 1,000 characters
- Name one of your organization’s values, if it showed one
- Keep it private where the type allows; some types are always private
- Check and send shows each person, who sees it, the first approver, who is told and the allowance left before anything goes out
- Drafts save as people type, are visible only to the author and never count against an allowance
- Managers can recognize someone on behalf of the team
Illustrative screen with sample data.
Approve
The right approver for each kind of recognition
Types that need approval follow their route: the sender’s manager, the recipient’s manager, or a named role on the approver roster, in one or more steps. Approvers see items on their own route, under Approvals.
- Edit wording to tidy a message before it publishes; the original is kept for the people named and administrators, and the sender is told
- Approving opens a check that says what happens next: the next approver by name, or publishing, privately if that’s the recipient’s choice
- Declining needs a reason from a list and a note, which the sender sees; Send again starts a new one from their words
- Nobody approves a recognition they sent or received, or two steps of the same one; Laurel routes around them
- Administrators can pass a stuck step to someone else, with a reason
Illustrative screen with sample data.
Publish
A wall everyone can see, and choices about who sees what
Approved, public recognition appears on the wall, newest first, with its badge, the people, the message and the value it showed. Anyone can search it and filter by type, department, location and period.
- Types can be public, private or the sender’s choice
- Each person decides whether new recognition about them goes on the wall or waits until they share it
- Either person named can take a recognition off the wall without deleting it; only whoever hid it can put it back
- Anyone can report a recognition with a reason, and sees the recognition team’s decision and reply
- Senders can change the wording while nobody has approved it, or for 7 days after a no-approval type is published, and withdraw it while it’s waiting or for 30 days after it’s published
- A home page web part shows recent recognition on your intranet home page
Illustrative screen with sample data.
My team
Managers see who is being missed
Anyone with direct reports in Entra ID gets My team. It lists their people, what each has received and given, and names anyone who hasn’t been recognized in 90 days.
- Direct reports by default; a manager of managers can switch to their whole reporting line
- Private recognition shows for a manager’s own direct reports, and stays with each person’s own manager further down
- A recognition record for each person, for any period, with counts by type and value and a CSV for one-to-ones
- Hide from the wall for a direct report, with a reason they see; they can put it back
- Only managers in a person’s reporting line see their page
Illustrative screen with sample data.
Run
HR runs the program from one console
HR admins and site owners manage everything in the management console. Changes apply straight away, are written to the audit log, and the last one can be undone.
- Recognition types: badge, audiences by group or department, approval route, allowances, organization-wide cap and visibility
- Values: add, rename and retire, with retired values kept on the recognitions that named them
- Approver roster by department and location, with duplicate scopes blocked and waiting items listed before anyone is removed
- Roles: grant HR admin from the directory after a check; the last administrator is protected
- Reported items: keep, change the wording or take off the wall, with a reply the reporter sees
- Theme & branding: inherit the SharePoint site theme, choose a preset or set your colours, checked live against WCAG 2.2 AA contrast
- Points and rewards: off by default; when on, points per type, an optional reward and a quarterly points budget
Illustrative screen with sample data.
Report
See whether recognition is reaching everyone
Reporting covers a manager’s reporting line, or the whole organization for HR. Filter by type, department, location, manager, person and dates, and group by type, value, department, location, recipient, sender, manager or month.
- Include or leave out archived items and leavers
- Private items are counted where the viewer can see them, and their messages stay out of reports
- Export CSV gives one row per recognition, without messages
- Indexed columns let you connect Power BI to the recognitions list if you want your own dashboards
Illustrative screen with sample data.
Records
Retention, leavers and an audit log
Archive & retention holds the rules for how long recognition stays on the wall, how long it’s kept, and what happens when someone leaves. Rules that delete or remove things are chosen first, then applied after one check.
- Recognition leaves the wall after a set window (12 months by default) and stays in reporting and people’s own lists
- Five rules for leavers, from keeping them on the wall as a former colleague to taking their name off and out of the wording
- Erase on request removes one person’s recognition for a data-subject request, with the reason and request reference in the audit log
- Laurel archives rather than deletes; deleting on a schedule uses a Microsoft Purview retention label
- The audit log records every configuration change, wording edit and approval decision, with who made it and what changed
Illustrative screen with sample data.
Notify
Updates in Laurel, and Teams or email if you want them
Laurel tells people everything under Updates: recognition they’ve been given, approvals waiting for them, and what happened to things they sent or reported. Four optional Power Automate flows add delivery and housekeeping.
- Notifications: Teams, email or both, as each person chooses in My settings
- Private items: locks private, waiting and declined recognition to the people involved in SharePoint itself
- Draft clean-up: reminds authors three days before an unfinished draft is cleared
- Weekly digest: emails each manager their team’s recognition from the past week
- All four use standard connectors, and each does nothing until it’s ticked in Laurel
Illustrative screen with sample data.
Where people use it
On your intranet, in Teams and on phones
- A page on your Laurel site, which can be added to Teams as a tab so people reach it through the Teams mobile app
- Recent recognition on any intranet page, with a Give recognition button
- Works on phones and desktops; on a small screen the menu folds behind a Menu button
- Get help is in the same place on every screen, with the recognition team’s contacts and the Help centre
A solution accelerator
Built for your organization, installed by iomer
Everything on this page is already built on SharePoint, Microsoft Entra ID and Power Automate. iomer sets up your organization’s Laurel as a single deployment package, with your recognition types, values, approvers, theme and retention rules, and installs it in your tenant.
See Laurel with awards like yours
Book a 30-minute walkthrough set up with awards and approval routes like yours, or take the evaluation kit away and come back when you’re ready.
