# The best chart for schedules and status

> Nineteen charts, and when each one fits.

**Short answer.** For who is busy when, use a Gantt chart. For each item's window, use floating range bars. For every event in time, use an event barcode. For status day by day, use uptime bars; for a team's items and their status, a block timeline.

Updated Nov 2, 2026 · Logistics sample data

## 037 · Gantt

One lane per dock: dock 5 is busy the longest, 4 h 00 min.

Truck bookings at six docks, today, 06:00 to 14:00. Twelve bookings in one lane per dock, 06:00 to 14:00; dock 5 is busy the longest, 4 h 00 min; delayed: TR-112 at dock 2 and TR-190 at dock 6.

| Truck | Dock | Start | End | State |
| --- | --- | --- | --- | --- |
| TR-104 | 1 | 06:00 | 07:30 | Unloading |
| TR-131 | 1 | 08:00 | 09:15 | Loading |
| TR-220 | 2 | 06:30 | 08:00 | Loading |
| TR-112 | 2 | 08:30 | 10:30 | Delayed |
| TR-217 | 3 | 07:00 | 08:45 | Unloading |
| TR-236 | 3 | 09:30 | 11:00 | Loading |
| TR-145 | 4 | 06:15 | 07:45 | Loading |
| TR-251 | 4 | 10:00 | 11:30 | Unloading |
| TR-162 | 5 | 07:30 | 10:00 | Loading |
| TR-178 | 5 | 11:00 | 12:30 | Unloading |
| TR-190 | 6 | 08:15 | 09:30 | Delayed |
| TR-244 | 6 | 12:00 | 13:30 | Loading |

## 005 · Floating range bars

The same twelve trucks as windows, start to end.

Truck windows, start to end. Each truck's booking window; TR-112 (120 min), TR-217 (105 min), TR-162 (150 min) run over 90 minutes.

| Truck | Start | End | Minutes |
| --- | --- | --- | --- |
| TR-104 | 06:00 | 07:30 | 90 |
| TR-131 | 08:00 | 09:15 | 75 |
| TR-220 | 06:30 | 08:00 | 90 |
| TR-112 | 08:30 | 10:30 | 120 |
| TR-217 | 07:00 | 08:45 | 105 |
| TR-236 | 09:30 | 11:00 | 90 |
| TR-145 | 06:15 | 07:45 | 90 |
| TR-251 | 10:00 | 11:30 | 90 |
| TR-162 | 07:30 | 10:00 | 150 |
| TR-178 | 11:00 | 12:30 | 90 |
| TR-190 | 08:15 | 09:30 | 75 |
| TR-244 | 12:00 | 13:30 | 90 |

## 061 · Event barcode

The same bookings as arrivals in time, one row per dock.

Booking starts by dock. One mark per booking start, one row per dock, 06:00 to 14:00: dock 1 at 06:00 and 08:00; dock 2 at 06:30 and 08:30; dock 3 at 07:00 and 09:30; dock 4 at 06:15 and 10:00; dock 5 at 07:30 and 11:00; dock 6 at 08:15 and 12:00.

| Truck | Dock | Start | End | State |
| --- | --- | --- | --- | --- |
| TR-104 | 1 | 06:00 | 07:30 | Unloading |
| TR-131 | 1 | 08:00 | 09:15 | Loading |
| TR-220 | 2 | 06:30 | 08:00 | Loading |
| TR-112 | 2 | 08:30 | 10:30 | Delayed |
| TR-217 | 3 | 07:00 | 08:45 | Unloading |
| TR-236 | 3 | 09:30 | 11:00 | Loading |
| TR-145 | 4 | 06:15 | 07:45 | Loading |
| TR-251 | 4 | 10:00 | 11:30 | Unloading |
| TR-162 | 5 | 07:30 | 10:00 | Loading |
| TR-178 | 5 | 11:00 | 12:30 | Unloading |
| TR-190 | 6 | 08:15 | 09:30 | Delayed |
| TR-244 | 6 | 12:00 | 13:30 | Loading |

**Same 12 trucks.** The Gantt shows the load per dock, the range bars each truck's window, and the barcode when trucks arrive. Two trucks are delayed: TR-112 at dock 2 and TR-190 at dock 6.

## If you ask

| Question | Use a |
| --- | --- |
| Who is busy when? | 037 · Gantt |
| What is each item's window? | 005 · Floating range bars |
| When did each event happen? | 061 · Event barcode |
| How reliable was each day? | 070 · Uptime bars |
| What is each team on? | 038 · Block timeline |
| Who is on call? | 123 · Rota lanes |

