# Gantt: resource load Who is on each task, and whether anyone is booked twice over. An Enterprise option on `GanttProConfig`: `resourceField` names the assignee, and `resourceHistogram` sums the assignments into a load strip under the chart. ```svelte ``` ## Naming the resource `resourceField` on its own puts the assignee in the tooltip and gives the histogram something to count: ```svelte r.id} gantt={pro({ startField: 'start', endField: 'end', parentField: 'parentId', resourceField: 'owner', tooltip: true, })} /> ``` ## The load strip `resourceHistogram` sums the assignments into a strip under the chart - one row per resource, one bar per axis column, counting the tasks that touch it, with anything past capacity in red. `true` takes the defaults (a capacity of one, 88 px tall); the object form names the capacity field on each resource and sets the strip's height. ```svelte r.id} gantt={pro({ startField: 'start', endField: 'end', parentField: 'parentId', resourceField: 'owner', resources: crews, resourceHistogram: { capacityField: 'cap', height: 80 }, editable: true, onTaskMove: (e) => writeSpan(e.row, e.start, e.end), onTaskResize: (e) => writeSpan(e.row, e.start, e.end), })} /> ``` Drag a task onto a column that is already full and the bar under it goes red; the strip recomputes with every edit. It sticks to the bottom of the chart and scrolls with the axis, so a column and its load are always in line. ## How a cell is counted A cell's number is **how many of that resource's tasks overlap the column**, not an average and not person-hours. On a day or week axis that is exactly concurrency; on a coarser one it counts everything touching the column, which reads high rather than low. Only **leaves** are counted - a phase is its children, so counting it too would book its owner twice for the same work. `resources` is the ordered list of who to show, as `{ id, title, ... }` - the same shape the [scheduler](https://svgrid.com/docs/help/rows/scheduler/) uses, so one array can serve both views. Omit it and the rows come from the data, in the order the tasks first name them, each with a capacity of one. A resource in the list with no tasks still gets a row, which is how an idle crew shows up. ## A field-service quarter Two regional crews and one specialist, with a capacity of two for the crew that runs two vans, and the weekends folded out of the axis: > Live demo: Resource load & folded axis - https://svgrid.com/demos/477-gantt-resources/ The portfolio console turns the same numbers into a chart - remaining working days per owner - from the rows alone, without the strip: > Live demo: Portfolio office - project console - https://svgrid.com/demos/481-gantt-portfolio-console/ ## See also - [Critical path, baselines and constraints](https://svgrid.com/docs/help/gantt/critical-path/) - the rest of the planning layer. - [Staffing board](https://svgrid.com/docs/help/rows/scheduler/) - the scheduler's utilization histogram, for shifts rather than tasks. - [Config reference](https://svgrid.com/docs/help/gantt/api/#gantt-pro) - the Pro options in one table. --- SvGrid is the Svelte 5 data grid (`npm install @svgrid/grid`, MIT). This page: https://svgrid.com/docs/help/gantt/resources/ . All docs: https://svgrid.com/llms.txt