The Lemon Score is a demerit engine. Bad behaviour adds points by how bad it was. Good behaviour — and plain old time — takes them back off. Here's exactly how the number moves.
You're the hirer. Dial in what a candidate has on record — and how many separate employers logged each thing. Two agencies flagging the same trait is where it turns sour, fast.
The maths, in the open: each incident scores base × m(n), where n is the number of independent employers who logged it and the corroboration multiplier is m(n) = 0.25n² + 0.75n — one report counts ×1, two ×2.5, three ×4.5. Points sum, ripening offsets subtract. The reference band is 0–1000, but a peachy candidate can run negative (a 5-star hire) and a thoroughly rotten one can blow past 1000 — both are deliberate, for illustration.
Uploads aren't free text and they aren't vibes. Each one maps to a fixed incident type with a fixed point value — heavier for the things that actually torch a client contract.
A starter set — the full 50-incident simulator covers the whole catalogue, grouped by category. A comprehensive, evidence-backed upload (3 tokens) lands the heaviest weighting.
When a second — or third — employer logs the same trait on the same person, the points don't just add. They multiply, on a quadratic curve. A repeated lemon gets sour fast.
A corroborated lemon is a real lemon. Independent agencies seeing the same behaviour is the strongest signal the platform has — so the score treats it that way.
Illustrative. Pucker-up territory after three.
The score isn't a life sentence. Stay clean and it decays on its own. Put in real effort and it drops faster.
Same person, 18 months later. Score 720 → 180. That's the platform working.
Sour to peach — the whole point of a score that decays.
Frivolous uploads would poison the well. So every record runs a contest window before it counts — and the employer pays to file it, which keeps the trigger-happy ones honest.
A structured incident report, evidence attached, against a paid token. Money on the line means no idle grudges. The record is queued, not yet visible.
An OTP-verified alert goes to the worker. They have the contest window to accept it, or push back with their side of the story.
No response, no dispute — the record publishes and the points land on the Lemon Score.
The worker can reach the ex-employer to resolve it. A quality, corroborated rebuttal mitigates the score. A flimsy one doesn't.
Pilot operators get a walkthrough of the engine, the incident catalogue and the contest flow.