Most people can name the moment a human turned them down. Far fewer can name the moment software did — and that's the point. Automated decision systems are now embedded in hiring, housing, lending, insurance, and healthcare, and they are typically invisible by design: no notification, no explanation, no obvious place to object. You just get a rejection that reads like a form letter, because it is one. The good news, and the reason this article exists, is that the paper trail you're entitled to is stronger than most people realize — and the systems are built on the assumption that you'll never ask for it.
Where These Systems Actually Sit
This isn't a forecast. Each of the following is in production right now, at scale, in ordinary consumer life:
- Hiring. Applicant tracking and screening tools rank and filter candidates before any person reads a résumé. In the ongoing Mobley v. Workday litigation, a federal court conditionally certified a nationwide class of older workers, noting that the platform's screening may have touched more than a billion applications [3].
- Housing. Tenant screening scores decide who gets shown an apartment. SafeRent settled for $2.3 million over an algorithm that allegedly scored Black and Hispanic applicants and housing-voucher holders lower — partly because it leaned on credit data while ignoring that a voucher guarantees much of the rent [2].
- Health coverage. The suit over UnitedHealth's nH Predict tool alleges it estimated how long patients "should" need post-acute care, and that coverage was cut on that estimate rather than the treating physician's judgment [1].
- Credit and insurance. Scoring models set approvals and prices, increasingly using behavioral inputs well beyond payment history.
- Government services. Eligibility, fraud flags, and benefits determinations increasingly run through risk models first.
The Design Assumption: You Won't Appeal
The single most revealing number in any of this is 0.2%. That's the share of denied claims the UnitedHealth complaint says were appealed — and the same filing alleges roughly nine in ten denials that were challenged got overturned on appeal or before a judge [1]. Read those two figures together and a business model appears: a tool can be wrong most of the time and still work perfectly, provided almost nobody pushes back.
That asymmetry is the actual subject of this article. These systems aren't primarily dangerous because they're biased, though some demonstrably are. They're dangerous because they're quiet, and quiet decisions don't get contested. Every rejection that arrives with no explanation is betting on your exhaustion.
A system can be wrong nine times out of ten and still function — as long as almost nobody appeals.
— The economics of automated denialThe Rights You Actually Have
Here's where it gets more useful than most coverage admits. You have real, specific entitlements — they're just rarely advertised.
If you're denied credit, insurance, housing, or employment based on a consumer report, federal law entitles you to an adverse action notice: what was decided, which reporting agency supplied the data, and your right to a free copy of that report plus the ability to dispute errors in it. This applies whether a person or a model made the call. Most people bin the letter. It's the thread to pull.
Colorado's AI Act (SB 24-205), the first comprehensive state AI law, covers "consequential decisions" across education, employment, lending, government services, healthcare, housing, insurance, and legal services — requiring disclosure, impact assessments, and an appeal path. Enforcement was pushed to June 30, 2026, with a cure period into 2027 [5]. NYC's Local Law 144 requires annual independent bias audits, published publicly, for automated hiring tools, at $500–$1,500 per day in penalties — and a December 2025 Comptroller audit found enforcement had been weak, which is exactly why employers are being warned to expect a stricter phase [4].
Article 22 gives you the right not to be subject to decisions based solely on automated processing where they significantly affect you, plus rights to an explanation, to contest, and to human intervention. Critically, the SCHUFA ruling closed the obvious loophole: a rubber-stamp signature doesn't count. A human who lacks genuine authority or capacity to reach a different conclusion doesn't make a decision non-automated [6].
What to Actually Do
If a decision goes against you and you suspect software drove it, this sequence costs a stamp and puts everything in writing:
- Ask, in writing, whether an automated system was used. One sentence. The written record matters more than the answer, and vague replies are themselves informative.
- Request the specific reasons and the data used. Not "you didn't meet our criteria" — which criteria, and which data points about you.
- Get the underlying report and check it. Screening files carry mismatched names, stale addresses, and other people's records with startling regularity.
- Explicitly request human review. Use those words. In the EU/UK it's a legal right; in the US it increasingly triggers an internal process that exists mainly because regulators asked for it.
- Appeal even when it feels pointless. The 0.2% figure is the whole ballgame. Appeals are where these systems' error rates become visible.
- Escalate to a regulator. CFPB for credit, HUD for housing, EEOC for employment, your state insurance commissioner, or the relevant data protection authority in Europe.
"You did not meet our minimum requirements." · "Based on information in your consumer report." · "Our system was unable to approve." · "Coverage is no longer medically necessary." — Vague, instant, and unattributed decisions are the signature. A denial that arrives within seconds of an application had no human in it, whatever the letterhead implies.
None of this argues that automated decisions are inherently wrong. Reviewing thousands of applications consistently is a genuine use for software. The problem is a system that decides quietly, explains nothing, and depends on you not asking — because that combination converts an ordinary error rate into a permanent outcome for real people.
So treat the unexplained rejection as unfinished rather than final. Ask whether a machine decided. Ask what it used. Ask for a person. It's a handful of sentences, and it's the one move these systems are not designed to absorb.
I've made the fuller argument about why I still want this technology in my life — on very different terms — in Citizen 11574.