Meeting Types: The meeting type is used to classify the use case for the meeting. Most people start in our system utilizing the Business Review meeting type to run their standard QBR's. As you become more comfortable in the system different meeting types can be used for different tasks.
The meeting type does four things for you within the system:
1. It tells the system which templates to use from those that you have assigned to the client in their library./
2. It tells the system what reports to output based on the meeting setting,
3. It sets the data for display in the meeting view
4. It groups the data for long-term use. When you close a meeting, the system archives the results, archives the scores, and then the data moves forward to the next meeting for editing, reducing prep time.
Meeting States: These mirror the most common workflow we see used by our users in the system. These are optional for use, you are not required to change states during the process, but it helps teams know who has control of the assessment. It also appears on the QBR landing dashboard to give you at-a-glance
- Default: This is the starting point and where an assessment can reside until work starts. If you schedule meetings in advance, any new meeting will appear in the default column on the dashboard when it is 30 days for the due date signifying it is time to look at starting the review.
- Engineer Review: This is usually the first stop for the review when you are working in a vCIO/Engineering team format. The engineer will conduct their assessment and then can move the assessment to the next stage (note: If the vCIO owns the process end to end, this stage can be skipped.
- vCIO: This stage is where gaps are reviewed and solutions are usually built in preparation for the meeting.
- Pending: This stage locks the data so no additional edits can be made prior to the meeting event.
