Members <member>
of a club’s leadership team are required to complete various tasks <task>
in support of the on-boarding process. E.g., the member needs to gain access to the club's documents, read certain policies, complete training courses, etc. Some of these tasks <task>
need to be renewed periodically. The Task Module
of the membertility system is designed to define these tasks <task>
and track the members' <member>
completion records.
This guide describes the concepts of the membertility Leadership Task Module, as well as gives guidance for how to configure the items in the Task Hierarchy
.
To facilitate task
assignment to members <member>
, a task hierarchy is defined. The leadership admin
creates positions <position>
and task groups <task group>
to facilitate management of sets of tasks <task>
.
- each
task
may be assigned to one or moretask groups <task group>
(Task Groups view
) - each
task group
may be assigned to one or morepositions <position>
(Task Groups view
,Positions view
) - each
position
may be be assigned to one or moremembers <member>
(Position Wizard
) tasks <task>
which follow themember
->position
->task group
->task
tree are displayed on thatmember's <member>
Task Checklist view
- digraph records {
graph [fontname = "helvetica"]; node [fontname = "helvetica"]; edge [fontname = "helvetica"]; "member 1" -> "position 1"; "member 2" -> "position 1"; "member 2" -> "position 2"; "member 3" -> "position 2"; "position 1" -> "task group 1"; "position 1" -> "task group 3"; "position 2" -> "task group 2"; "position 2" -> "task group 4"; "task group 3" -> "task group 2"; "task group 1" -> "task 1"; "task group 2" -> "task 1"; "task group 2" -> "task 2"; "task group 3" -> "task 1"; "task group 4" -> "task 2"; "task group 4" -> "task 3"; { rank=same; "member 1", "member 2", "member 3" }; { rank=same; "position 1", "position 2" }; { rank=same; "task group 1", "task group 3", "task group 4" }; { rank=same; "task 1", "task 2", "task 3" };
}
The system keeps track of a list of tasks <task>
for each member
, and that member's <member>
indication that they have completed each of a list of the tasks <task>
, and when it was completed.
tasks <task>
are displayed tomember
via theTask Checklist view
- using the
Task Checklist view
, themember
can select atask
, open an "view task" window, and click a button to mark thetask
as completed leadership admin
sets the attributes fortask
(e.g., conflict of interest may be required every other year, safe sport every year), to control thetask
status
and expiration behavior, as defined inTask Configuration Guide
tasks <task>
are generally displayed by urgency, e.g., if thetask
expires sooner it will be displayed closer to the top, but there is also a priority, which controls the order of display all things being equal
The Tasks view
is used to configure task
behavior.
Task <task>
status
and expiration is controlled using the attributes
- Period - how long after the
task's <task>
completion date when it become overdue - Date of Year -
task
becomes overdue on a date of year (e.g., March 3) if not marked completed - Overdue Starts - task remains up to date after Date of Year for this duration. Only applicable when Date of Year is set
- Expires Soon - how long before
task
expires that the status shows up as expires soon - Optional Task - if set to yes,
task
is suggested but not required, and does not expire
To configure a task
to be required periodically, but not on any specified date, set
- Period to the duration after completion that the
task
before the task expires - Expires Soon to the duration in advance of Expiration Date that the
task
should start showing expires soon - Optional Task to no
- leave Date of Year and Overdue Starts unset
To configure a task
to be required periodically by a specified date, set
- Date of Year to the date the
task
must be completed by - Overdue Starts to the duration after Date of Year during which the
task
remains up to date - Expires Soon to the duration in advance of Expiration Date that the
task
should start showing expires soon - Optional Task to no
- leave Period unset
To configure a task
to be required but done only once, set
- Optional Task to no
- leave Period, Date of Year, Expires Soon, and Overdue Starts unset
To configure a task
to be optional, set
- Optional Task to yes
- leave Period, Date of Year, Expires Soon, and Overdue Starts unset
To facilitate assignment of sets of tasks <task>
to individual members <member>
, tasks <task>
are assigned into one or more task groups <task group>
using the Task Groups view
.
See Position Management
for details on how to assign task groups <task group>
to positions <position>
and members <member>
to positions <position>
.
The leadership admin
needs to be able to see summaries of what tasks <task>
are outstanding in total and for individual members <member>
.
Member Summary view
- shows a summary oftask
completion bymember
Task Details view
- shows the details oftask
completion by allmembers <member>
, with appropriate filters for individualmembers <member>
,status
, etc.
The Member Summary view
shows a summary of the task
status
for each member
. From this view, the leadership admin
can select a member
, then view that member's <member>
details using the Task Details view
.
Each member
is shown tasks <task>
they are responsible for on their Task Checklist view
. The tasks <task>
which each member
is responsible for can be viewed by the leadership admin
on the Task Details view
.
When using Member Summary view
or Task Details view
, the task status
is displayed. These may be one of the following.
- overdue
task
should have been done by now, and needs to be completed- expires soon
task
will be becoming overdue shortly- optional
task
can be completed, but isn't required- up to date
required
task
has been completed, and does not need to be done untilexpiration date
- done
optional
task
has been completed
For those members <member>
who have not completed all their tasks <task>
, emails will be sent periodically to remind them what tasks <task>
are outstanding.
- individual emails are sent to
members <member>
who have overdue or upcomingtasks <task>
leadership admin
receives a summary email, separate from the individual emails mentioned above- the emails are sent every two weeks