Ten years after the case, an investigative reporter contacted her.
“I’m working on vehicle database auditing.”
She almost declined.
Then the reporter said:
“The automated alerts created after your case were disabled three years ago.”
The former agent sat straighter.
“Why?”
“Department says too many false positives.”
“What replaced them?”
“Supervisor spot checks.”
“How frequent?”
“Unclear.”
“Who authorized change?”
“Trying to find out.”
The former agent felt an old sensation.
Not adrenaline exactly.
Pattern recognition.
Systems drift.
Reforms are often strongest immediately after scandal.
Then memory fades.
Staff turns over.
The painful event becomes somebody else’s history.
Controls feel inconvenient.
Alerts become noise.
Exceptions accumulate.
Eventually the safeguard exists only in a training slide.
She asked:
“Any evidence of current abuse?”
“Two officers disciplined for unauthorized plate queries last year.”
Her jaw tightened.
“Connected to theft?”
“No evidence.”
“Personal lookups.”
“One ex-partner.”
“One neighbor dispute.”
Different misconduct.
Same access problem.
The reporter asked:
“Will you comment?”
The former agent thought.
“Yes.”
This time she did.
Not because her story mattered.
Because the policy did.
She reviewed documents.
The original post-case reform required automated audit flags for high-volume queries, off-duty access, repeat queries on the same plate without case association, and plate searches preceding dispatch events.
Exactly the pattern that had caught the corrupt officer.
Three years earlier, the department migrated software vendors.
The new system produced too many alerts because integration with dispatch records was poor.
Instead of fixing integration, administrators reduced alert categories.
Then disabled two entirely.
No corruption required.
Budget.
Workload.
Technical frustration.
Ordinary erosion.
The former agent told the reporter:
“Controls fail when people remember the inconvenience longer than the reason the control exists.”
That line spread.
She hated that people loved lines.
But the article worked.
The police department reopened audit review.
City council held hearings.
The former agent testified remotely.
A council member asked:
“Are you suggesting the department intentionally weakened accountability?”
“No.”
“Then what happened?”
“They optimized for workload.”
“Is that wrong?”
“Not automatically.”
“Every control has cost.”
“But if you reduce a control, you should explicitly document what risk you are accepting.”
The council member frowned.
“Meaning?”
“If an alert catches one serious misuse per ten thousand legitimate queries, you may decide it creates too much review burden.”
“That is a policy choice.”
“But say it honestly.”
“Do not call the risk gone because you stopped measuring it.”
The room quieted.
The department restored redesigned automated auditing with better dispatch integration.
Not because of her alone.
Technical staff built it.
Supervisors negotiated workflow.
Union representatives raised privacy concerns.
Civilian oversight reviewed.
The reporter kept pressure.
The former agent was one input.
She liked that.