Status reliably tells the team what stage the piece is in and what should happen next.
How it works
Use status as workflow state
Choose the status that describes what must happen next, not merely who last touched the piece.
Keep publishing states meaningful
Scheduled, publishing, published, and failed states reflect delivery evidence and can have field locking or recovery behaviour.
Add custom statuses carefully
Brand admins can add or arrange custom workflow states when the existing pipeline does not express a real handoff.
Use the same definitions
Document what each custom status means and when a person should move work into or out of it.
Was this page helpful?
Related articles
Need more help with this?