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.
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.
How Capacity is Structured
Each leg on a Belgrave–Gembrook service has a total capacity of 176 passengers, made up of two components:
| Component | Capacity | Notes |
|---|---|---|
| Bel - Lak & Lak - Gmb Return / single-journey passengers | 120 | Covers Bel–Lak, Lak–Gem, and return equivalents |
| Belgrave – Gembrook Allocation (Return) | 56 | Full return journey product; seats are reserved via Allocation Groups |
| Total per leg | 176 |
Note: The 56 Belgrave–Gembrook Return passengers are already counted within each leg's 176-seat capacity. Adjusting the Return allocation changes how many of those 176 seats are reserved for that product specifically.
Quick Reference Guide
| What you want to change | Where to right-click | Key settings | Extra step? |
|---|---|---|---|
| Bel - Lake & Lake - Gmb Return or single-journey capacity (Bel–Lak, Lak–Gem, Gem–Lak, Lak–Bel) |
Green manifest row | Set max Pax to… | No — legs update automatically |
| Belgrave–Gembrook Return capacity (typically 56) |
Belgrave – Gembrook Allocation (Return) leg row | Set max Pax to… and Set Allocation on Allocation Groups | Yes — set Allocation Group to match |
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.
- If the Allocation Group value and max Pax become mismatched, the system may accept bookings beyond the intended limit. Always tick "Set Allocation on Allocation Groups" for any Part B changes.