ReviewDesk
← Back

ReviewDesk guide · By the Ingenious AI team · Published 14 November 2026 · Reviewed 14 November 2026

Do you have to tell employees when monitoring or productivity software scores them?

Generate a free adverse-outcome letter — no sign-up Build a free pre-use notice See pricing

The short answer. If software scores your existing workforce in ways that affect shifts, discipline, promotion or continued employment, employees are affected persons — and the employment notice pattern from Illinois, with Colorado and California behind it, points one way: tell them what runs, what it weighs, and how to challenge what it gets wrong. Secret scoring is the one configuration no regime in this fleet tolerates, and the one most corrosive to trust when — not if — it surfaces.

What is employee-monitoring notice duties?

Employee-monitoring ADMT covers workplace systems that score, rank or flag existing employees with material consequences: productivity scoring feeding discipline, algorithmic shift and task allocation, performance analytics informing promotion or termination, and automated monitoring outputs used as evidence. The regimes ReviewDesk tracks address employment decisions; Illinois HB 3773 names recruitment, hiring and promotion expressly, and the notice logic extends naturally to in-workforce scoring that shapes an employee's livelihood.

Why does in-workforce scoring deserve its own guide?

Because employers who handle applicant notices well routinely miss the workforce case, although the stakes run higher: an applicant loses an opportunity; an employee scored wrongly can lose shifts, standing or the job itself. The data is also different — continuous, behavioural, generated inside the employment relationship — which makes errors harder for the employee to detect and dispute. An employee cannot correct a productivity record they have never seen, produced by rules they were never told. Notice is what converts monitoring from surveillance into a system an employee can engage with.

There is a candour point for leadership: if a scoring system's rules cannot be told to the workforce, the rules — not the telling — are the liability. The notice exercise forces the question early, while the system can still be redesigned, rather than in a dispute, when the only question left is why nobody asked it sooner.

What should employees be told, concretely?

That the system exists, what it measures, what its outputs influence — allocation, review conversations, formal processes — and what they do not influence. The factor description matters as much as the headline: 'activity levels' could mean keystrokes, tickets closed, calls handled or locations visited, and employees deserve to know which. State the human architecture: who sees scores, who can act on them, and the rule — if it is your rule — that no formal consequence follows from a score alone without a person's review. Then the routes: how to see one's own record, how to correct it, how to ask for review.

Deliver it as workforce communication, not as a policy PDF: team briefings, the handbook, the systems employees already open daily, with a hosted notice page as the canonical version — the pattern of the hosted-notice guide. Illinois-facing employers will recognise the employment-notice shape from the HB 3773 guide; the workforce notice is its in-employment sibling.

Where is the scope line for workplace tools?

Measure influence, per the scope test. A rota tool proposing shifts that managers rearrange freely is light-touch. The same tool's reliability score silently governing who gets premium shifts is a livelihood decision. A quality dashboard managers glance at differs from the dashboard whose bottom decile is auto-enrolled in a performance process. The worksheet determination should be filed per workforce system, with acceptance and override measurements — and re-run when a system's outputs gain new consumers inside the business, because scope creep in monitoring is the norm, not the exception.

Discipline is the bright line. The moment a score is cited in a formal process — a warning, a capability procedure, a dismissal rationale — the system that produced it is part of a consequential decision about that employee, and the notice, record and review expectations apply to that use with full force, whatever the system's original purpose was. Purpose drift is how monitoring tools become evidence by accident.

How do correction and review work for employees?

Correction first, as everywhere: shift records misattributed, system downtime scored as inactivity, cases credited to the wrong handler. Give employees a route to see and challenge their own records that does not begin with their line manager — some records are wrong because of the line manager's own entries — and verify fast, because allocation consequences compound weekly. Review proper, for challenged consequences, belongs to a person outside the original chain, with the full record and authority to remove the score's effect, following the review checklist.

Record outcomes in the docket, not in email. An employee's challenge and its resolution are exactly the records a later dispute will reconstruct from fragments if the desk does not hold them whole. The three-year trail from the records guide protects the employer who handled the challenge properly as much as it protects the employee who raised it.

What do the numbers usually reveal?

