Shared coverage

Two tasks that run side by side often use the same crew: the same four finishers pour the deck and then strip it. Counted task by task, that looks like eight people. Shared coverage tells Ganttry that those tasks share their people and machines, so every count reads them once.

What a coverage set is#

A coverage set is a named set of tasks, inside one project, that draw on the same trade or machine. You build it by hand. Ganttry never guesses from matching names: two tasks that happen to need the same trade in the same week stay separate crews until you say otherwise.

While tasks are in a set, the requirement for each trade or machine type, on each working day, is the highest requirement among the set's own tasks that day. You can set your own number for a trade instead; clearing it goes back to Automatic, the computed number.

Where to find it#

Shared coverage is built on the Schedule tab of a project:

• Tools ▾ → Shared coverage… lists the project's coverage sets. Each has Edit…; + New set… starts a new one.
• Or select the tasks in the grid, right-click, and choose Shared coverage…. The set opens with those tasks in it, or, if they are already in a set, that set opens.

Making a set#

The set's dialog has a Name and three parts:

• TASKS: the tasks in the set. + Add tasks… adds more; each row can be removed. A task belongs to one set at a time; adding a task that is already in another set asks before moving it.
• SHARED PEOPLE AND MACHINES: + Assign people and machines… picks the people and machines these tasks share. Picking one here fills every task in the set that needs that trade or type. Only what you pick here is shared; everything else on these tasks stays on its own task.
• DAILY REQUIREMENTS: one row per trade or type. Leave a row empty for Automatic, the highest requirement among the tasks in the set, or type your own whole number.

Save keeps the set. A set needs a name and at least one task.

What it changes#

Every place that counts crew and equipment reads the same shared number:

• the Crew & equipment demand report, its PDF, workbook and copied text;
• the Crew & equipment lookahead;
• the Gantt crew band and Crew planning.

A member task's Crew cell carries a small brace mark; hover it for the set's name. Its crew popup and the task pane on Work read the shared people once, for example 2 of 2 filled · 1 more from Deck pour crew, instead of counting a person twice.

Someone booked on People for only some of a task's days is shared only on those days. Once anyone in a set is booked that way for a trade, a member's crew popup and Work pane read that trade on the day with the most still to fill.

Double-booking warnings between the set's own tasks stop, because those people are meant to be on both. Every other conflict still flags as before: a shared person on an unrelated task, or a clash across projects.

What it never touches#

• task dates, dependencies, or each task's own crew and equipment line. A task still prints its own line everywhere it already printed;
• the cross-project conflicts on the Resource assignments board;
• the Have column on Crew planning;
• the schedule quality checks for unfilled requirements. A task with a short line of its own still flags, in a set or not.

Ungroup#

Ungroup in the set's dialog dissolves the set. It asks first and says what changes, for example "Laborer goes from 4 a day to 8. Nobody is unassigned; every task keeps its own people and machines." Every task's own number comes back at once. Nobody was ever unassigned: a coverage set never removes a fill, it only changes how the numbers are read while the set stands.

Who can use it#

Anyone who can edit the project's schedule; Field accounts can't. Picking shared people and machines needs a connected company with its roster and fleet on Roster & equipment. See Who can see and do what.

Good to know#

• A coverage set lives inside one project; it can't join tasks from two projects.
• A project can have up to 40 coverage sets, a set up to 200 tasks, and up to 40 shared people and machines.
• My tasks still lists each task's own crew line, not the shared count; the Calendar and the Work page's cards show no crew count at all.