Cleveland.com removes reporter byline from AI “Express Desk” story after complaint
Kaitlin Durbin said the article ran under her name while she was on her honeymoon and that she “did not write or review a word of it.”
Cleveland.com government reporter Kaitlin Durbin said an AI-assisted “Express Desk” story was published under her byline without her knowledge while she was on her honeymoon. Cleveland.com later removed her name and posted a correction note saying the byline was added “in error.”
Key Takeaways
- A Cleveland.com “Express Desk” story assisted by AI tools appeared under government reporter Kaitlin Durbin’s byline while she was away, according to her Sept. 7 post on X.
- Durbin said she “did not write or review a word of it,” and described the item as a local update about Cuyahoga County’s law director stepping down.
- Cleveland.com updated the page to remove Durbin’s name and added a correction note stating a reporter’s byline was added “in error,” leaving the story labeled only as “Cleveland.com Express Desk.”
- Editor Chris Quinn attributed the incident to “a miscommunication between a couple of editors,” framing it as an operational mistake rather than a dispute over credit.
Durbin Says an AI “Express Desk” Story Ran Under Her Name While She Was Away
The mechanism here is simple and consequential. A byline is the author credit that tells readers who is responsible for the reporting and editing decisions on a story, and Durbin says that signal was attached to an AI-assisted desk item she never touched.
In a post on X dated Sept. 7, Durbin wrote that she was “Trying to understand how this story published with my byline last week while I was on my honeymoon.” She added: “I did not write or review a word of it and it does not pull info from past reporting.”
Durbin also framed the episode as a question of consent and ownership over her professional identity. “Does Cleveland.com think they just own my name now?” she wrote.
The story Durbin referenced was described as a local news item about the law director of Ohio’s Cuyahoga County stepping down. Durbin said it “had nothing to do with her reporting,” and that it did not draw from her prior work.
Cleveland.com Pulls the Byline and Posts a Correction Note
After Durbin’s post, the article page was updated. Durbin’s byline was removed, and Cleveland.com appended a correction note that addresses the byline directly rather than the underlying local-news content.
The correction language was explicit about the nature of the change: “Note: This story has been updated to correct the byline,” the note reads. It continues: “A reporter’s byline was added to the story in error.”
The story ultimately carried no named author credit beyond the desk label “Cleveland.com Express Desk.” That matters because it shifts accountability from an individual reporter to a newsroom workflow, which is exactly where Durbin’s complaint lands.
The correction also supports a narrower interpretation of what went wrong. The outlet did not argue that Durbin contributed, edited, or approved the piece. It treated the byline as an operational error that needed to be reversed.
Editors Call It a Miscommunication as the Express Desk’s Review Claims Get Re-tested
Cleveland.com has publicly framed its “Express Desk” as an AI-assisted publishing pipeline, not an autonomous one. The desk “uses AI tools to assist in producing content” that the outlet says is “reviewed and edited by staff.” The Durbin incident re-tests that claim in the one place readers can verify it quickly: the byline.
Editor Chris Quinn described the byline attachment as “a simple mistake, the result of a miscommunication between a couple of editors.” He said, “It was corrected as soon as we learned of it from the Tweet.”
Quinn also pointed to prior public explanations of Cleveland.com’s AI policies. He said he has “written extensively about our policies, practices and controls regarding AI content in my From the Editor columns this year,” then added: “If you’re looking for information about us, it’s all there. I have nothing to add.”
The episode also cuts against Cleveland.com’s earlier positioning that AI desk output would still map cleanly to human responsibility. Leila Atassi, the outlet’s editor of public interest and advocacy, previously said AI desk stories would still be “the work of a real reporter.” She added: “It’s real accountability… AI is the assistant, but it’s not the journalist.”
The unresolved friction is procedural, not philosophical. The packet does not include independent documentation of whether staff reviewed and edited this specific Express Desk story before publication, and Quinn’s explanation does not describe the CMS or handoff step where a named byline could be attached while the reporter was away.
Signals to Watch for AI newsroom byline error sparks backlash
The first signal is whether Cleveland.com publishes a more detailed account of how Durbin’s byline was attached beyond “miscommunication between a couple of editors.” In AI-assisted workflows, the failure mode is often mundane: a template default, a copy-forward field, or a permissions shortcut that works until someone is out of office.
Second is whether Cleveland.com clarifies, in this specific case, whether the Express Desk story was reviewed and edited by staff prior to publication. The outlet’s general claim is that staff review exists, but the Durbin complaint is about a named reporter being presented as that reviewer when she says she was not.
Third is whether more Express Desk stories receive corrections or byline changes. A single corrected incident can be a one-off workflow slip. Multiple similar edits would indicate a systemic labeling problem that readers cannot reliably detect in real time.
Finally, watch for updated guidance from Cleveland.com leadership on labeling standards for AI-assisted stories, including when a named reporter’s byline is appropriate versus when a desk byline is the only honest attribution.
What Traders Should Infer About AI-Generated Information Pipelines
The threshold that matters here is attribution integrity, not the local-news subject of the Express Desk item. If a newsroom can accidentally attach a reporter’s name to an AI-assisted story she says she never saw, then the byline stops functioning as a clean accountability primitive, and readers have to treat it as a best-effort label rather than a guarantee.
If Cleveland.com can explain the exact workflow step that caused the byline attachment and tighten controls so it cannot recur, this stays a contained operational error. If it cannot, the practical consequence is broader: AI-assisted publishing pipelines will keep producing information that looks fully vouched-for right up until the moment a byline is revealed to be a UI artifact rather than a human sign-off.
