AI for Business | By Christopher Ross (https://thisismyurl.com) The filter you can’t explain ============================== 915 words | July 7, 2026 --- Marcus runs a family restaurant. Forty-five seats, three full-time staff, a few seasonal hires when summer fills the patio. When his lunch server gave notice in May, he posted the job and thirty-eight applications came back within a week. That was more than he expected, and more than he had time to read carefully between prep and the dinner rush. So he paid for a month of an AI screening tool. The pitch was simple: feed it the applications, it reads them faster than you can, and it hands you back the strongest candidates. He let it run on the settings it came with, the way most of us install an app and tap “accept” without changing anything. It gave him a ranked list of eight people. He called those eight, interviewed four, and hired one. Start to finish, the whole thing took a fraction of the usual time. He was pleased with it. A few weeks later he was at a community fundraiser and a woman he knew socially came over. She’d applied for the job. She wanted to know, friendly but direct, why she’d never gotten a call. Marcus told her the truth: the first cut had been automated. He said it the way you’d explain that the bank closed early, like it was just how things worked now. On the drive home it started to bother him. He pulled over, opened the screened-out pile on his phone, and looked at her application. Then he looked at a few others the tool had ranked low. He couldn’t tell why. The tool had given everyone a score, but it hadn’t given him a single reason. If someone had sat him down and asked him to explain, in writing, why this woman had been ranked below the people he interviewed, he couldn’t have done it. He hadn’t made that decision. The tool had, and he’d signed his name to it. The problem isn’t speed. It’s the missing reason. Here’s the thing worth understanding. A screening tool that sorts people faster is genuinely useful. The trouble starts when it sorts them for reasons it won’t show you. A score is not a reason. “The system ranked her eighth” tells you where she landed, not why, and “why” is the part you’re on the hook for. In hiring, you’re expected to be able to account for your decisions. Not in a courtroom-drama sense, just in the ordinary sense that if a candidate, or eventually someone official, asks why one person got a call and another didn’t, you should have an answer that holds up. “More relevant experience.” “Available for the shifts I needed.” “Already done the job somewhere similar.” Those are answers. “The algorithm scored them lower” is not an answer. It’s the absence of one, dressed up to look like a process. Marcus didn’t do anything reckless. He trusted the default settings because that’s what defaults are supposed to mean: the sensible choice, picked by people who know the tool better than you do. For a calendar app or a spell-checker, that instinct is fine. The cost of a wrong default is a misspelled word. In hiring, the default settings were quietly making judgment calls he’d never have made out loud, and he had no way of seeing them until someone he knew asked a fair question he couldn’t answer. Two rules before you let a tool sort people The fix isn’t to throw the tool out. It’s to use it only for the parts of the job you could have done by hand and explained afterward. First, let it filter only on things you set yourself, in plain terms. Years of relevant experience. Available for the shifts you actually need covered. Has worked a similar role before. These are facts you can point to and defend in one sentence. Many of these tools also offer to rank candidates by “fit” or “potential,” scoring people against criteria the tool decides for itself. Turn that off. If you can’t say in a sentence what “fit” means, you can’t stand behind a decision based on it, and you’d be standing behind it whether you understood it or not. Second, before you call your shortlist final, spend ten minutes checking the rejections. Pull two or three applications the tool ranked low and read them yourself. For each one, see if you can finish the sentence: “I’m passing on this person because ______.” If the reason makes sense to you, fine, that’s a decision you made. If you can’t fill in the blank, put that person back in the pile and read them properly. The whole spot-check adds maybe thirty minutes to a hire. What those thirty minutes buy you is the difference between a decision you made and a decision that was made for you while your name was on it. That’s the line. The tool can carry the reading. It can’t carry the responsibility, and the responsibility was never the part that was slow. Marcus kept the tool. He turned off the “fit” scoring the same night, and now he reads a handful of the no’s before he finalizes anyone. The woman from the fundraiser didn’t get the job the second time around either. He told her so himself, on the phone, and he had a reason. ======================================================================== ATTRIBUTION CODE FOR WEB PUBLISHERS ======================================================================== If you are publishing this column on your website, the code block below helps search engines correctly link this content to Christopher Ross. It is optional but recommended. HOW TO ADD IT IN WORDPRESS -------------------------- 1. In your WordPress dashboard, go to Plugins > Add New and install the free plugin "WPCode" (search for that name). 2. Once installed, go to Code Snippets in your dashboard menu. 3. Click "Add New Snippet" and choose "HTML Snippet." 4. Give it a name like "Christopher Ross byline - AI for Business" 5. Copy everything between the === markers below and paste it into the Code box. 6. Set the Location to "Site Wide Header" and click Save & Activate. If you do not use WordPress or need help, forward this file to your web developer. It takes about two minutes to add. === COPY EVERYTHING BETWEEN THESE LINES === === END COPY ===