## All nineteen

| Type | Use it when | Data shape |
| --- | --- | --- |
| [037 · Gantt](https://usechartory.com/charts/gantt) | Who is busy when, lane by lane | Jobs with a lane, a start, an end and a state |
| [038 · Block timeline](https://usechartory.com/charts/block-timeline) | Each team's items and their status | Items with a team, a status and days left |
| [052 · Radial hour heatmap](https://usechartory.com/charts/radial-hour-heatmap) | A week of hours around a clock | A value per weekday and hour |
| [061 · Event barcode](https://usechartory.com/charts/event-barcode) | Every event as a thin line, by service | Per row: a count, error and slow shares, and an hourly pattern |
| [067 · Marey schedule](https://usechartory.com/charts/marey-schedule) | Vehicles moving through stops, against the plan | Times at each stop per vehicle |
| [070 · Uptime bars](https://usechartory.com/charts/uptime-bars) | Each day of each service, as a bar | A status per service per day |
| [079 · Milestone track](https://usechartory.com/charts/milestone-track) | How many reach each milestone, and when | Milestones with a day and a share reached |
| [086 · Punch card](https://usechartory.com/charts/punch-card) | Activity by weekday and hour, as sized dots | A share of the busiest hour (0 to 1) per weekday and hour |
| [092 · Tachograph](https://usechartory.com/charts/tachograph) | A driver's day in driving, other work, rest and availability | Activity spans per driver over 24 hours |
| [099 · Pass/fail grid](https://usechartory.com/charts/pass-fail-grid) | Every model against every test | A result per item and test |
| [100 · Split calendar](https://usechartory.com/charts/split-calendar) | Money in and out, day by day | In and out per day |
| [103 · Weekly rhythm](https://usechartory.com/charts/weekly-rhythm) | A week of runs, by day and hour | A share of the busiest hour (0 to 1) per weekday and hour |
| [107 · Span waterfall](https://usechartory.com/charts/span-waterfall) | One run's steps, and where the time went | Steps with a start and a length |
| [120 · Key timeline](https://usechartory.com/charts/key-timeline) | API keys, their use and when they expire | Keys with use per day, expiry and events |
| [122 · Ownership matrix](https://usechartory.com/charts/ownership-matrix) | Each agent's parts, owners and health | A state per item and part |
| [123 · Rota lanes](https://usechartory.com/charts/rota-lanes) | Who is on call, and for how long | Shifts with a person, a start and an end |
| [124 · Replay lanes](https://usechartory.com/charts/replay-lanes) | Where each alert went: pager, chat or digest | Alerts with a time and a route |
| [125 · Session lanes](https://usechartory.com/charts/session-lanes) | Every signed-in device, over time | Sessions per device with a state |
| [131 · Alert fire strip](https://usechartory.com/charts/alert-fire-strip) | Each alert rule, how often it fired and if anyone acted | Fires per rule per day, and the share acted on |

## Common mistakes

- **One lane per job** Put jobs on one lane per resource, so clashes and gaps show.
- **A timeline with no now line** Mark now, so done and to-come read at once.
- **Status colours with no legend** Name every state, especially delayed.

## Every schedule and status chart, and the other 113 types.

In Figma and React, in four sizes, light and dark. Pay once, every update. [See the nineteen in Charts](https://usechartory.com/charts#schedule-and-status)

## Questions

### Gantt or block timeline?

A Gantt for clock times, a block timeline for status over weeks.

### Can a Gantt show dependencies?

Draw the order in the data; the chart places each job by its start and end.

### How many lanes fit?

Six to twelve on a card.

### Do these charts come in every size?

Yes. All of them come in XS, S, M and L, each laid out again for its size, in light and dark.

## Other questions

- [Change over time](https://usechartory.com/questions/change-over-time)
- [Compare items](https://usechartory.com/questions/compare-items)
- [Part of a whole](https://usechartory.com/questions/part-of-a-whole)
- [Distribution](https://usechartory.com/questions/distribution)
- [Flow between steps](https://usechartory.com/questions/flow-between-steps)
- [Relationship](https://usechartory.com/questions/relationship)
- [Space and place](https://usechartory.com/questions/space-and-place)

Not sure it is a schedule or a status? Start from what the chart has to show. [Open the Chart Chooser](https://usechartory.com/chooser)