Short answer: the Gantt chart lays activities against time as horizontal bars, sized by duration, so schedules, overlaps and dependencies become visible. In a brewery it’s the brew and packaging schedule, tank and fermenter occupancy, and the new-product project timeline — anywhere two things might collide over the same vessel or week. Its strength is showing duration and overlap across parallel tracks; its weakness is going stale the moment the plan changes, so keep it connected to real data.
Part of The Brewer’s Chart Field Guide. It’s the scheduling chart — time on one axis, resources or tasks stacked on the other.
When to reach for it
Reach for a Gantt when you’re placing activities on a timeline and overlap or sequence matters — when the question is “what runs when, and does anything collide.” Bars sized by duration make clashes and critical paths jump out.
Use case 1 — Tank and vessel occupancy
Rows for fermenters and bright tanks, bars for each batch’s residency. The Gantt instantly shows where two batches want the same vessel in the same week — the single most useful scheduling view a planning brewer has.
Use case 2 — The brew and packaging schedule
Brew days, fermentation, conditioning and packaging runs laid against the calendar across the brewhouse and line. Dependencies (you can’t package before it’s conditioned) become visible, and gaps reveal under-used capacity.
Use case 3 — The NPD project timeline
For a new product, the stages from recipe trials through pilot, scale-up and launch as a Gantt. It keeps a cross-functional beer NPD project honest about what must finish before launch.
Where this breaks
Staleness — a static Gantt is wrong the moment the plan shifts; connect it to live data or it misleads. Complexity — many vessels and batches crowd fast; filter to a horizon or a resource group. Not a utilisation number — it shows time and overlap, not capacity %; for that, use a bar or heat map. Over-detailed — a Gantt of every micro-task is unreadable; show the activities that actually clash or gate.
The bottom line
The Gantt chart shows activities against time with duration and overlap — tank occupancy, the brew/packaging schedule, the NPD timeline — making clashes and critical paths visible at a glance. Keep it connected to real data, filtered to a sensible horizon, and reserve a different chart for pure utilisation. Last in the field guide’s specialized set: spatial data, the geographic map.
Frequently asked questions
When should a brewery use a Gantt chart? When you’re scheduling activities against time and overlaps and dependencies matter — the brew and packaging schedule, tank or fermenter occupancy, or a new-product project timeline. Each task is a horizontal bar positioned and sized by its start and duration, so clashes (two brews needing the same vessel) and critical paths become visible.
What is a Gantt chart good at that a calendar isn’t? Showing duration and overlap across many parallel tracks at once. A calendar shows what’s on a given day; a Gantt shows how long each activity runs and where activities collide across resources — ideal for spotting that two beers both need the bright tank in week three. For simple day-by-day scheduling a calendar may be plenty.
What is the weakness of a Gantt chart for brewing? It can become complex fast — many vessels, many batches, shifting durations — and a static Gantt goes stale the moment the schedule changes. It also shows time and duration well but not capacity utilisation as a number. For live scheduling, a Gantt needs to be connected to real data, and for pure occupancy percentages a different chart is clearer.