Story code: ST-000676
Part 2: The Packet Knew Him Better Than He Claimed
After Evelyn asked him how he found the paragraph so fast, Dylan kept his fingertip on the page for a second too long, then lifted his hand and gave a small shrug like the question itself was overblown. The lobby noise outside our glass wall stayed steady-phones, footsteps, the soft thud of the entry door-and inside that office the only thing that changed was the amount of space around his answers. He had come in claiming he could not follow basic bank wording, but the packet in front of him seemed to know exactly where his hands wanted to go.
“It’s just the page we were looking at before,” he said.
Evelyn lowered her glasses and looked down at the stack. “No, it wasn’t.”
I said, “Let’s reset.”
I gathered the packet, squared it against the desk, and put it back in the center where both of them could see it. Then I slid our bank verification checklist beside my note pad.
“At this point,” I said, “I need to confirm what this packet is, where it came from, and who completed it. That’s standard when a document doesn’t match our current format.”
Dylan smiled again, but it was the quick version this time. “Totally fine. That’s why we came in. I’m useless with forms.”
He said useless, then watched closely while I turned to the first page.
I asked Evelyn direct questions first, because I wanted the sequence clean. Had she printed this packet? No. Had she downloaded it herself? No. Had she been told by branch staff to sign this exact set of pages? No. Each answer came after a pause, each pause a little longer because Dylan kept shifting in his chair and trying to fill the silence.
“She asked me to help,” he said.
Evelyn answered without looking at him. “I asked you to help me make an appointment.”
That landed and stayed there.
I moved to the packet itself. “Who put these pages in this order?”
Dylan let out a small laugh. “Probably me, but not on purpose. I was just trying to keep it together.”
“Did you fill in any typed information?”
“I copied what she told me.”
Evelyn turned her head toward him. “You told me it was already on the form.”
He spread his hands. “Some of it was. Some of it I entered. That’s what I mean. This is why I said I’m bad at explaining it.”
That was his rhythm. Every clean question turned into mist, and every bit of mist drifted back toward Evelyn.
I began checking the pages against our system references. The titles were close to real service forms but not exact. A disclosure paragraph used terms we had retired. A routing line appeared on a page that did not require one. On page three, an internal reference code was formatted almost correctly, except for one transposed digit. None of that was proof by itself, but it was enough to trigger the next routine step.
I rotated the checklist so I could see the second section. “Because this packet was presented by you,” I told Dylan, “I need to verify the source path and completion sequence with the presenting party before we go any further.”
He blinked once. “The source what?”
“The source path. Where you got it, what screen or contact produced it, and the order the pages were completed in.”
He leaned back and gave me another helpless smile. “That’s exactly the stuff I don’t know. She wanted the forms, I pulled them up, and then it all kind of blurred together.”
He made a circling motion with one hand, vague on purpose.
I kept my tone level. “That’s fine. We can do it another way. Standard verification also allows the presenting party to identify the packet by structure.”
He did not answer right away.
Evelyn looked from me to him. “Dylan, if you brought this in, answer her.”
“I’m trying,” he said, sharper than before. “I’m saying I don’t know the technical names.”
“You don’t need technical names,” I said. “I only need you to show me how you handled the packet.”
That was when he stopped performing small confusion and started performing patience instead. He sat very still, eyes on the papers, jaw tight for one beat, then relaxed it.
I separated the packet into two short stacks and placed them face down. “Routine question,” I said. “Which stack contains the page with the supplemental authorization block you said Ms. Harper kept missing?”
He looked at the left stack first. Then his eyes flicked right. Then back to me.
“I don’t know what that’s called,” he said.
“A minute ago you put your finger on it without looking,” Evelyn said quietly.
No one raised a voice. The lobby noise outside kept moving past the glass.
I continued as if we were still in ordinary process. “If you can identify it, we can continue verification. If you can’t, I’ll need manager confirmation before any part of this packet stays in our workflow.”
His fingers tapped once against the chair arm, then stopped. He looked at the two face-down stacks with the concentration of someone trying not to reveal how much he already knew.
Then he asked, too carefully, “If I show you the right one, what exactly happens next?”
That was the clearest sentence he had given me all morning, and it was the first one that sounded like he understood the structure better than he wanted either of us to notice.