Skip to content

New: Chartory 1.0. 100 charts free in React, MIT licensed

Read the changelog

Charts / Questions

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

Truck bookings at six docks, today, 06:00 to 14:00Twelve 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.06:0008:0010:0012:0014:00Dock 1Dock 2Dock 3Dock 4Dock 5Dock 6104131220112217236145251162178190244LOADINGUNLOADINGDELAYED
Truck bookings at six docks, today, 06:00 to 14:00
TruckDockStartEndState
TR-104106:0007:30Unloading
TR-131108:0009:15Loading
TR-220206:3008:00Loading
TR-112208:3010:30Delayed
TR-217307:0008:45Unloading
TR-236309:3011:00Loading
TR-145406:1507:45Loading
TR-251410:0011:30Unloading
TR-162507:3010:00Loading
TR-178511:0012:30Unloading
TR-190608:1509:30Delayed
TR-244612:0013:30Loading

037 · GanttOne lane per dock: dock 5 is busy the longest, 4 h 00 min.

Truck windows, start to endEach truck's booking window; TR-112 (120 min), TR-217 (105 min), TR-162 (150 min) run over 90 minutes.14:0012:0010:0008:0006:00104131220112217236145251162178190244WITHIN 90 MINOVER 90 MIN
Truck windows, start to end
TruckStartEndMinutes
TR-10406:0007:3090
TR-13108:0009:1575
TR-22006:3008:0090
TR-11208:3010:30120
TR-21707:0008:45105
TR-23609:3011:0090
TR-14506:1507:4590
TR-25110:0011:3090
TR-16207:3010:00150
TR-17811:0012:3090
TR-19008:1509:3075
TR-24412:0013:3090

005 · Floating range barsThe same twelve trucks as windows, start to end.

Booking starts by dockOne 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.Dock 1Dock 2Dock 3Dock 4Dock 5Dock 606:0008:0010:0012:0014:00LOADINGUNLOADINGDELAYED
Booking starts by dock
TruckDockStartEndState
TR-104106:0007:30Unloading
TR-131108:0009:15Loading
TR-220206:3008:00Loading
TR-112208:3010:30Delayed
TR-217307:0008:45Unloading
TR-236309:3011:00Loading
TR-145406:1507:45Loading
TR-251410:0011:30Unloading
TR-162507:3010:00Loading
TR-178511:0012:30Unloading
TR-190608:1509:30Delayed
TR-244612:0013:30Loading

061 · Event barcodeThe same bookings as arrivals in time, one row per dock.

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

All nineteen

TypeUse it whenData shape
037 · GanttWho is busy when, lane by laneJobs with a lane, a start, an end and a state
038 · Block timelineEach team's items and their statusItems with a team, a status and days left
052 · Radial hour heatmapA week of hours around a clockA value per weekday and hour
061 · Event barcodeEvery event as a thin line, by servicePer row: a count, error and slow shares, and an hourly pattern
067 · Marey scheduleVehicles moving through stops, against the planTimes at each stop per vehicle
070 · Uptime barsEach day of each service, as a barA status per service per day
079 · Milestone trackHow many reach each milestone, and whenMilestones with a day and a share reached
086 · Punch cardActivity by weekday and hour, as sized dotsA share of the busiest hour (0 to 1) per weekday and hour
092 · TachographA driver's day in driving, other work, rest and availabilityActivity spans per driver over 24 hours
099 · Pass/fail gridEvery model against every testA result per item and test
100 · Split calendarMoney in and out, day by dayIn and out per day
103 · Weekly rhythmA week of runs, by day and hourA share of the busiest hour (0 to 1) per weekday and hour
107 · Span waterfallOne run's steps, and where the time wentSteps with a start and a length
120 · Key timelineAPI keys, their use and when they expireKeys with use per day, expiry and events
122 · Ownership matrixEach agent's parts, owners and healthA state per item and part
123 · Rota lanesWho is on call, and for how longShifts with a person, a start and an end
124 · Replay lanesWhere each alert went: pager, chat or digestAlerts with a time and a route
125 · Session lanesEvery signed-in device, over timeSessions per device with a state
131 · Alert fire stripEach alert rule, how often it fired and if anyone actedFires 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.

Get all nineteen

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

See plans

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.

Not sure it is a schedule or a status? Start from what the chart has to show.

Open the Chart Chooser