Workflow order
Editors can only move a submission forward to the next allowed status from its current position in the workflow. This keeps the queue consistent and prevents people from skipping required steps.
Help
How to use the tracker
This page covers the workflow rules and small behaviors that are easy to miss when you first start using the queue.
Reverting a submission
A submission can be sent back only along the workflow paths the tracker allows. If a story needs more work, move it back to the nearest valid earlier step instead of forcing it forward.
Editor assignment
Editors and admins can assign or unassign a story. Viewers can inspect the queue but cannot make workflow changes.
Notes and replies
Notes are internal only. Staff can add a top-level note or reply within the same thread, but replies stay at one nested level so discussions stay readable.
Synopsis and manuscript links
The Manuscript panel shows the original uploaded document and the Google Doc link when a conversion exists. Editors and admins can update the synopsis in writable environments.
Read-only environments
Local and staging are intentionally read-only against live production data. They are meant for validation, not operational queue changes.
Current workflow statuses
SubmittedIn ReviewEditingProofreadingLockedRejected
Editors can move a submission forward only along the allowed workflow transitions, and can move it back only to valid earlier workflow steps when work needs to be revisited.