That was where the first serious disagreement emerged.
Carlos Mendoza believed the department had made substantial progress and that the panel should focus on supporting supervisors rather than increasing reporting requirements.
Rachel disagreed.
She believed the available data still showed inconsistencies in how supervisors documented their decisions.
Nina Patel argued that both concerns could be valid.
Samuel Whitaker wanted more information before drawing conclusions.
Evelyn asked me to summarize the legal and institutional considerations.
I looked around the table.
“Supervisors need enough discretion to make reasonable decisions,” I said. “But discretion without documentation can make it difficult to determine whether standards are being applied consistently.”
Carlos nodded.
“I agree. But we can't require a ten-page explanation for every minor correction.”
“No,” I said. “That would be counterproductive.”
Rachel leaned forward.
“Then how do we know whether a supervisor actually reviewed the evidence?”
I considered that.
“We need to identify the information necessary for meaningful review without creating unnecessary paperwork.”
Nina smiled.
“That's a systems-design question.”
“Exactly.”
Evelyn looked at Carlos.
“Would you help us develop a sample review framework?”
He nodded.
“Of course.”
She turned to Rachel.
“And would you help identify what information residents need to understand complaint outcomes?”
“Yes.”
I watched them.
The disagreement had not disappeared.
But it had become productive.
That was one of the things I appreciated about Evelyn.
She did not treat disagreement as a threat to the panel's legitimacy.
She treated it as information.
Several months later, the panel received a complaint that tested its independence.
A local business owner named Harold Whitcomb alleged that officers had repeatedly failed to respond adequately to disturbances near his property.
He claimed the department was ignoring him because he had publicly criticized city leadership.
The allegation was serious.
But the initial records suggested a more complicated situation.
Officers had responded to several calls.
Some involved noise complaints.
Others concerned disputes between customers.
In one case, officers had determined that no criminal offense had occurred.
In another, they had referred the matter to the city's code enforcement office.
Harold believed the responses were insufficient.
The department believed it had acted appropriately.
The panel's responsibility was not to decide which side sounded more convincing.
It was to examine the records.
During our review, we discovered that the department's dispatch system categorized several of Harold's calls inconsistently.
Some were listed as disturbances.
Others as requests for assistance.
A few had been closed under administrative codes that made it difficult to understand what officers had done.
The problem was not necessarily retaliation.
But it was poor documentation.
We recommended improvements.
Harold was dissatisfied.
At a public meeting, he accused the panel of protecting the police department.
“You're supposed to hold them accountable,” he said. “Instead, you're making excuses.”
The room grew tense.
Evelyn remained calm.
“Mr. Whitcomb, we reviewed the available evidence and identified documentation problems that require correction.”
He shook his head.
“That's not enough.”
“I understand that you disagree with our findings.”
“You don't understand anything.”
I watched Evelyn carefully.
She did not raise her voice.
She did not dismiss him.
She explained the scope of the review.
She described the evidence.
And she acknowledged the limitations.
Afterward, Rachel approached me.
“That was difficult.”
“Yes.”
“Do you think we handled it correctly?”
I considered that.
“I think we were careful.”
She looked uncertain.
“Is that enough?”
“Sometimes careful work produces conclusions people don't like.”
Rachel nodded slowly.
I continued.
“Our responsibility isn't to validate every allegation. It's to examine them fairly.”
She looked toward the empty chairs.
“And when the evidence doesn't support the allegation?”
“Then we say so.”
She sighed.
“Even when the person is angry?”
“Especially then.”
The panel's first annual report was published the following spring.
It documented meaningful progress.
The complaint portal had been improved.
Supervisory review procedures had become clearer.
Internal reporting channels were being used more consistently.
The department had begun tracking whether corrective training actually changed employee performance.
But the report also identified unresolved concerns.
Some complaint outcomes remained difficult for residents to understand.
Certain data systems were not fully integrated.
Public confidence varied significantly across neighborhoods.
And the department needed to do more to explain how accountability decisions were made without disclosing protected personnel information.
The report was neither a celebration nor a condemnation.
It was an assessment.
That distinction mattered to me.
The city council held a public hearing.
Evelyn presented the findings.
Panel members answered questions.
Some council members praised the work.
Others questioned the cost.
A few suggested that the department had already been monitored long enough.