From Disruption to Direction: Rethinking Journal Publishing Operations

Over the past year, I’ve had the opportunity to engage with journal publishers across a wide spectrum — large and small, global and regional, commercially ambitious and mission-driven. The contexts vary considerably. The markets differ. The portfolio sizes and subject areas range enormously.

But beneath all of that variation, a single question surfaces with remarkable consistency:

How do we scale journal operations without losing control?

Control over timelines. Control over quality. Control over the experience we offer to authors and editors.

This question is not driven by lack of capability. Publishers have capable teams, experienced editors, and established processes. It is driven, rather, by a growing recognition that the system supporting journal publishing is under structural strain — and that the model which served the industry well for the past two decades may no longer be fit for the demands ahead.

---

The System We Built — and the Limits We’re Hitting

Most journal operations today run on a model that has evolved organically, layer by layer, over time.

A distributed structure. Multiple vendors. Discrete stages of work. Submission screening. Editorial office management. Peer review coordination. Production. Quality control.

Each stage, taken individually, often works quite well. The people involved are skilled. The tools are capable. The processes are established.

But the system as a whole does not hold together.

Because between these stages, something consistently breaks: handoffs.

Context is lost in transition. Ownership becomes ambiguous. Visibility degrades. Delays accumulate — not because any single stage is slow, but because the boundaries between stages introduce friction that no individual team has the authority or visibility to resolve.

Over time, this doesn’t just create inefficiency. It creates structural friction — a drag on the entire publishing operation that compounds as volume grows.

Editors spend time following up rather than deciding. Authors experience inconsistency rather than predictability. Operations teams find themselves coordinating work more than enabling it. And as submission volumes increase — as they have consistently, year after year — the gaps between stages become harder to bridge, not easier.

The challenge, in most cases, is not performance. It is design.

---

The Shift from Services to Systems

What we are now witnessing, across the industry, is a deeper and more consequential shift in how publishers think about operations.

The demand is no longer for isolated, specialist services. It is for systems — end-to-end workflow management, connected processes, integrated accountability.

This shift reflects a growing recognition that workflow is not a support layer sitting beneath the real work of publishing. It is the infrastructure of publishing. It determines how quickly manuscripts move, how consistently decisions are made, how reliably quality is maintained, and how confidently authors and editors engage with journals. And increasingly, it determines whether publishing operations can scale sustainably — or whether growth simply means proportionally more coordination cost.

This represents a subtle but important reframing of the operational question.

The old question: How do we optimize each stage?

The emerging question: How do we design the system?

These are meaningfully different. Optimizing individual stages in isolation often increases coordination complexity — because the interfaces between those stages become more numerous and more consequential. What publishers need is not just efficiency within stages. They need flow across the lifecycle.

A system where workflows are continuous rather than stitched together. Where technology is embedded rather than layered on top. Where human expertise is integrated throughout rather than applied reactively. Where accountability is clear and performance is visible in real time.

This is the shift from a vendor ecosystem to an operating model.

---

What an Integrated Operations Model Actually Means

The concept of an integrated publishing operations model is sometimes misunderstood — or conflated with simply outsourcing more work to a single supplier. It is worth being precise about what integration means, and what it does not mean.

Integration is not the same as consolidation. Bringing more activities under one roof achieves little if the underlying structure remains fragmented — if processes are still siloed, if technology platforms don’t communicate, if accountability is still distributed across teams.

What genuine integration requires is continuity — a single, connected workflow in which each stage flows directly into the next without loss of context, and in which the governing logic of the entire system is consistent throughout.

This has specific structural implications.

It means that the intake data captured at submission is still present and accessible at the point of production. It means that the decisions made during peer review are visible and traceable when an editor picks up a manuscript. It means that quality standards applied during copyediting are consistent with the thresholds set during screening. It means that the author’s experience of communicating with the journal is coherent from submission through to proof approval.

None of this is possible when stages are managed by disconnected parties working from different systems, against different incentives, with limited shared visibility.

And critically, integration does not require — and should not involve — the publisher ceding editorial control. The governance boundary is fundamental: who executes the workflow and who makes editorial decisions are two distinct questions, and in a well-designed integrated model, they have distinct, clearly defined answers.

---

The Role of Technology — Infrastructure, Not Add-On

One of the most persistent mistakes in publishing technology adoption is treating technology as something layered on top of existing processes to make them faster or more convenient.

This produces marginal efficiency gains. It does not transform operations.

Technology creates lasting operational value only when it is embedded into the architecture of the workflow itself — when it is structural rather than cosmetic.

Consider AI-driven manuscript screening. Deployed as a standalone tool, it may reduce the time taken for a specific check. But its real impact emerges when its outputs are integrated directly into the workflow — automatically routing manuscripts, triggering the next stage, populating metadata fields, and generating structured reports that follow the manuscript through to editorial decision. At that point, it is not a faster version of an existing step. It is a redesigned step.

The same logic applies across the technology stack: workflow orchestration platforms, automated quality control systems, XML-first production pipelines, collaborative author proofing tools. These are individually capable technologies. Their transformative potential is realised only when they function as a connected system — inputs flowing from one to the next, standards enforced consistently, and data accumulated in ways that make the next decision better informed than the last.

This is what it means for technology to be infrastructure rather than an add-on.

---

Visibility as a Control Mechanism

In most publishing operations today, visibility into the workflow is periodic and retrospective.

