# Capacity Overview & Quick Reference

## Key Concepts: Manifests and Legs

In CustomLinc, a **manifest** represents the overall service (e.g. the 11:00 Bel-Lak-Gem / 15:05 Gem-Lak-Bel service). It appears as a **green highlighted row** in the Manifests view. Within each manifest, individual **legs** represent each segment of that journey — for example, Belgrave to Lakeside, or Lakeside to Gembrook. Legs appear as indented grey rows beneath the manifest.

[![image.png](https://bookstack.pbr.org.au/uploads/images/gallery/2026-05/scaled-1680-/5M5image.png)](https://bookstack.pbr.org.au/uploads/images/gallery/2026-05/5M5image.png)Changing capacity at the *manifest level* flows down and updates the relevant legs automatically. However, the **Belgrave – Gembrook Allocation (Return)** leg is a special product and must be adjusted separately using a different procedure.

---

## Quick Reference Guide

<table id="bkmrk-what-you-want-to-cha"><thead><tr><th>What you want to change</th><th>Where to right-click</th><th>Key settings</th><th>Extra step?</th></tr></thead><tbody><tr><td>All Return service (Excl. Bel-Gmb) or single-journey capacity  
  
</td><td>Green manifest row</td><td>Set max Pax to…</td><td>No — legs update automatically</td></tr><tr><td>Belgrave–Gembrook Return capacity  
*(typically 56)*</td><td>Belgrave – Gembrook Allocation (Return) leg row</td><td>Set max Pax to… **and** Set Allocation on Allocation Groups</td><td>Yes — set Allocation Group to match</td></tr></tbody></table>

---

## Maintenance Notes

- Review and update capacities whenever rolling stock or service configurations change.
- Always verify leg capacity figures after making changes to confirm they have applied correctly.