Getting startedSet up integrationsCreate your first initiativeInvite your teamPlan today's workShare your first update
InsightsPlanned vs unplannedRoadmap ProgressPull Request FlowTaxonomy AnalyticsAgent Analytics
DocsAPI Reference

Main

  • Home
  • About
  • Pricing
  • Vault
  • Changelog
  • Docs

Features

  • Roadmaps
  • Planning
  • Standups
  • Status updates
  • Insights
  • AI assistant / MCP
  • Integrations

Solutions

  • Startups
  • Dev shops / agencies
  • Software teams
  • Internal IT & platform teams

Alternatives

  • vs Jira
  • vs Linear
  • vs Asana
  • vs Monday.com
  • vs ClickUp
  • vs Notion

Company

  • Blog
  • Security
  • Log in
  • Sign up
  • Terms of Use
  • Privacy Policy

Resources

  • Docs
  • Community
  • API reference
  • CLI
  • Desktop app
  • SDK

© 2026 One Horizon. All rights reserved

FacebookInstagramThreadsXRedditTikTokYouTubeMedium


Planned vs. Unplanned Work

Use planned versus unplanned work to see whether completed work followed the plan or came from unplanned intake.

What it measures

The dashboard chart is called Planned vs Unplanned Work. Completed tasks linked to initiatives count as planned. Completed work that is not linked to an initiative counts as unplanned.

The chart appears in Insights when initiative allocation data exists for the selected workspace or team.

Planned vs Unplanned Work

Distribution of planned and unplanned completed work


How to read it

A high planned share usually means completed work is attached to initiatives before it ships. A high unplanned share does not automatically mean the team is doing the wrong work. It means more work is coming through interrupts, bugs, support, operations, or undocumented decisions.

Use the chart to decide whether unplanned work should become a tracked initiative, move through Triage, or change the roadmap conversation.

A short overview of how unplanned work, blocked tasks, and hidden requests become visible enough to plan around.

How to improve the data

Keep initiative links, statuses, owners, and taxonomy current. Move real planned work out of vague backlog state. Keep bugs and support work visible instead of hiding reactive work inside feature initiatives.

Use Initiatives and Backlog together so planned work and reactive work stay distinct.


PreviousInsightsNextRoadmap Progress

Related Articles

Agent Analytics

Understand how agent-assisted work is attributed in Insights and roadmap reporting.

Insights

Use workspace and team insights to understand delivery activity, planning health, pull request flow, and work distribution.

Pull Request Flow

Pull request flow shows whether code is moving through review and merge at a healthy pace.

Roadmap Progress

Roadmap progress connects initiative status, child work, and activity back to the plan.

  • What it measures
  • How to read it
  • How to improve the data
  • Back to top