MeroScore is designed to be fair and flexible. Here’s how it behaves when certain features aren’t in place.
No traffic sensors
Traffic Responsiveness pillar: Hidden / inactive
Score impact:
The Traffic pillar (weight 2) is removed from the calculation.
Your MeroScore is based only on other active pillars.
What you’re missing
Data-driven insights about whether you’re cleaning before/after busy times.
Recommendations like “Clean Restroom A more often during the morning rush.”
You can still manage traffic via experience and feedback; the score just won’t measure it.
No consumables sensors
Consumables Management pillar: Hidden / inactive
Score impact:
Its weight (1) is removed.
Your MeroScore relies on the remaining pillars.
What you’re missing
Automatic tracking of how quickly you refill empty dispensers.
Alerts based on live levels rather than manual checks.
Your team should ensure they have good manual refill routines. Mero won’t penalize you for not having sensors, but you won’t get those insights either.
Not using Mero work orders
Work Order Performance pillar: Hidden / inactive
Score impact:
Its weight (4) is removed.
Your MeroScore reflects just cleaning, traffic (if available), supplies (if available) and platform usage.
What you’re missing
Visibility into:
How long issues stay open
How often things get fixed right the first time
Patterns of recurring problems
To enable this pillar, start logging maintenance issues as Mero work orders. Once you do, MeroScore will automatically include the Work Order pillar and its KPIs.
Limited or incomplete scope of work
If many locations have no cleaning tasks assigned, you’ll see:
A lower Platform Usage score, particularly in Scope of Work Coverage
Often a Top Improvement Opportunity like:
“Assign cleaning tasks to unmanaged locations.”
How to fix
Review your locations list.
Assign an appropriate set of tasks (and frequency) to each area you care about.
Aim for 90%+ coverage (some spaces can legitimately be excluded).
This not only improves your score, it ensures your cleaning program is actually complete.
No beacons / base stations
If you don’t use cleaner beacons and base stations:
MeroScore still works based on task completions, work orders, and sensors.
Platform Usage may show lower scores for device-related KPIs like “Fix Offline Devices” or similar.
You’ll be missing:
Detailed cleaner-level tracking (“who cleaned where, when”)
Some granular analytics around time spent per area
But you can still get strong value from MeroScore if your tasks, sensors and work orders are set up well.
Minimal setup: the bare minimum
You can start with something very simple:
A set of cleaning tasks for at least one location
Cleaners marking tasks completed in Mero
Your Mero account configured
With that:
MeroScore will mainly use Scope of Work and Platform Usage.
The score might be volatile at first (few tasks → each miss has big impact).
As you add more locations and features, the score stabilizes and becomes more representative.
Growing into MeroScore over time
A good rollout path:
Start with Scope of Work
Define tasks & frequencies.
Get your team used to completing them in Mero.
Watch the Scope of Work & Platform Usage pillars.
Add Work Orders
Move maintenance requests into Mero.
Start tracking resolution speed and quality.
Watch the Work Order pillar appear and adjust operations accordingly.
Add Traffic Sensors (where valuable)
Instrument high-traffic areas.
Use Traffic Responsiveness to optimize timing.
Let Mero highlight time-of-day problems.
Add Supply Sensors (for critical restrooms)
Ensure high-profile restrooms and key areas never run out of soap or towels.
Monitor Consumables Management scores to prove consistency.
At each step, MeroScore:
Adapts to include the new pillar.
Uses the Activity Log and Top Improvement Opportunities to show you exactly how changes affect your score.
Helps you prioritize what to fix next.