NewsLabs
Customer loginBook a demo

Written by

Todor Papić
Todor PapićStrategist and business developer

Todor Papic is a strategist and business developer at NewsLabs, where he helps newsrooms and media companies turn ideas into growth. Drawing on years of experience at the intersection of media, sales, and strategy, including work with editorial analytics, he writes about focus, mindset, and how media teams can work smarter.

LinkedIn
← All stories
ENGINEERING

Beyond model power: Why newsroom AI success depends on workflow architecture, not bigger context windows

Beyond model power: Why newsroom AI success depends on workflow architecture, not bigger context windows
  • Large context windows don't guarantee performance. Models routinely lose track of information buried in the middle of a long prompt, a problem researchers call "lost in the middle."
  • Systems built on retrieval-augmented generation (RAG) and workflow orchestration give newsrooms the accuracy and verifiability that journalism requires and general-purpose models don't provide.
  • Newsroom leaders are better off investing in platforms and engineering skills that give them control over AI outputs than waiting for the next, more powerful general-purpose model.

Model makers now advertise context windows of up to two million tokens, enough to fit thousands of pages of text in a single prompt. For newsrooms, that sounds like an AI assistant that could read an entire archive or draft an in-depth report with perfect recall. It doesn't work that way. For journalism, where the stakes of getting things wrong are high, raw model power and context size matter far less than the system built around the model.

The illusion of the infinite context window

A bigger context window does not automatically produce better results. Performance usually degrades long before the token limit is reached. A widely cited 2023 Stanford study documented the "lost in the middle" problem: LLMs handle information placed at the very beginning or end of a long context much better than details buried in the middle, which they often ignore or misread. For a journalist synthesizing several documents at once, that's a serious failure mode. The model can produce a plausible summary that silently drops a contradictory fact because of where it happened to sit in the input.

Cost and speed are problems too. Transformer models, the architecture behind most LLMs, use a self-attention mechanism that compares every token against every other token, so computation scales quadratically with context length. Doubling the input can quadruple processing time, which rules out real-time tasks like live fact-checking. And since most providers charge per token, filling a huge window with marginally relevant material gets expensive fast. The effective context length, the range where a model actually performs well, is usually far shorter than the advertised maximum.

From prompt crafting to automated workflows

Prompt engineering, the craft of writing careful text instructions to steer a model, was the first attempt at control. It's a useful skill and a shaky foundation for critical business logic. Serge Liatko, CTO of LAWXER, calls it "transitional scaffolding": fragile, manual, and hard to scale. Making LLMs useful in production means building automated workflows where code, not a person, manages the context.

The first big architectural step is retrieval-augmented generation (RAG). Instead of relying on a model's static training data, a RAG system first retrieves relevant, current information from an external knowledge base, such as a news organization's own archive, a trusted public database, or a live data feed, and hands it to the model as context. The output is grounded in checkable sources, which cuts hallucinations sharply and leaves a traceable evidence trail. For journalism, that trail is the whole point. A recent paper on long-form fact-checking found that RAG-based systems beat baseline LLMs on factual consistency for exactly this reason: their outputs were anchored to a curated corpus of scientific papers.

The next step is to automate that layer entirely. A scalable system doesn't depend on an engineer hand-crafting context snippets. Scripts can introspect databases, generate up-to-date schemas, and deliver concise documentation to the LLM at exactly the step in the workflow that needs it. This is the shift from "context engineering" to what Liatko calls "automated workflow architecture": breaking complex tasks into atomic steps and using code to manage the flow of information between them.

Building a fact-checking engine, not a chatbot

Recent fact-checking research shows the gap between a general-purpose model and a purpose-built journalistic tool. A study presenting SAFE, a System for Accurate Fact Extraction and Evaluation, describes a multi-agent RAG architecture built to counter COVID-19 misinformation. One LLM agent scans long articles and extracts individual claims. A second agent then verifies each claim against a corpus of 130,000 scientific documents using an advanced RAG framework.

This modular design addresses several LLM weaknesses at once. Chunking and claim extraction sidestep the lost-in-the-middle problem, because each claim is processed in a narrow, focused context. RAG grounds every verification in a trusted, domain-specific knowledge base rather than the model's generalized and possibly outdated training data. And the system returns the supporting evidence alongside each verdict, which a generalist chatbot won't do. That is a different thing from pasting an article into a chatbot and typing "fact-check this." It is an engineered process built for reliability and auditability.

The new newsroom stack: orchestration and observability

These systems require new tools and disciplines. Orchestration frameworks like LangChain, LangGraph, and LlamaIndex provide the building blocks for multi-step, stateful applications: chains of logic that connect LLMs to data sources, APIs, and other tools, and manage context through the whole workflow. This is the technical foundation for moving past simple prompts to real AI-powered newsroom applications.

Building is only half the job. Keeping these systems reliable in production requires observability: monitoring whether the retriever found the right documents, whether the final output stays faithful to its sources, and how many tokens each query consumes. Treating the context window as a strict budget forces developers to decide which tokens actually earn their place, which improves both performance and cost.

Curious why workflows beat LLM context windows?

Schedule a 30-minute call with our team can show you what is possible inside NewsLabs

Book a call

For newsroom leaders, the practical takeaway is to stop waiting for an even more powerful, all-knowing general-purpose LLM. AI in journalism will be shaped by specialized, architected systems that give editors control over outputs, a verifiable evidence trail, and a fit with professional workflows. The advantage will sit with organizations that have the engineering discipline to build smart systems around whatever model they use, rather than with whoever has access to the biggest one.

This article was drafted using AI, namely NewsLabs, on whose website you are reading these lines. It was verified and edited by a human editor.