They Arrested Him for Driving a $410,000 Car — Then Learned He Designed It.

Chapter 32

Theme:
Font Size:
24px

“There is a preliminary recommendation for additional review of Dunley's conduct, including whether his stated reasons were sufficiently supported by the information available at the time.”

Marcus nodded.

“And Miller?”

“The report recognizes that he attempted to verify the registration but did not adequately pursue his concerns when the detention continued.”

Marcus looked through the window of his office.

He thought about the younger officer's face when the documents finally matched the system record.

Miller had not been the person who placed the handcuffs on him. But he had stood nearby while the situation escalated, and he had not done enough to stop it.

Accountability needed to recognize both facts.

A system that treated every person involved as equally responsible would be inaccurate. A system that excused everyone except the person whose name appeared in the headlines would be equally flawed.

“Make sure the final public summary distinguishes the findings about each officer,” Marcus said.

Elaine nodded.

“We'll ask the department to do the same.”

The independent audit began collecting data the following month.

It was slow work.

Some records were complete. Others were inconsistent. Certain fields had been entered differently by different officers, making comparisons difficult. In several cases, the reason recorded for a stop was too vague to support a meaningful assessment.

The auditors refused to treat missing information as proof of wrongdoing.

They also refused to treat it as irrelevant.

A system that could not reliably explain why certain enforcement decisions were made had a problem even before anyone determined whether a particular decision was discriminatory.

The preliminary report identified several areas requiring further examination.

The most significant concerns involved inconsistent documentation, uneven compliance with recording requirements, and limited mechanisms for identifying recurring patterns in complaints and stops.

The available data did not justify a sweeping conclusion that every disparity reflected intentional discrimination. But it also did not support the department's earlier assumption that the original incident could safely be treated as an isolated misunderstanding without examining broader practices.

The auditors recommended improvements in documentation, supervisor review, recording compliance, and complaint tracking.

They also recommended periodic analysis of stop data, with clear procedures for investigating unexplained patterns.

The report contained a section acknowledging limitations.

Some records were incomplete. Some variables could not be compared reliably. The available information could not reveal the motivation behind every individual stop.

The auditors were explicit about what they could and could not establish.

Marcus read the report in its entirety.

He did not celebrate.

He called Naomi and asked her to prepare a public summary that retained the limitations rather than burying them in fine print.

“People need to know what the audit found,” he said. “They also need to know what it didn't find.”

Naomi agreed.

“What about the recommendations?”

“We need a response from the department that identifies who is responsible for each one and when the changes will be implemented.”

“And if they refuse?”

“Then the refusal should be documented as clearly as the recommendation.”

When the report was released, the public reaction was mixed.

Some community advocates said the findings confirmed concerns they had raised for years. Others argued that the audit did not go far enough. Several police representatives emphasized that the report had not established intentional discrimination in every case.

The department issued a response accepting some recommendations and requesting additional discussion on others.

There was no universal agreement.

There was, however, a public document that people could examine, question, and use to demand further action.

For Marcus, that mattered more than a declaration that the problem had been solved.

The most difficult meeting took place after the audit had been published.

Deputy Chief Harlan invited Marcus to a private discussion about the department's response.

This time, Marcus brought Denise Walker and an independent legal adviser. Harlan attended with the director of professional standards and a representative from the city's oversight office.

Harlan began by acknowledging the audit's findings.

“We accept that our documentation and review systems need improvement,” he said. “We have already started implementing several changes.”

Denise opened her folder.

“Which changes have been implemented, and which have merely been announced?”

Harlan looked toward her.

“We've revised the recording-compliance guidance, begun supervisor training, and created a new monthly review of traffic-stop documentation.”

“Who verifies that the reviews are actually happening?”

“The professional-standards unit.”

“Who verifies the professional-standards unit?”

Harlan paused.

“The civilian oversight office will receive quarterly summaries.”

Denise nodded.

“Will those summaries be public?”

“Subject to applicable privacy restrictions, yes.”

“And will the department report when an officer fails to comply with the recording requirements?”

“Aggregated compliance information will be included.”

Denise wrote something down.

“Good. That's a measurable commitment.”

Marcus watched the exchange.

News in the same category

They Arrested Him for Driving a $410,000 Car — Then Learned He Designed It.

45 Part