For many attendees, the meeting was the first time they had heard someone in a senior legal role acknowledge the practical weaknesses of complaint procedures without either defending every institution or condemning every officer.
The conversation continued for nearly two hours.
People discussed delays, confusing forms, inconsistent explanations, and the difficulty of obtaining records. Some shared experiences that appeared to involve serious misconduct. Others described encounters in which officers had acted professionally and resolved problems quickly.
Evelyn encouraged the organizers to record the suggestions without turning individual allegations into established facts.
At the end of the meeting, Marisol approached her again.
“People appreciated that you didn't promise them a miracle.”
“I wouldn't know how to deliver one.”
“You also didn't tell them to stop being angry.”
“Anger can be understandable. The important question is what we do with it.”
Marisol smiled.
“That's probably what they needed to hear.”
On her way home, Evelyn thought about the stories she had heard. Her own encounter had involved a well-dressed customer, an expensive boutique, and a police officer whose actions were now under formal review. Many of the people at the community center had faced different circumstances, with fewer resources and less confidence that anyone would listen.
Their experiences could not all be treated as identical.
But they shared a common concern: when authority was exercised, people wanted to know that the decision rested on facts rather than assumptions, and that a complaint would be examined without the outcome being determined in advance.
That expectation was not radical.
It was the foundation of public accountability.
Two days later, the inspector general's team made an important discovery while examining the department's report-management system.
The system recorded when a report was created, when it was edited, and which account had submitted each revision. However, the department's internal guidance did not consistently require supervisors to record a detailed explanation for every substantive change.
That omission did not prove that anyone had altered a report improperly. Some changes were routine. Others had been made at the request of prosecutors seeking clarification before a case proceeded. Several reports had been revised because an officer corrected a factual mistake after reviewing additional evidence.
But the absence of consistent explanations made it difficult to determine why particular wording had changed.
Investigators selected a group of reports for closer review.
One involved a young man who had questioned an officer's decision to search his backpack outside a transit station. The initial version described him as asking whether he was required to consent. The final version described him as becoming confrontational.
Another report concerned a woman who had repeatedly asked an officer to explain why her vehicle was being searched. In the original notes, the officer recorded that she had asked several questions and appeared upset. The final report described her as interfering with the investigation.
The investigators did not assume that the final descriptions were false. They wanted to know what had prompted the changes and whether the revisions accurately reflected the events.
When the officer involved in the transit-station encounter was interviewed, he explained that he had used “confrontational” because the young man had spoken loudly.
“Did he threaten you?” the investigator asked.
“No.”
“Did he attempt to interfere physically?”
“No.”
“Did he refuse a lawful instruction?”
The officer paused.
“I don't remember giving him an instruction he refused.”
“Then what did you mean by confrontational?”
“I meant he was challenging what I was doing.”
“Was he entitled to ask why you were searching his backpack?”
The officer looked uncomfortable.
“I suppose he was.”
“Did the report distinguish between asking questions and interfering with the investigation?”
“No.”
The investigator made a note.
“Would you agree that those descriptions can mean different things to someone reviewing the incident later?”
“Yes.”
The interview continued, and the officer provided additional details that could be checked against the available records.
In the second case, the officer explained that the woman had moved toward the vehicle while he was conducting the search. That detail, if accurate, could be relevant to assessing the encounter. The investigators requested the body-camera footage and dispatch records to determine what had happened.
The developing review was forcing the department to confront a problem more complicated than a few questionable adjectives.
Police officers made decisions in unpredictable circumstances. They needed to communicate quickly and document what mattered. Yet the language they chose could shape the way other people interpreted an encounter long after the immediate danger or uncertainty had passed.
A report that described a person as angry without explaining why might encourage a later reader to view the person as unreasonable. A report that described a person as interfering without identifying the specific conduct could obscure whether an instruction had been lawful or whether the person had actually obstructed anything.
The solution was not to prohibit ordinary descriptive language.
It was to require facts that gave those descriptions meaning.
The inspector general recommended that the department preserve the original wording of substantive reports, record the reasons for material revisions, and establish a consistent supervisory review process. The recommendation was preliminary, pending the completion of the investigation.