Your workflow,your statuses
Every team works differently. Define custom statuses that match your actual process — from first idea to final publication to archive.
Example status workflow
Create statuses that match YOUR workflow. These are just examples.
Initial concept, not yet started
Work in progress
Waiting for feedback
With legal team
Ready for next step
Queued for publishing
Live and public
Completed, filed away
Why custom statuses matter
Fixed status options
- •'Draft' and 'Final' only — what about Review? Legal?
- •Using folders or tags to fake statuses as workarounds
- •All statuses look the same in lists — no visual distinction
- •Process mismatch: tool doesn't fit how your team works
Custom statuses in WURDX
- •Define exactly what you need: Idea, Draft, Legal Review, Approved
- •First-class feature — statuses appear everywhere
- •Colors & emojis for visual distinction at a glance
- •Configure WURDX to work the way you actually work
Every team works differently
WURDX doesn't force a process on you. Here's how different teams set up their status workflows.
Marketing & Content
Content moves from idea to published. Webhooks notify Slack and CMS when something hits 'Approved'.
Legal & Compliance
Policies need multiple review gates. Admin-only transitions on 'Current' and 'Deprecated' prevent unauthorized changes.
Engineering
RFCs and design docs follow the eng lifecycle. Status changes trigger Linear/Jira webhook updates.
Statuses power everything
Kanban columns
Each status = a column. Drag to change.
Filtering
'Show all In Review' — one click.
Workflow builder
Trigger webhooks on status change.
Frequently asked questions
Ready to define your workflow?
Start with default statuses, customize when you're ready.