A 4.2-star officer and a 4.6-star officer look like they're telling you something. Mostly, they aren't. A single average hides what went right, what went wrong, and whether the number is even based on enough shifts to mean anything.
One number, too many questions
Think about what a three-star review of a security officer could mean. They arrived late. Or they were on time but unfriendly. Or the client was unhappy about something that was never the officer's job. Or the site had no briefing and the officer did their best with nothing. All four collapse into the same three stars, and the next provider can't tell them apart.
The number looks precise and says very little.
It punishes the wrong people
Averages are fragile when there are only a few ratings behind them. An officer early in their time on a platform can be dragged down by one bad review from one difficult site, and a lower score means fewer shifts, which means fewer chances to recover. The fairest officers can end up looking worst simply because they're new.
Two things help. Scores should say how many ratings they're based on, so a thin sample reads as thin. And a score shouldn't be the only thing used to decide whether someone keeps working. A rating alone shouldn't quietly end anyone's work without a person reviewing it.
Break it into things you can act on
Instead of one number, rate the parts that actually matter, separately. For an officer, that's things like reliability, attendance and how they handled the site. And crucially, use what can be measured from the shift itself where you can. Whether an officer arrived on time and completed their patrols is recorded fact, not opinion, and it shouldn't have to compete with how pleasant someone found them.
Trust has to run both ways
Most platforms rate the worker and never ask the worker anything. But an officer knows things about a site that nobody else is recording: whether the post was safe, whether there was a proper briefing, whether the shift matched what was advertised, how they were treated, and whether they were paid on time.
That information protects the next officer who gets sent there. And it gives good providers credit for doing things properly. Clear briefings and reliable payment are exactly what should make a provider's shifts the ones good officers want.
Keep safety out of the star rating
This is the one we feel most strongly about. A serious safety or conduct problem should never be reduced to a one-star review sitting alongside complaints about the coffee. It needs to go somewhere private, with a severity level, where it's handled as a safety matter.
Mixing the two causes harm in both directions. Real safety concerns get diluted into a number and ignored. And people become reluctant to report a genuine problem when doing so publicly might invite retaliation.
What this looks like on Guardlane
Officers rate sites on safety and conditions, briefing quality, shift accuracy, respect and conduct, and payment reliability, each kept separate. Providers see officer reliability and attendance built from logged shift evidence. And safety or conduct concerns go through a private report that never appears as a public rating.
None of this makes feedback perfect. It makes it more honest about what it's measuring.