Ongoing Work

Use ongoing work for recurring streams that need planning and reporting without being recreated as a project each cycle.

When to use ongoing work

Use ongoing work for work that repeats or continues across cycles: recurring security audits, documentation improvements, content publishing, social media publishing, design QA, customer support review, or shared maintenance.

This is especially useful for multidisciplinary teams where product, engineering, design, marketing, support, and operations contribute to the same stream over time. Use an Initiative when the work has a defined outcome and finish line; use ongoing work when the stream itself needs owners, status, children, and reporting.

How it appears

Ongoing work lives alongside initiatives on the roadmap. You can view initiatives only, ongoing work only, or both together. It can carry teams, assignees, status, hierarchy, and taxonomy like other roadmap work.

You can convert between initiative and ongoing work when the shape of the record changes.

Use Roadmap Progress when ongoing work needs to be reviewed beside planned initiatives.