Content Moderation Checklist

Require editors to confirm manual checks before selected Content Moderation transitions, and record their confirmations in the content revision log.

Features

• Configure a separate checklist for each workflow transition.
• Require confirmations in core node editing forms and the compact moderation form.
• Validate required checks on the server, including when JavaScript is unavailable.
• Record the editor's account, UTC time, workflow, transition, content language, and confirmed wording in the revision message.
• Preserve the editor's own revision message and use Drupal's existing revision history and permissions.
• Export checklist settings with the workflow and translate them through Configuration Translation.

For example, a publishing checklist can ask an editor to review alternative text, check links, or confirm that a legal review has taken place. The editor performs those checks; the module does not analyze the content.

Post-Installation

Enable Content Moderation Checklist. Go to Configuration → Workflow → Workflows, edit a Content Moderation workflow, and open Editorial checklists. Add one plain-text check per line for the transitions you want to control. A transition with no checks keeps its normal behavior.

Assign the workflow to the intended content types and give editors the relevant transition permissions. Configuring lists uses the existing Administer workflows permission. The module does not create example content types or accounts.

Additional Requirements

• Drupal 10.6 or Drupal 11.4 and later compatible minor releases.
• PHP 8.3 or later.
• The core Content Moderation, Workflows, and Node modules.

Scope and limitations

Confirmations are manual declarations, not automated accessibility or legal compliance checks. Enforcement covers the supported core node forms; API and programmatic saves, imports, bulk or scheduled operations, revision reverts, other entity types, and custom forms are outside the scope.

Revision messages follow Drupal's access rules and are not immutable. Node access modules may restrict the revision overview. Uninstalling removes checklist configuration but preserves declarations in existing revision messages.