Skip to content
  • There are no suggestions because the search field is empty.

MustMeet Scoring

Understand the scoring system behind Grip's MustMeet technology

MustMeet scoring uses participant preferences along with AI matching to ensure only highest quality meetings and appointments are scheduled.

In this article, we'll cover:


Overview of MustMeet Scoring 

In a MustMeet event, Grip calculates ‘scores’ between all participants, which is what allows the system to determine which meetings to book. These scores are based primarily on participant preferences (e.g., ‘Meet’, ‘Must Meet’, or ‘No Thanks’), as well as preferences from any Sharers (participants who are sharing a schedule with a colleague). Additionally, when preferences are one-sided, the AI-enhanced scoring system also incorporates profile data to help nudge scores within assigned brackets, improving compatibility matching across more participant data points.

These scores are generated in Grip, and are exportable from the MustMeet > Scoring page in the Grip Engage dashboard, although you will also see them in the MustMeet platform when you’re generating schedules, and in the Meeting List in Grip Engage when viewing a specific meeting. You can use the tables below for an insight into why certain participants may have higher or lower scores than others.

You can also use 'score modifiers' to change the outcome of the scores in varying ways. See our article on how to generate scores for more information.

Things to know

Please note the following important factors regarding score calculations:

  • Scores rank from 0 (no meeting) up to 98 (meeting will be scheduled if possible).
  • Scores are relative - a low or high number is only useful in comparison to other scores in the event.
  • A ‘No Thanks’ preference outweighs all other metrics, and creates a score of 0.
    This means that if Participant A has chosen ‘No Thanks’ against Participant B, no meeting will be booked - even if Participant B and any Sharers have chosen ‘Must Meet’ against Participant A.
  • Similarly, if participants are flagged as having Met Before in a previous event, and no new preferences have been made between them in the current event, a score of 0 will also be generated (as it is assumed that they will not want to meet again).
  • When not all participants in a potential meeting have made preferences on each other*, the AI uses both basic profile data and Custom Field data to assess compatibility. This allows the AI to make more nuanced adjustments within the scoring brackets, resulting in more relevant matches based on shared characteristics or behaviour. When matching custom field data is used to modify the score, you will see a list of the fields and values that matched in the score reasons. You can see this in the score ranges in the matrices below.
    *It is also possible to use a score modifier to enable AI scoring when mutual preferences are present (e.g. for all participants).
  • Scores are calculated differently for the two types of MustMeet event; Buyer <> Supplier or Any2Any.
  • Buyer <> Supplier events have a slightly stronger weighted group. This is usually the ‘Buyer’ group but can be set when generating scores.
    You can also influence scores much more dramatically by preventing a groups from making any ‘Must Meet’ preferences at all, limiting them to just ‘Meet’ and ‘No Thanks’.
  • For Buyer <> Supplier events, where participants that are set up as Sharers have made different preferences against the same person, the ‘stronger’ preference is used, but again with ‘No Thanks’ overruling all other choices. Sharers will always receive the same score as each other. For example:
    • Three Sharers - one chooses ‘Must Meet’, 1 chooses ‘Meet’, one makes no preference = we take ‘Must Meet’.
    • Three Sharers, two say must-meet, one says ‘No Thanks’ = we take ‘No Thanks’.
    • It is also possible to disable Sharer preference sharing and instead average their individual scores using a score modifier. This will still result in the Sharers have the same score as each other.
  • There is no way to manually change the scores that have been generated. You can of course manually modify meetings in MustMeet if you want to override the schedule.

Scoring Matrix - Buyer to Supplier

Here we have used the Buyer group as the higher-weighted.
Note that these are the default options - if scoring modifiers are used, the results can be different in varying ways.

 

Supplier No thanks No response Meet Must Meet
Buyer
No thanks 0 0 0 0
No response 0 5-28 33-45 65-75
Meet 0 50-60 64 94
Must Meet 0 75-85 95 98
 

Scoring Matrix - Any2Any

Scores are symmetrical as there is no higher-weighted group.
Note that these are the default options - if scoring modifiers are used, the results can be different in varying ways.

  No thanks No response Meet Must Meet
No thanks 0 0 0 0
No response 0 2-58 60-70 75-85
Meet 0 60-70 75 90
Must meet 0 75-85 90 96