Reports are generated at intervals. Status updates are requested. Progress is inferred from the absence of escalations rather than from direct observation.

This is not a minor operational inconvenience. It is a fundamental limitation on the ability to manage performance.

When visibility is periodic, problems become apparent only after they have accumulated — when a turnaround time has already been missed, when an author has already grown frustrated, when a bottleneck has already affected multiple manuscripts downstream.

In a genuinely integrated system, visibility is continuous and prospective. At any point, it is possible to see where every manuscript is, what stage it is in, where delays are emerging before they become problems, and how performance is trending against agreed benchmarks.

This is not merely more convenient. It is a qualitatively different kind of management capability. It enables proactive intervention rather than reactive recovery. It enables meaningful, evidence-based conversations between publishers and their operational partners. And it enables the kind of confident escalation and decision-making that fragmented, low-visibility environments make structurally difficult.

---

Single Accountability as a Structural Advantage

There is another benefit of integrated operations that is frequently underestimated: the clarity of accountability.

In fragmented environments, responsibility is distributed across parties in ways that are often theoretically clear but practically ambiguous. When a manuscript is delayed at the handoff between peer review coordination and production, which party is responsible for resolution? When a quality issue emerges, who owns the investigation and the fix? When an author sends a query that falls between stages, who responds?

These questions may seem straightforward on paper. In practice, their answers often depend on context, relationship, and the willingness of individual teams to extend beyond their defined scope.

In an integrated model, by contrast, a single partner owns execution across all stages. There is one accountability layer, one escalation path, and one performance conversation. This does not mean that things never go wrong. It means that when they do, the path to resolution is unambiguous, and the incentive to resolve quickly is undiluted.

For publishers, this represents a significant reduction in management overhead — not just in terms of time spent, but in terms of the cognitive and organizational complexity of managing multiple supplier relationships simultaneously.

---

Measuring What Actually Matters

Integrated operations also change what can meaningfully be measured — and therefore what can be managed.

In a fragmented model, performance metrics tend to track the outputs of individual stages in isolation: how quickly a particular screening check was completed, how many reviewer invitations were sent in a given week, how many pages were typeset per day. These metrics are useful within their scope. They are not useful for understanding whether the publishing operation as a whole is performing well.

The metrics that matter to publishers — and, more importantly, to authors, editors, and editorial boards — are end-to-end outcomes:

• Time from submission to first editorial decision
• Reviewer invitation acceptance rates and time to first reviewer
• Time from acceptance to first author proof
• Time from acceptance to online publication
• Author satisfaction across the full lifecycle
• Production quality and post-publication error rates

These outcomes cannot be reliably measured — let alone managed — when responsibility for different parts of the lifecycle sits with different parties. They require a single system with a single data model.

And it is these outcomes that determine how a journal is perceived by the research community: its efficiency, its reliability, its respect for the time and effort of the people who publish in it.

---

A Practical Path: Starting with Evidence

Recognising the value of an integrated operations model and implementing one at scale are different things. The transition involves genuine complexity — technical integration, change management, stakeholder alignment, and the inherent risk of changing operational structures that currently work, even imperfectly.

This is why the right path forward is not a wholesale transformation but a measured, evidence-based pilot.

Select a representative cohort of journals — ideally a mix that reflects the breadth of the portfolio in terms of volume, subject area, and operational complexity. Establish clear baseline metrics before the pilot begins. Define the evaluation criteria in advance. Run the integrated model across the selected cohort for a defined period. Then assess the outcomes with honesty and rigour before deciding whether and how to scale.

This approach achieves two things simultaneously.

It manages risk — because the decision to scale is based on demonstrated performance rather than projected assumptions.

And it builds organisational confidence — because the people who need to trust a new operating model are most persuaded by evidence from their own journals, not by analogies from other publishers or claims from suppliers.

---

The Direction of Travel

There is no question that scholarly publishing is in a period of genuine disruption. Submission volumes are rising. AI is reshaping what is possible in manuscript screening, language assessment, and production. Author and editor expectations are increasing, informed by the consumer digital experiences they encounter elsewhere. The pressure on turnaround times is intensifying. Compliance requirements are expanding.

Disruption, on its own, is not directional. It creates pressure and possibility simultaneously. What makes it valuable is the response it provokes — the willingness to question structures that have been accepted as given, and to invest in designing something better.

The direction that is emerging, across the industry, is clear: journal publishing is moving toward being managed as an integrated, measurable, and accountable operating system — not a collection of services, not a network of vendors, but a deliberately designed system in which operational continuity, technological integration, and clear accountability are foundational rather than aspirational.

This shift does not displace editorial judgement. It does not reduce the importance of editors, reviewers, or the scholarly communities that give journals their authority. It creates the operational conditions under which those things can function at their best — free from the friction, delay, and ambiguity that fragmented systems routinely impose.

OneFlo is Integra’s working model for this shift. It is not a finished answer to every question. It is a designed system, built around the principle that one partner, owning the full lifecycle, and accountable for end-to-end performance, can deliver the continuity, transparency, and quality that scholarly publishing increasingly demands.

The most compelling argument for it is not the logic of its design. It is what it produces when it runs.

---

Ashutosh Ghildiyal is Vice President – Growth & Strategy at Integra. He works with scholarly publishers on operational strategy, transformation, and the design of next-generation publishing models. His focus is on building scalable systems that combine operational clarity with execution rigour.