The project team
The Team view, under Work on the project page, is about people rather than work. It answers who is on this project, what each of them can do, and whether the work already planned on them adds up to something a human can actually deliver. Its three tabs are Members, Workload and Skills.
Membership is explicit​
A project's teamProject teamThe explicit list of resources on a project, maintained in its Team view with their skills and weekly workload. Membership is declared, not inferred from who has appointments. is a list you maintain, not something inferred from who happens to have appointments.
That distinction does more than it looks. It means somebody can be on the team before any work is assigned to them, which is what makes this view useful for planning rather than only for reporting: you can staff a project and then plan it, instead of discovering the team by looking at what was already planned.
Members lists the team, busiest first, with the hours each person has planned on this project and a bar relative to the busiest member. The range picker beside the tabs limits those hours to a period. Use Add member to add anybody, and the row actions to change a member's dates or remove them. Membership is per project, so the same resourceResourceAn entity that can carry out work - a person, vehicle, tool, or room - that you schedule on the planning board. can be on several.
People who have appointments on the project without being members are listed separately as Tentative members. They are doing the work but nobody has confirmed them, and Add to team makes them members.
Workload​
Workload answers whether the team can carry what is planned. It has one row per person and one column per week, each cell showing that person's planned work against their capacityCapacityThe amount of working time a resource has available in a given period, used to spot over- and under-planning.. A cell counts everything planned on the person, not only this project: their work on Other projects and their work without a project weigh on the same week. Tentative work counts too and is hatched, so you can tell which part is not confirmed yet. A cell above capacity is red; exactly full is not over. A week without capacity records shows the planned hours but no percentage.
It counts planned work only, the appointments on the boards. A task that is assigned to someone but not planned yet is not load until it is planned.
Under the people, the Whole team rows add the team up per week, the way the Team capacity health rule counts it: Planned, Capacity and Team load, shaded by that rule. Weeks after the project's end are shown but not counted. Somebody who is a member but not planned on the project inside that window is shown without being counted, which the row's hint explains.
The view opens on the busiest person's busiest week. Picking any cell shows what fills it underneath: the hours on this project, on other projects and without a project against the capacity, the week day by day, and the tasks behind it. Open on the board jumps to the planning board for that person and week, which is usually where an overload gets fixed. The Resources card and the resource rules on the project's Overview link straight here with See workload.
Skills​
Skills shows one card per member with the skillsSkillA qualification a resource holds and a task can require, typically modeled as a filter group. Skills drive resource filtering, the project team view and the solver’s choice of who can do what. and attributes recorded against them, grouped the way they are grouped on the resource, so you can see what the team collectively brings and where it is thin. A member with nothing recorded shows as having no skills, which usually means the attributes were never set on the resource rather than that the person cannot do anything.
This is the view to use when a project needs a capability nobody on it has. It is faster than opening resources one at a time to find out.
Related​
- Crews - for people who always work together, a crewCrewA resource that stands for a group of other resources. Dropping work on a crew fans the booking out to every member, which suits people who always work together. assigns them as one.
- Resources - where skills and attributes are maintained.
- Capacity - the capacity records the workload is measured against.