Skip to content
shadcn.io

shadcn.io is not affiliated with official shadcn/ui

Capacity Planner Team Block for React

A capacity planner for an engineering team: six people as stacked bars, a segment per project and the free capacity as a muted track, with a slider for incoming work that draws a hatched piece in the free space of everyone who could take it.

Framework
UI library

Preview

Preview width

Installation

Part of Pro
Pro unlocks the code and one-line install of every Pro button and text effect, plus the MCP for your AI editor.
Have Pro already? Sign in to open it.Opens here as soon as you're Pro.

Overview

A capacity section for React with Base UI, for Thwaite, engineering planning, in a split with a divider. At the start: the header, a slider for incoming work in points with a line that counts who has room for it, and a legend of the three projects with their totals. At the end, a framed figure of six people, each a stacked bar: one segment per project in a foreground tone with its points written inside, and the rest of the person's capacity left as a muted track (part-timers have a shorter one, on the same scale). Slide the incoming work and a hatched piece appears in the free space of everyone who could take it; for those who can't, the row says how many points short they are. It's built from Slider, Avatar and Guides, with your theme's tokens for every colour. For planning pages, team dashboards and any hand-off between sprints.

FAQ

How do I change the people, the projects and the range?

Edit PROJECTS, PEOPLE, MAX_INCOMING and START_INCOMING at the top of the file. A person has a capacity in points and an allocation array with one number per project, in the order of PROJECTS. Free capacity, the legend's totals, the shared scale of the bars and who fits are all computed, so a new person or project needs no other edit.

How does the slider work with a keyboard and a screen reader?

It's a labelled slider ("Incoming work (points)") with a step of one: the arrow keys move by one, Page Up and Page Down by more, Home and End to the ends, and its value is read as "12 points". A polite line under it says how many people have room ("1 of 6 people have room for 12 points"), and each row says "Could take it" with a check, or "Short by 8" with a no-entry icon. A hidden sentence on every row reads its allocation by project.

How are the stacked bars read?

Each segment is a project in a tone of the foreground colour, darkest to lightest, with its points inside; the legend names the three. The muted remainder is free capacity and the hatched piece is the incoming work, in the space that is free. The bars are drawn and hidden from assistive technology; the row's text and its hidden sentence carry the same numbers, so no figure is only visible.

Why are some bars shorter?

Every track is drawn on one scale, the biggest capacity in the list, so a part-timer's 20 points really is a shorter bar than a full-timer's 32. That also keeps the hatched piece honest: the same number of points is the same length on every row.

Does the slider differ between libraries?

The slider is Base UI's, named through aria-labelledby with a hidden label, with its range and thumb in the foreground colour.

Wherever it runs, the value text, the step and the count of who fits behave the same.

How does it fit on a phone?

The copy and the slider come first, then the legend, then the six rows. Each row keeps the avatar, name and free capacity on one line with the bar under it; the bars shrink to fit and the numbers inside the segments stay readable. Nothing scrolls sideways at 320 pixels.

  • Pro

    Utilisation Bars Team

    Projects and workload

    Seven designers' utilisation as hairline rows with a bar under each name and one line through every bar at 85%, tasks and points beside it, a word and an icon for who is over the line, a team average and a switch that sorts by load or by name.

  • Pro

    Velocity Chart Team

    Projects and workload

    Six sprints of a QA team's velocity as paired bars (planned in a hatched outline, delivered solid, with a dashed average), a button per sprint that drives the figures and the five engineers' rows below, each opening its tickets and share.

  • Pro

    Accordion Projects Team

    Projects and workload

    Four projects of a build-planning tool as a single-open accordion beside four counted figures: each row shows a name, a stack of initials, the people, the full-time equivalents and a deadline as a week, and opens to a table of roles and time.

  • Pro

    Weekly office hours of a pair-programming service: five day tabs, each with three engineers' half-hour slots as pills, and a single Shine Button that reads 'Book Thu 14:00 with Noor' once a slot is picked.

  • Pro

    Bullet Chart Stats

    Bar and column

    Four bullet graphs for department KPIs, each with three shaded ranges, a bar for the result, a tall tick for the target, a labelled scale and a verdict with a glyph and words.

  • Pro

    Swimlane Projects Team

    Projects and workload

    One person's next twelve weeks as swimlanes: three projects as bars with the role inside and a status word at the end, a shaded column for this week and a last lane that adds up the time per week, with a table of the same facts on a phone.