Some content needs to go live at exactly the right time and without scheduling, that timing depends on someone being online, whether it’s late at night, on a weekend, or across time zones. Even during working hours, manually publishing content adds unnecessary coordination and risk.
Automation solves this. When content transitions are scheduled in advance, publishing becomes reliable, predictable, and hands-free. Teams can shift focus to strategy and execution—without the overhead of timing logistics.
While Drupal offers strong content moderation and workflows, the Scheduled Transitions module adds the missing piece—time-based scheduling for content state changes, adding precise, revision-level scheduling for any moderated content—so content moves exactly when it should, without manual effort.
Problem statement
On large, content-heavy websites, teams often need to publish, update, or unpublish content automatically at specific times. This includes campaign pages, release announcements, press embargoes, seasonal banners, and other time-sensitive updates.
Drupal’s core features like Content Moderation and Workflows support revisioning and moderation states (Draft, Needs Review, Published), but they don’t support scheduled transitions out of the box. This leads to a few technical and operational challenges:
Without a reliable scheduling mechanism, content can go live too early, too late, or not at all—creating gaps in campaigns, missed deadlines, or outdated messaging.
Solution
The Scheduled Transitions module allows automated, revision-specific scheduling for any moderated entity (like nodes, custom blocks, etc.). It supports granular permissions, multilingual scheduling, and queue-based processing that doesn’t overload the default cron—making it a solid fit for time-sensitive content workflows in Drupal.
It works across all content entities that use workflows and moderation and supports revision-specific scheduling. Editors can pick the exact revision they want to publish and schedule that transition directly from the UI.
The module provides:
Instead of relying on Drupal’s site-wide cron (which isn’t designed to run every minute), it uses custom queue jobs:
This lets scheduling run every minute without affecting site performance. If needed, the module can also run via default site cron at a longer interval.
By using Scheduled Transitions, editorial teams can automate time-sensitive publishing workflows, avoid manual errors, and remove the need to be online during off-hours. The result: reliable, accurate, and maintainable content scheduling across complex Drupal sites.
Drupal 10 modules used for scheduling
Configure Scheduler module in Drupal 9
Let’s understand the use of this module with the example. The following example uses a flow of draft to publish, but any transition is possible. The general flow for users is:
Conclusion
The Scheduled Transitions module fills a key gap in Drupal’s content moderation system: the ability to automate publishing based on scheduled dates and times for specific revisions. It ensures content goes live exactly when planned, without any manual effort.
Over 1,000 Drupal sites use the module, including government platforms, universities, newsrooms, and nonprofits. It supports multilingual content, strict timelines, and globally distributed workflows.
But scheduling is just the start. Drupal’s next phase is being shaped by AI-assisted publishing.
Features like auto-tagging, translation support, and semantic search are already in use. Organizations like Acquia are adding AI/ML to Drupal DXP stacks, while community-led projects explore LLM integrations.
Governments and global organisations are leading this shift. Drupal powers platforms for the European Commission, UNESCO, the City of Boston, and UNICEF. Major brands like NASA, Pfizer, and The Economist also use Drupal at scale—integrating AI to optimize publishing.
The trend is clear: AI content automation is projected to grow 18.7% annually through 2030. Scheduling will move beyond fixed dates to AI-informed windows based on engagement, traffic, and campaign timing.
Modules like Scheduled Transitions will evolve with this shift—helping Drupal build smarter, data-driven workflows for modern content teams.