Skip to content

Load bars

Who owns how much, by kind of work.

Definition · Updated Nov 2, 2026

Load bars show how many items each person owns, split by kind, against the team average. Overloaded people and work with no owner stand out. Use it for ownership of agents, prompts, alerts and keys, or any team workload.

Pay once. Every update included.

Live preview

Owned objects per personObjects owned per person, from 22 (maya) down to 2; team average 13.3. 5 objects have no owner and are suggested to ana (+1), leo (+2), dev (+2).NO OWNERMAYAANALEODEVPRIYASARATOM52216+115+213+21192TEAM AVERAGE 13.3AGENTSPROMPTSEVAL SUITESALERT RULESAPI KEYSNO OWNER
Owned objects per person
PersonAgentsPromptsEval suitesAlert rulesAPI keysTotalSuggested
MAYA6544322
ANA1643216+1
LEO2128215+2
DEV3242213+2
PRIYA3223111
SARA223119
TOM110002

Sample data: items per owner across agents, prompts, eval suites, alert rules and API keys, team average 13.3

Size
Legend
Data shape
Items per person, split by kind
Good for
Ownership, workload, on-call load
Avoid when
There is no owner field
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

126 / Load bars

chart/126-load-bars
plot · load bars
Layer
part · maya · agents
Type
Rectangle
Size
157 × 14
Fill
data/cat-2
Radius
2
Group
Marks · 43

Layers

126 / Load bars

chart/126-load-bars
plot · load bars
Layer
unowned · 0
Type
Rectangle
Size
7 × 7
Fill
status/warning
Radius
2
Group
Marks · 43

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

Labels2020

Marks4343

Height212 px246 px

Same tokens at every size: text styles, 1 px lines and mark radius stay put.

When to use

Who carries the load.

Three signs it fits, and three signs another type fits better.

Is it per person?

Per item, with health.

Yes: Keep the load bars

Is the split by kind needed?

One count per person.

Yes: Keep the load bars

Is there an average to compare?

Plain totals.

Yes: Keep the load bars

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/126-load-bars

size
legend
Property = propValuesDefault
size"xs" · "s" · "m" · "l""xs"
legendtrue · falsetrue
color"cat-1" · "cat-2" · "cat-3" · "cat-4""cat-1"
npx shadcn add @chartory/load-bars
load-bars.tsx
import { LoadBars } from "@/components/chartory/load-bars"import { ownerLoad } from "./owner-load"export function OwnerLoad() {  return (    <LoadBars      data={ownerLoad}      size="m"      legend={true}    />  )}

Hearth widget

Load bars as a widget.

The chart in a Hearth card with a hero number and two blocks. One token set, light and dark.

Get the code

EmberPreset

ChartoryDefault preset

Pick the blocks, the size and the preset for your own widget.

Read the Hearth widget docs

FAQ

Load bars questions.

What people ask before they put load bars in a dashboard.

Something else?

hello@usechartory.com
  • Items nobody owns, listed first so they get picked up. It has its own colour in the legend.

Related types

The same question, a different shape of answer. Every type ships in Figma and in code.

Same family

Part of a whole

16 types in Chartory answer this question.