Skip to content
shadcn.io

shadcn.io is not affiliated with official shadcn/ui

Utilisation Bars Team Block for React

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.

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 workload section for React with Base UI, for Appleby, a design-ops tool. A compact header says what the bars mean, and a tinted band under it holds two facts worked out from the data (the team's average and how many people are over the line) and a Segment Group that sorts the rows by load or by name. The rows run from rail to rail and end the block. Each is an initials avatar, a name, a role, the tasks and points the person carries out of their capacity, the share of that capacity in use, and a bar under the name. One thin line runs through every bar at 85%, the level above which the team agrees work starts to slip; a bar past it is solid and says "Over 85%" with a warning icon, one under it is a lighter tone and says "Within" with a check. It's built from Segment Group, Progress, Avatar and Guides. For design and delivery pages, operations reviews and capacity check-ins.

FAQ

How do I change the people and the threshold?

Edit PEOPLE and THRESHOLD at the top of the file. A person is a name, a role, their tasks, the points they carry now and their capacity in points; utilisation is points over that person's own capacity, so a part-timer with less capacity is measured fairly. The team average, the count over the line, each bar and the line itself all follow from these.

How is the line drawn through every bar?

Each row draws a one-pixel segment at the threshold across its own bar and a little past it, so the segments join into one continuous line down the list; the line passes behind the percentage and status text rather than through it. A label above the first row names it. The bars and the line are hidden from assistive technology, and the percentage and status are written as text.

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

The control is a radio group named Sort by, with Load and Name: Tab moves into it and the arrow keys move between the options, choosing as they go. A polite status line says what happened ("Sorted by load, Devi Kapoor first"). Load puts the heaviest first; Name is A to Z. Re-sorting moves the rows but the block keeps its height.

Why does the status say Over 85% or Within instead of a colour?

Colour is kept for the page's one call to action. A bar over the threshold is the full foreground tone with a warning-triangle icon and the words "Over 85%"; one within it is a lighter tone with a check and "Within". The numbers are written too, so nothing relies on seeing the bar.

What moves, and what happens with reduced motion?

The block fades up once on load and the team average rolls to its number once when it comes into view; the bars are drawn at their values. With reduced motion the fade is off and the average shows its final number.

How does it fit on a phone?

The band stacks its facts above the sort control. Each row keeps the avatar, the name block (role, tasks and points) and the percentage with its status at the end, and the bar spans the full width under the name. The 85% line and its label stay aligned from row to row, and nothing scrolls sideways at 320 pixels.

  • Pro

    Capacity Planner Team

    Projects and workload

    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.

  • 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

    Skill Bars Team

    Skills and expertise

    A picker of five e-learning specialists beside a framed figure of five skill bars: choosing a person fills the bars to their scores, each with its number and a tick for the team average on its track.

  • Pro

    Five support metrics, each on a scale line with three markers (your team as a solid dot, the industry average as a ring, the top 10% as a tick), a verdict with a glyph and words, and the three values as text.

  • Pro

    Fourteen daily bars against a labelled quota line in a framed chart, days at or above the quota solid and days below it outlined, with a two-cell band under it for days met and the average against the quota.

  • Pro

    Status Filter Team

    Hours and places

    A live-chat widget's eight people in rows under a ruled pill filter (All, Online, Away, Busy) with counts, each row showing a presence dot, what they are doing and when they were last seen.