A few had admitted that they had occasionally relied on impressions rather than documented evidence when deciding whether a customer appeared suspicious.
None had described themselves as prejudiced.
Most had believed they were exercising judgment.
That was precisely why James considered the investigation important.
A system did not become fair simply because the people operating it believed themselves to be fair.
It became fair when its decisions could be examined, its procedures could be challenged, and its failures could be corrected.
At nine o'clock, the chief executive opened the meeting.
“Let's begin with the findings.”
Priya Shah connected her laptop to the conference-room display.
The first slide contained a timeline of Brandon Coleman's visit.
12:16 p.m.
Customer enters branch.
12:19 p.m.
Initial documentation presented.
12:31 p.m.
Manager raises concerns.
12:38 p.m.
Senior teller recommends verification.
12:43 p.m.
Manager declines verification.
12:47 p.m.
Check destroyed.
12:49 p.m.
Security instructed to remove customer.
12:52 p.m.
Regional vice president arrives.
The room remained silent as Priya explained the sequence.
She then displayed the relevant excerpts from the transaction system.
The check had not been submitted to the issuing institution for verification.
The system had generated a verification prompt.
The manager had classified the transaction as suspected fraud without documenting a specific discrepancy.
The branch's procedures did not authorize the destruction of the instrument under those circumstances.
The evidence was clear.
The chief executive looked at the general counsel.
“Any disagreement with these findings?”
“No,” the general counsel replied. “The facts are supported by the records and witness statements.”
Priya moved to the next slide.
It summarized the reopened complaints.
Twenty-seven cases had been identified as potentially relevant.
Twenty-one had now received detailed review.
Nine contained allegations involving race, appearance, or perceived financial circumstances.
In several cases, the evidence supported a finding that procedures had been applied inconsistently or that customer complaints had not been adequately investigated.
Other cases remained unresolved because the available records were incomplete.
The report did not claim that every questionable decision was discriminatory.
It did establish that the bank's existing review process had failed to identify patterns that deserved examination.
The chief executive leaned forward.
“What are the principal control failures?”
Priya answered without consulting her notes.
“First, our procedures rely too heavily on subjective judgments without requiring employees to identify the specific evidence supporting those judgments.
“Second, we do not consistently require a second-level review when a manager classifies a high-value transaction as suspected fraud before verification is completed.
“Third, our complaint system evaluates cases individually but does not reliably compare similar complaints across branches.
“Fourth, our records do not always distinguish between an objective transaction discrepancy and a customer's appearance, behavior, or perceived financial status.”
The chief executive looked around the table.
“Can we fix those issues without compromising our fraud-prevention responsibilities?”
“Yes,” Priya said. “In fact, clearer procedures should improve our ability to identify genuine fraud. Employees will still be able to escalate suspicious transactions. They will simply need to document the specific reasons for doing so and follow the appropriate verification process.”
The head of risk management nodded.
“We should also separate immediate risk controls from conclusions about intent. An employee can flag a transaction for review without declaring the customer a fraudster.”
“Agreed,” Priya said.
James spoke for the first time.
“We also need to examine how managers respond when customers challenge their decisions.”
The head of branch operations frowned.
“Customers can be difficult. Some become aggressive when a transaction is delayed.”
“Of course,” James replied. “But the fact that some customers behave badly does not justify treating a polite request for clarification as a threat.”
He placed his hands on the table.
“Mr. Coleman asked for verification. He asked which procedure applied. He asked for a written explanation. Those were reasonable requests. The manager interpreted them as a challenge to her authority and responded by destroying the check.”
The room remained quiet.
James continued.
“If we want employees to exercise sound judgment, we must also teach them that authority does not remove the obligation to explain a decision.”
The chief executive nodded.
“Let's discuss the corrective actions.”
The New Rules
The board reviewed the proposed changes one by one.
The first was a mandatory verification protocol for high-value financial instruments.
Employees would have to record the specific checks performed, the source of the verification, and the evidence supporting any decision to reject or escalate the transaction.
A manager could still stop a transaction when legitimate concerns existed.
But the decision would require a documented reason.
The second change concerned the destruction or alteration of customer documents.
Employees would be prohibited from destroying a financial instrument merely because they suspected fraud. Any document believed to be fraudulent would have to be preserved according to the bank's evidence-handling procedures and referred to the appropriate team.
The third change involved supervisory review.
If a manager rejected a transaction before completing the available verification steps, a second authorized employee would have to review the decision unless an immediate, documented security concern required otherwise.
The fourth change created a centralized customer-review office.
Customers would be able to challenge a branch decision without having to rely on the same manager whose conduct they were questioning.
The office would have authority to review transaction records, request additional documentation, and refer potential policy violations to compliance.
The fifth change concerned historical complaints.
The bank would establish a process for comparing similar complaints across branches and identifying patterns that individual case reviews might miss.
The sixth change required managers to complete training on evidence-based decision-making, professional communication, and the distinction between legitimate fraud indicators and subjective impressions.
The training would not be treated as a substitute for accountability.
Completion would be recorded.
Managers would be tested on practical scenarios.
Repeated violations could result in disciplinary action.
The seventh change introduced periodic independent audits of selected transaction decisions.
The audits would examine whether comparable cases had received comparable treatment, whether required verification steps had been followed, and whether decisions were supported by documented evidence.
The board approved the proposals in principle.
Then the chief executive turned to James.
“What do you recommend regarding the Philadelphia branch?”
James considered the question.
“An immediate review of every transaction marked as suspected fraud under the previous management team. We should also review unresolved customer complaints and contact customers whose cases may have been affected by the failures we've identified.”
“How far back?”
“Three years initially. If the review identifies earlier patterns that warrant examination, we should extend the period.”
The chief executive nodded.
“Approved.”
James felt a measure of relief.
The decision did not solve everything.