When the inquiry reached Halcyon's technology department, Leila discovered a second danger: the temptation to automate away responsibility. A vendor offered an intake tool that would scan identification, recognize names and assign visitors a service priority. The demonstration was smooth. Customers entered, a green light appeared, and the system sent them to a desk without requiring conversation. The salesperson called it an objective solution. Leila asked what variables determined the priority. The vendor would not provide the complete list without a contract.
She requested a technical evaluation anyway. In a simulated environment, staff entered fictitious clients with identical appointments but different histories of previous visits. The system treated a missed appointment as a reason to assign lower priority, even when the appointment had been marked missed because the bank's own receptionist had refused to admit the visitor. An earlier error could therefore become evidence supporting a later one. Leila stopped the demonstration and asked the salesperson how a customer could challenge the label. He referred her to the company's administrator console. She asked how someone outside the building would know the label existed. He did not answer.
The episode changed the direction of the bank's reform plan. Rather than purchasing an opaque ranking engine, the project team built a simpler verification tool with a visible sequence of checks. It confirmed the booking, identified the assigned service desk, and recorded a reason whenever assistance could not proceed. Every denial required review by a second employee who had access to the same evidence. A visitor could receive a reference number without disclosing an account balance to the person at reception. Complex exceptions went to trained staff rather than being hidden behind a score.
Leila wrote test cases based on mistakes she and Peter had found. What if a visitor used a preferred name? What if a wheelchair user arrived late because the accessible entrance was locked? What if a confirmed appointment had been booked by a guardian? What if a person came only to ask whether a document was required? The software did not need to decide that all visitors were eligible for every service. It needed to keep staff from claiming an eligibility decision had been made when no one had examined the evidence.
The first unannounced assessment of Halcyon's new process was deliberately uneventful. A test visitor named Mr. Nash arrived asking about a document required for a charitable account. He wore work clothes, carried no expensive accessories, and spoke plainly. The receptionist checked whether he had an appointment, established that he was requesting general information rather than account access, and provided the public requirements without demanding private financial details. An independent observer recorded the exchange. It lasted four minutes and contained nothing a camera crew would have considered dramatic. That was the point.
The second visit was less successful. A woman who used a mobility aid arrived through the side entrance specified on the bank's website. The door was locked. She called the posted number and waited in the rain before someone came to admit her. Inside, the receptionist followed the revised verification procedure correctly. The appointment proceeded, but the visitor had already experienced a barrier. The bank's initial scorecard marked the interaction as compliant because the reception steps had been completed. Leila challenged the classification. A process should be judged from the visitor's actual arrival, not from the moment the institution chose to begin counting.
The facilities manager reviewed the door's schedule and found that a building automation update had changed its locking hours. It was a mundane technical error, easily corrected once identified. Yet nobody had noticed because the accessible entrance was rarely used by the executives who approved the building's service standards. The incident prompted a wider review of the bank's instructions, including online directions, translated materials, and procedures for clients who could not use a telephone. The project team discovered that a promise of equal service required more than equal treatment at a single desk.
Leila presented the findings to a staff group that included Daniel and Priya. She expected embarrassment, but Daniel seemed relieved. He had spent years reporting broken doors through a maintenance channel that recorded repairs without tracking whether people had missed appointments. Priya suggested that the bank include a way to correct the absence code when a building failure delayed a visitor. The suggestion was adopted, and the test visitor received confirmation of the change.