Getting started
From thanks in a chat to a program people use
Laurel is a solution accelerator. The foundation is already built, so iomer builds your organization’s version, installs it in your tenant and pilots it with you. Most of your effort goes into deciding your awards, approvers and privacy rules, and who owns the program.
Go live in five steps
Five steps, in order
-
Step 1
Plan
We map your program with you: the awards and thank-yous you want, your values, who approves what, your privacy, retention and leaver rules, and the state of your manager data in Entra ID.
From you: your current awards and nomination forms, your values, and someone from HR, privacy and IT for a workshop.
-
Step 2
Build
We build Laurel for your organization as a single deployment package: your recognition types and badges, audiences and allowances, approval routes and roster, theme, and archive, retention and leaver rules.
From you: decisions on types, routes and privacy, and the names for your approver roster.
-
Step 3
Install
We add the package to your app catalog, take your SharePoint administrator through the two Graph approvals, run the guided setup with a site owner, apply the permission design and install the flows you want. There’s nothing for your IT team to assemble.
From you: a SharePoint administrator for the approvals, a site owner, and a service account if you want the flows.
-
Step 4
Pilot
We start with one team or location, watch how recognition flows, and adjust types, allowances and routes before rollout.
From you: a team or site to pilot with, and feedback from its managers.
-
Step 5
Launch
Launch communications, training for your HR admins, a Teams tab and recent recognition on your intranet home page. As your needs change, we build and install a new version of your package.
From you: a program owner who will run Laurel day to day.
Everyone on board
Bring your HR or people lead, internal communications, a manager, someone from IT and someone from privacy into the conversation before the proposal. Laurel touches all of them.
Who’s involved
Bringing your program across
Start from what you already have
Your existing awards become recognition types with their own routes, your values go into the console, and the people who approve awards today go onto the approver roster. If your program runs on another platform, we plan the move with you.
We scope this with you, so you can see the effort before you commit.
What sets the size of the job
- How many recognition types and approval routes you need
- Whether routes follow the manager chain or a roster of named approvers
- How much your Entra ID data needs tidying
- Several business units or brands, and frontline rollout support
- How much help you want designing the program itself
Before we talk
Questions to think about
You don’t need answers to all of these for a first conversation. They’re what tells us how Laurel fits, who else should be involved, and how big the job is.
How do people thank each other at work today?
Email, Teams praise, a spreadsheet or a vendor platform. Each points to what matters most: visibility, fairness, cost or where the data lives.
Do you run formal awards, such as values or safety awards?
These become recognition types with approval routes. More types mean a bigger design phase.
Who approves recognition now, and does it always follow the reporting line?
If safety leads or an HR panel approve some awards, the approver roster handles it.
Do you want points or rewards, or is recognition on its own enough?
Both are optional and off by default. Laurel records rewards; it doesn’t provide a catalogue or payroll link.
How many staff, and how many are frontline or without a desk?
Sizes the job, and tells us whether a Teams tab and phone access matter most.
Where is your Microsoft 365 data held, and does data location matter to you?
Laurel’s records stay wherever your SharePoint content already lives.
How reliable is your manager and department data in Entra ID?
Approval routes, My team and reporting depend on it. Gaps mean a clean-up task before go-live.
Who will own the program day to day?
Laurel needs an internal owner, usually in HR or internal communications.
What do you want to report on, and to whom?
Participation, fairness by site or team, or values. It shapes the reporting design and your launch measures.
How should recognition be handled when someone leaves?
Opens the privacy and retention conversation early. Bring in your privacy or records staff.
Are some recognitions likely to be sensitive?
Personal circumstances or health. The privacy choices and the search setting are decided in design.
Are you using Journey or another iomer accelerator today?
You already have the site design, the skills and the governance model, and Journey and Laurel share the same Entra ID clean-up.
Why a solution accelerator
The benefits of off-the-shelf and custom, without the trade-offs
No two organizations are the same, but every recognition program needs the same foundation. Laurel gives you that foundation already built, and builds the rest around you.
| Recognition platform | Custom build | Laurel solution accelerator | |
|---|---|---|---|
| Fits how you work | You adapt to it | Built around you | Your types, routes and rules are built for you |
| Designed before you start | Yes | No, designed as it’s built | Yes, the foundation is already built |
| Time to go live | Fast to start, slow to fit | Slow, everything is built from scratch | Faster, because only your parts are built |
| Where people use it | Another site and sign-in, or an app inside Teams | Wherever it’s built | Your intranet and Teams, with the sign-in people already use |
| Who sets it up | Your team | Your developers or a partner | iomer, as one deployment package |
| Where records live | The vendor’s cloud | Wherever it’s built | Your own Microsoft 365 tenant |
| Rewards | Often a full catalogue | Whatever you build | Optional points and rewards, recorded; you provide the reward |
| Cost | A subscription, usually per user | An open-ended project | Scoped with you first, then a work estimate and proposal |
| Changes later | Wait for the vendor’s roadmap | Another project | A new version of your package, built and installed by iomer |
Already using Praise in Teams? Keep it. Praise is a good quick thank-you between two people; Laurel is for when recognition needs to be a program, with types that mean something, approvals and reporting HR can act on. Many organizations use both.
Pricing
Scoped with you first, then a work estimate and proposal
Every Laurel engagement starts by working through your program with you: the recognition types and approval routes you need, and how much help you want with launch. Then we give you a work estimate and a written proposal for building, installing and piloting, so you can see the effort before you commit.
What the estimate depends on
- How many recognition types and approval routes you need
- Whether you want the Power Automate flows and a Teams tab
- How many business units, brands or sites are involved
- How much help you want with launch and program design
Laurel runs on the Microsoft 365 licences you already have, with no extra Microsoft licences needed. Already running Journey? Laurel can share the same SharePoint site design, Entra ID clean-up and governance model.
What happens next
From first call to proposal
Watch the 50-second tour first Download the datasheet (PDF, 2 pages)
- Discovery call
We learn how recognition works today and what matters most.
- Tailored walkthrough
Thirty minutes with Laurel, set up with recognition types like yours.
- Scoping workshop
Your types and routes, your data and your privacy rules. It produces your program design and a work estimate.
- Proposal
A written proposal with the work estimate and timeline.
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.
