Block timeline
Each team's items and their status.
Definition · Updated Nov 2, 2026
A block timeline gives each team a column of blocks, one per item, with its status and days left. Blocked items stand out without dates on every block. Use it for roadmaps, squad plans and release tracking.
Pay once. Every update included.
Live preview
Sample data: items across core, growth, platform and mobile squads, shipped, in progress, blocked and planned
- Data shape
- Items with a team, a status and days left
- Good for
- Roadmaps, squad plans, releases
- Avoid when
- Exact dates matter
- Sizes
- XS, S, M and L, re-laid out from the data
Anatomy
Inspect it like the Figma file.
The same layers, names and tokens as the component. Select one to read its size, fill and style.
Layers
038 / Block timeline
- Layer
- block · usage alerts
- Type
- Rectangle
- Size
- 185 × 66
- Fill
- data/cat-2
- Radius
- 4
- Group
- Marks · 8
Layers
038 / Block timeline
- Layer
- block · usage alerts
- Type
- Rectangle
- Size
- 105 × 42
- Fill
- data/cat-2
- Radius
- 4
- Group
- Marks · 8
Layers
038 / Block timeline
- Layer
- block · usage alerts
- Type
- Rectangle
- Size
- 65 × 29
- Fill
- data/cat-2
- Radius
- 4
- Group
- Marks · 8
Sizes
Re-laid out, never scaled.
The same data at XS, S, M and L. Every size is redrawn from the data, so text and line weights never shrink.
M against S
Width360 px480 px
Plot328 px440 px
Labels1926
Marks88
Height212 px246 px
Same tokens at every size: text styles, 1 px lines and mark radius stay put.
When to use
What each team is on.
Three signs it fits, and three signs another type fits better.
Is status more important than dates?
Exact times per job.
Yes: Keep the block timeline
Is it items, not ownership health?
Owners and health per item.
Yes: Keep the block timeline
Code and Figma
One name in Figma and in code.
Every Figma property is a prop with the same name and values. One command installs it.
Figma
chart/038-block-timeline
npx shadcn add @chartory/block-timelineimport { BlockTimeline } from "@/components/chartory/block-timeline"import { squadItems } from "./squad-items"export function SquadItems() { return ( <BlockTimeline data={squadItems} size="m" legend={true} /> )}Hearth widget
Block timeline as a widget.
The chart in a Hearth card with a hero number and two blocks. One token set, light and dark.
EmberPreset
ChartoryDefault preset
Pick the blocks, the size and the preset for your own widget.
Read the Hearth widget docsFAQ
Block timeline questions.
What people ask before they put a block timeline in a dashboard.
Something else?
hello@usechartory.comThe item's name and its status or days left (Usage alerts · 4 days left).
Shipped, in progress, blocked and planned, named in the legend.
One data object in the sample’s shape: items with a team, a status and days left. The docs page lists every field and links its JSON Schema; the sample data comes with the component, so you can start from it and swap in your own.
Series take the preset’s data colours in order, and states such as up, down or warning take its status colours. Change the preset in Figma or in code to recolour every chart at once.
XS, S, M and L, in light and dark. Each size is laid out again from the data, so text and lines keep their size.
Yes. It plays in when it scrolls into view, and when the data changes every mark moves from its old place to its new one. With reduced motion on, it does not move.
Yes. The React component is free in the public registry in Hearth, no token needed; Signal comes with Code and Complete. The Figma component comes with Figma and Complete.
Ask for it by name. The MCP server tells the agent what data it needs and runs the same command: npx shadcn add @chartory/block-timeline. You review the diff.
Related types
Other ways to show schedule and status.
The same question, a different shape of answer. Every type ships in Figma and in code.
Same family
Schedule and status
19 types in Chartory answer this question.