“The Login That Wasn’t Mine<\/p>\n\n\n\n
Our managing partner called me into a conference room on a Thursday afternoon to inform me, with a gravity that made my stomach drop before he’d finished his first sentence, that a client’s signature on a finalized settlement document appeared to have been forged, and that my colleague, Richard, had reported seeing me alone in the file room the exact afternoon the document had been completed and submitted.<\/p>\n\n\n\n
“”I wasn’t in the file room that afternoon,”” I said, keeping my voice as level as I could manage given what I was being accused of in front of the firm’s managing partner. “”I was at the Hendricks deposition the entire day, from nine in the morning until well past five. There’s a sign-in log at the courthouse that will confirm that, along with three other attorneys who were in that same room with me.””<\/p>\n\n\n\n
“”That’s a convenient thing to say,”” Richard said from across the table, already wearing the beginning of a smirk he clearly hadn’t planned on needing to hide quite so soon.<\/p>\n\n\n\n
“”It’s not convenient,”” I said, meeting his eyes directly. “”It’s verifiable, same as the courthouse log. But you don’t even need that. Pull the document’s server access history instead. Every single edit is timestamped and tied to a specific login credential. That’ll tell you exactly who was in that file, and when.””<\/p>\n\n\n\n
Our IT director, sitting quietly at the end of the table, pulled the document’s full access history up on the conference room’s shared laptop screen within a few minutes, the managing partner leaning in close to read it directly rather than take anyone’s summary of it secondhand.<\/p>\n\n\n\n
The document had been opened, actively edited, and electronically signed at 2:47 that afternoon, according to a login credential that was clearly, unambiguously logged in the system’s own records.<\/p>\n\n\n\n
It wasn’t mine. It was Richard’s, his exact username sitting right there in the access history, timestamped to the minute the signature field had changed.<\/p>\n\n\n\n
“”Richard,”” the managing partner said slowly, turning the laptop screen fully around so it faced him directly, his voice carrying a new and noticeably harder edge, “”explain to me why your own credentials are the ones logged into editing a document you’re accusing someone else entirely of forging.””<\/p>\n\n\n\n
His confident expression didn’t just fade, it collapsed completely, replaced by the particular stillness of someone realizing the story he’d told has just run headfirst into a server log he apparently never considered anyone would think to check.<\/p>\n\n\n\n
He tried, briefly, to suggest someone might have accessed his account without his knowledge, an explanation that grew considerably thinner once the IT director pulled up the building’s own login records showing his badge access into that same office on that same afternoon, at that same desk, for the full duration the document was open.<\/p>\n\n\n\n
It came out over the following week’s internal investigation that Richard had forged the client’s signature himself, under pressure to push a settlement through before the client, who’d been growing hesitant, had the chance to back out entirely, and that he had decided, once questions started circulating about the document’s legitimacy, that redirecting suspicion toward me was simpler than admitting what he’d actually done.<\/p>\n\n\n\n
He is no longer with the firm, his departure finalized within two weeks of that conference room meeting. I am, and my bar license remains exactly as clean as it was the morning before Richard decided a courthouse deposition alibi and a server access log were things he apparently never expected anyone to bother verifying.<\/p>\n\n\n\n
<\/p>\n","protected":false},"excerpt":{"rendered":"