That scores measure the measurable, and the gap between the measurable and the valuable is where your best people quietly live. Run the review and correction data quarterly: which factors generate successful challenges, which teams' scores move when staffing changes rather than when effort changes, where the tool punishes the people doing unmeasured work — mentoring, complex cases, the glue tasks. Most organisations find their scoring is a decent measure of a narrower job than the one they actually employ people to do. The finding is valuable precisely because the notice-and-review machinery surfaced it with evidence.

Publish the aggregate learning back to the workforce. A short annual account — what the systems measured, what challenges changed, what was redesigned — converts the notice from a legal artefact into a standing demonstration that the system is supervised. Trust follows demonstrated supervision more reliably than it follows assurances.

How should an employer start, if nothing is disclosed today?

Inventory, then tell, then wire the routes — in that order, quickly. List every workforce system producing scores, rankings or flags with consequences, however informal. Draft the notice from the worst case — the system with the most direct line to a livelihood consequence. Publish it with briefings, not a silent upload. Open the correction and review route on the same day, staffed — a notice that invites challenges into an unstaffed inbox re-creates the original problem in a new shape.

ReviewDesk's employment workflows carry the same machinery as applicant screening: the workflow for the allocation or performance decision, the hosted notice, the inbox, the audit trail. Start free with the single most consequential system, run one quarter of real challenges through it, and extend per system from evidence rather than from a rollout plan. The workforce will judge the programme by the first challenge it handles; make sure that challenge lands in a system that works.

Your five actions for employee-monitoring notice duties

  1. Inventory every workforce system producing scores, rankings or flags with consequences — including informal ones.
  2. Tell employees what runs, what it weighs, what its outputs influence and what they never decide alone.
  3. Give employees a correction and review route that does not start with their own line manager.
  4. File scope determinations per system and re-run them when a system's outputs gain new internal consumers.
  5. Report the aggregate learning back to the workforce annually — challenges, changes, redesigns.

Worked example: the downtime scored as idleness

A fictional logistics firm — Meridian Freight — allocates premium shifts partly on a reliability score drawn from its depot systems. After publishing its workforce notice and opening the review route, a driver's challenge arrives within the first month: his score shows three low-activity afternoons. The full record shows those afternoons coincide with a documented system outage and a vehicle defect — he was present, working, and unscored by a system that could only see its own silence. The correction is appended, his allocation position restores, and the scoring rule gains an outage exclusion pulled from the incident log automatically.

The quarterly review finds the same signature — scores dipping on outage days — across forty-one drivers, none of whom had previously had any way to connect their shift losses to a system they did not know existed. The fix costs a rule change. Without the notice, the pattern would have run for years, priced as a mystery about driver quality. With it, one employee's three afternoons became a fleet-wide correction — the strongest argument for telling the workforce what runs.

Frequently asked questions

Must employees be told about monitoring scores?

Where software materially influences decisions about employees — allocation, discipline, promotion, continued employment — the employment notice pattern in the regimes ReviewDesk tracks points to disclosure: what runs, what it weighs, and how to challenge it. Illinois names recruitment, hiring and promotion expressly.

What if the score is only 'one input' for managers?

Measure it. If scores usually determine who gets premium shifts or who enters a performance process, they materially influence consequential decisions, and the scope worksheet should record that honestly.

Who should handle an employee's challenge?

Correction and review should be reachable without starting at the employee's line manager, and review belongs to a person outside the original chain with authority to remove the score's effect.

What records should be kept?

The notice version, the employee's record as scored, challenges, corrections, reviews and outcomes on one timestamped trail — ReviewDesk's model keeps decision files for three years.

Is this guide legal advice?

No. ReviewDesk is templates and workflow tooling, not legal advice. Duties are summarised from the regimes in our research; consult counsel and your employment advisers for your situation.

Keep reading: How can a tenant applicant request human review of an automated screening decision? · How should a human-review inbox be designed so no request is missed? · How do SLA clocks keep human reviews inside their deadlines? · What should happen when a human-review request goes overdue? · How does an applicant status link change the experience of waiting for a review? · All ReviewDesk guides · ReviewDesk home · Try the free desk · Free letter generator · Free notice builder · Pricing

ReviewDesk is built by Ingenious AI. Templates and workflow tools — not legal advice.