The Meeting module assists to organise, and track meetings that may occur in your organisation. This document provides guidance on how the module works, options for configuration, and actions required to complete your configuration requirements for implementation.

Your Implementation Manager will share the timeframes for completing this workbook in the project plan.

Each key feature mentioned below builds upon the last diagram to build understanding before the ‘bringing it all together’ diagram which shows all features and the flow of the module.

The Workflow outlines the key stages that a module works through and is used as the framework for other aspects of the build. Each key stage is represented by a bubble icon and any relevant checks that may interact with the flow written on the progress lines.

Involvements capture the People Involved in the Meeting. This includes the Creator of the record, the minute taker and attendees as the owners of task (above the workflow); and other involvements (below the workflow).

These are represented by the addition of the blue person boxes below (also known as swim lanes).

Areas where users can input information are called forms and usually contain a list of questions. The Main Form is the starting point of a user’s interaction with the module and all other forms are called Subforms. Forms are represented by the Page Icons added below and align under the person/stage completing the forms.

This module includes Notifications and Actions to assist your users to successfully action and resolve records. All notifications, including being advised of an action that has been set, are emailed to the relevant person.

In our flow diagram, Notifications and Actions are represented by the below icons:

module to provide a visual reference on the record page and in registers.

The meetings module aims to achieve a best practice solution however we understand that each client is unique. The following configuration can accommodate your unique needs:

Configuration options are referred to as ‘Configuration Requirements’. Further information on how to complete your Configuration Requirements is outlined in the next section.

After the walkthrough of the Meeting module, you will be provided access for a more in-depth look. We encourage you to take this opportunity to review the specifics of the module and complete the configuration requirements below.

The additional “Question Guidance” document provides detailed information on the types of questions you can include in forms.

This includes the main form where the meeting is created.

Meeting Type Options can include:

Form changes can include:

This includes the Meeting Minutes form.

Form changes can include:

Notifications send after certain triggers to prompt users via email to action certain tasks.

Changes can include:

The current notifications are outlined below, and space has been provided if you wish to change the body text of the message. All notifications will contain a link to the record.

Changing the text is not necessary if the current message suits your needs.

During the implementation of this module, project and Hypercare period, your Implementation Manager is happy to provide support and guidance and we encourage you to reach out with any queries.

At the completion of the Hypercare period, your Implementation Manager will advise you of your new contact for support.