The alert problem began after a vendor updated the department's reporting platform. Field-interview entries were now stored in one category, citizen complaints in another, and personnel data in a third. The early-warning dashboard drew information from each, but one mapping rule had stopped matching officer identification numbers. The software displayed a cheerful green status indicator because the server itself was functioning. Priya found the problem while comparing manual counts with the dashboard's monthly summary. The counts were not close, and she was stubborn enough to ask why.
Her first email went to information technology and her supervisor. A second followed when no one answered. She attached examples with private identifiers removed and asked whether the dashboard should be considered unreliable until the mapping was repaired. The response thanked her for being thorough and said a vendor representative would review it after the next scheduled maintenance window. Priya wrote back that the problem affected supervisory review, not merely a cosmetic display. Nobody acknowledged that distinction in writing.
She could have left it there. She was not a sworn officer and had no authority to discipline anybody. Instead she printed a list of alerts that her manual calculations indicated might deserve review and put it in a folder marked PENDING VERIFICATION. She did not circulate names beyond the authorized supervisors. She knew a false positive could damage a person's reputation as surely as a missing alert could conceal a problem. For six months the folder grew while other tasks took priority.
When Kessler's arrest of Edward became public, Priya recognized the officer number from her spreadsheet. Her stomach tightened before she opened the file. She found several field contacts involving people who said they worked in or were visiting higher-income neighborhoods. She also found complaints that had been closed without sustained findings. Neither pattern was conclusive alone, and she resisted the urge to turn her calculations into an accusation. What made her angry was not certainty about his motives. It was knowing someone should have examined the data earlier and had not.
The independent reviewer asked Priya to explain the software failure in plain language. She drew three boxes on a whiteboard to represent field contacts, complaints, and employee records. Then she drew the missing connection. "The information was there," she said. "The automatic summary wasn't carrying it to the people who needed to review it." The investigator asked whether supervisors could have accessed the underlying records manually. Priya said yes, and showed him how. That answer complicated the idea that a single computer error had caused everything. A tool had failed, but people had also decided not to use the available alternative.
Captain Shaw sat through the briefing without interrupting. Afterward she asked for a list of every supervisor who had received Priya's notices. Priya gave her the documents, including one email Shaw herself had been copied on during a week of staffing emergencies. Shaw read it carefully. She remembered approving overtime during that week and ignoring several messages about technology maintenance because every message seemed urgent. The realization was unpleasant. She had not ordered anybody to disregard complaints. She had allowed an important warning to disappear into the ordinary noise of a busy office.