A CMMS that surfaces leadership health, without ever naming a name.
SMMS includes Leadership Pulse — recurring, two-question anonymous check-ins from frontline maintenance crews that roll up into leadership-health trends. Responses are never individually attributable: a structural anonymity-suppression gate withholds any cut of the data too small to protect identity.
How does SMMS keep pulse responses anonymous?
Every aggregate a leader can see flows through a single, structurally isolated suppression gate before it ever reaches a screen. The gate compares the number of unique respondents behind a cut — a team, a site, a department — against a minimum threshold (5 respondents by default; a tenant can raise it, but never lower it below a hard floor of 3). If a cut falls short, it is withheld entirely — not shown with a small, potentially identifying number.
A withheld cut and a cut with genuinely no responses yet render identically: there is nothing on screen to compare against, so a leader cannot infer a suppressed group's answer by noticing what's missing. The model has been through multiple internal adversarial review rounds, each round's fixes committed to the codebase rather than left as a recommendation — engineering diligence on a mechanism, not a customer testimonial.
Why measure leadership health in a maintenance system?
Frontline maintenance crews sit close to real operational pressure — backlog, downtime, safety incidents — and a CMMS is where that pressure is already logged. Leadership Pulse asks two short questions on a recurring cadence rather than adding a separate survey tool crews have to remember to open, so the signal comes from the same place the work already happens.
What leaders see, and what they never see
- Combined, aggregated trend lines for a category, site, department, or manager group — only once enough people have answered to protect anonymity.
- Participation rates (how many people answered), never who answered.
- A rolling health trend over time, with an arrow that only appears once both compared periods independently clear the anonymity threshold.
- Any individual response, ever — there is no admin override, no export, and no "just this once" exception.
- A count or score for a group too small to protect who is in it — that cut is withheld, and it looks identical to "no data yet," so a small group can never be inferred by comparison.
- Which specific employee gave which specific answer, even in raw form, even to a platform administrator.
Limitations
SMMS has no deployed customer sites yet, so every claim on this page is about what Leadership Pulse does today in the shipped codebase, not about adoption numbers or how well it works for a workforce of any particular size.
- Leadership Pulse is a short, recurring check-in by design (two questions per pulse by default, tenant-configurable from one to three) — it is not an open-ended survey-builder platform.
- Trend quality depends on participation clearing the anonymity threshold for a given group; a very small team may simply not generate a visible trend, by design, not as a bug.
- Leadership Pulse is an explicit-grant feature, not on by default for every tenant — a platform administrator has to turn it on deliberately.
Frequently asked questions
How does SMMS keep Leadership Pulse responses anonymous?
Every aggregate leaders can see is resolved by a single, structurally isolated suppression gate: any cut of the data — a team, a site, a department — that falls below a minimum-respondent threshold (5 by default, with a floor of 3 no tenant admin can lower it below) is withheld entirely rather than shown with a small number. A withheld cut and a "no data yet" cut look identical on screen, so leaders can never triangulate a small group's answer by comparing what is and isn't shown.
Is Leadership Pulse a full employee survey platform?
No — by design, it is a short, recurring check-in: two questions per pulse by default (a tenant can configure 1 to 3), not an open-ended survey builder. That constraint is deliberate: it keeps participation high and keeps the anonymity math tractable at small-team scale.
Is Leadership Pulse turned on by default?
No. Leadership Pulse is an explicit-grant feature — a platform administrator has to deliberately enable it for a tenant. It is never turned on as a side effect of a trial, a subscription tier, or any other bundling — collecting anonymous sentiment data from a workforce is treated as a decision a tenant makes on purpose, not a default.
Can employees opt out, or is participation mandatory?
Participation follows normal tenant role permissions — every role that can respond can also decline to answer a given pulse (an "N/A" response is excluded from scoring but still counts toward participation, so declining doesn't itself reduce anonymity for others). Whether pulses are optional or expected for a given workforce is a tenant policy decision, not something this page states either way.
Who can see Leadership Pulse analytics?
Analytics access is permission-gated, not open to every logged-in user: tenant admins and managers can view aggregated trend analytics; full administrative configuration (thresholds, question rotation) is restricted further, to tenant and functional admins. Every employee can respond regardless of role — responding and viewing analytics are separate, separately-gated capabilities.
See how a leadership signal looks without a single name attached.
Request a demo and we'll walk through the anonymity model, the suppression gate, and what a real trend view looks like — or take the free RMI QuickScan first to see where your program stands today.