Elena nodded.
"That's a reasonable expectation."
Michael opened the evaluation framework.
"Under the proposed process, applicants who are declined will receive an explanation identifying the principal factors behind the decision, subject to legal and regulatory requirements."
Denise looked skeptical.
"Will that explanation actually be useful?"
"It should be," Michael replied.
"Because I've received letters that said almost nothing. They used polite words, but I had no idea what I was supposed to do differently."
Michael paused.
"Then the process needs to be specific enough to help us identify whether the problem is financial, operational, or related to the structure of the request."
Elena watched him.
This was the kind of conversation she had wanted the bank to have.
Not a promise that everyone would receive money.
Not a sentimental argument that every small business deserved a loan.
A discussion about evidence, criteria, and accountability.
The meeting continued.
The business owners described their operations. The bank's team asked questions about revenue, costs, customers, and existing obligations.
Some applications appeared promising.
Others required further work.
One company had strong revenue but weak cash-flow forecasting.
Another had a viable business model but depended too heavily on a single customer.
A third had insufficient records to support the amount requested.
The new framework did not make those weaknesses disappear.
Instead, it made them visible.
And because they were visible, the applicants could understand what needed to happen next.
At the end of the session, Denise approached Elena.
"Can I ask you something?"
"Of course."
"Why did you get involved in this?"
Elena smiled faintly.
"Because I remember what it feels like to have a viable business and no one willing to look beyond the first impression."
Denise nodded.
"Did you ever think about giving up?"
"More than once."
"What stopped you?"
Elena considered the question.
"People who were willing to evaluate the work instead of judging the appearance."
Denise looked toward the conference room.
"I hope this works."
"So do I."
The pilot's first applications entered formal review the following week.
The process was slower than some executives had expected.
Each file required financial analysis, risk assessment, and documentation of the decision.
But the bank's employees were beginning to identify useful patterns.
Applications that had once been dismissed as incomplete were now being reviewed to determine whether the missing information could reasonably be obtained.
Requests that appeared too risky were examined to identify whether the amount, repayment schedule, or collateral structure could be adjusted.
The program did not guarantee approval.
It created a better way to determine whether approval was justified.
Meanwhile, the independent review of Harrington & Cole's internal practices continued.
The reviewers examined additional files and interviewed employees across several departments.
They found that the original seven complaints had not been isolated.
Other customers had experienced inconsistent responses, unexplained delays, or vague rejection notices.
Some complaints involved legitimate misunderstandings.
Others reflected poor documentation.
A smaller number raised more serious questions about whether employees had given undue weight to personal referrals or assumptions about a customer's status.
The bank could not simply apologize for each incident and move on.
It needed a way to identify the causes.
Patricia established a cross-departmental working group to review the findings and propose corrective measures.
Rebecca Bennett led the compliance component.
The group included representatives from human resources, corporate banking, customer service, risk management, and internal audit.
Andrew Miller was not part of the working group.
But he became involved in a related initiative.
After completing the required training, he requested permission to assist with a review of customer service procedures at Counter Seven.
His supervisor was skeptical.
"You want to volunteer for additional work after the incident that put you under investigation?"
Andrew nodded.
"I do."
"Why?"
"Because I think I need to understand how the process should work when the customer doesn't fit the profile I'm expecting."
His supervisor studied him.
"That sounds like something the training should have addressed."
"It did. But I want to see how the procedures work in practice."
The supervisor considered the request.
Eventually, he agreed.
Andrew spent the next two weeks reviewing transaction procedures, comparing them with actual cases, and identifying points where employees might rely on assumptions instead of evidence.
He found several areas that needed clarification.
For example, employees were trained to flag unusual transactions, but the guidance did not always explain how to distinguish an unusual amount from an unsupported source of funds.
Some staff members interpreted the instruction too broadly.
They treated unfamiliar customers as inherently risky.
Others focused almost exclusively on the amount and failed to consider the quality of the documentation.
Andrew wrote a proposal recommending clearer prompts in the transaction system.
Instead of asking only whether a transaction was unusual, the system would ask employees to identify the specific reason for concern and the evidence supporting it.
The proposal was reviewed by compliance.
Several recommendations were adopted.
Andrew did not receive a promotion.
He did not receive a public award.
He received something more useful.
The opportunity to demonstrate that he could learn from a mistake.
One afternoon, he found himself assisting a customer who arrived wearing a stained work jacket and carrying a folder filled with invoices.
The customer needed to verify a business check worth several hundred thousand dollars.
Andrew greeted him, explained the verification process, and reviewed the documents.
The customer watched him carefully.
"Do you need to know what kind of work I do?" he asked.
"Only if it's relevant to the transaction," Andrew replied. "I need to verify the source of the funds and the authority behind the payment. I don't need to make assumptions based on your appearance."
The customer studied him for a moment.
"Good answer."
Andrew completed the preliminary review and referred the transaction for the required verification.
The customer left with a clear explanation of the next steps.
When Andrew returned to his desk, he realized that the interaction had been ordinary.
No one had laughed.
No one had been humiliated.
No one had needed to prove that they belonged.
It was exactly what the process should have been from the beginning.
THE PRICE OF A PROMISE
Six months after Elena's first visit, Harrington & Cole released the results of its internal review to the board and published a summary of the corrective actions it had taken.
The bank did not disclose confidential customer information.
It did not identify employees who had been subject to individual reviews.
It did, however, acknowledge that its procedures for evaluating prospective business customers had not always been applied consistently.
The statement was brief.
It explained that the bank had revised its initial assessment process, expanded independent complaint review, and introduced new documentation standards for significant commercial inquiries.
It also announced a six-month evaluation of the revised procedures.
The response received mixed reactions.