The Reach Scoring Model Framework

The Reach Scoring Model framework assigns a score to records of the account, application, contact, enrollment, inbound interest, or lifecycle entities. This score can be based on criteria that are as varied as performance in a course, the student's age, the number of siblings or children, a combination of multiple criteria, and so on. The assigned score enables an administrator or supervisor to then make business decisions based on the score.

The score is determined based on the combined functionality in records of the following entities:

  • Score Definition (Reach): The Score Definition (Reach) entity functions as a container in which you need to select a base entity for which the framework will be implemented. Following are the base entities for which score definition records can be created:

    • Account
    • Application
    • Contact
    • Enrollment
    • Inbound Interest
    • Lifecycle

  • Scoring Factor (Reach): Logic runs on a user-selected field of the base or related entity to determine if its value qualifies to be given a score that is set in the Points field.
    Multiple Scoring Factor (Reach) records can be associated with the same Score Definition (Reach) record. This enables summing up values in the Points field of the associated Scoring Factor (Reach) records, and the total is then stored in the base entity’s field that's selected in the Score Definition (Reach) record.

  • Marketing List: For all base entities except Enrollment, the logic is run on a user-defined list of records of the base entity.

    Note: For the Enrollment entity, logic is run on a user-defined query condition created in the Query Condition tab of the Score Definition record of the Enrollment entity.

Reach Scoring Model Flows

The logic to process Score Definition (Reach), Scoring Factor (Reach) and marketing list records is included in the following flows which are enabled by default:

  • Scoring Model - Retention Score Calculator Scheduler: This is a scheduled flow and is defaulted to run every 15 minutes. It evaluates active Score Definition (Reach) records that are valid for score calculation (New record calculation and recalculation) during the current run and calls the following flows:

    • Scoring Model - Retention Score Calculator For Score Definition: The flow processes the calculations in Score Definition (Reach) records where the base entity is not Enrollment.

    • Scoring Model - Retention Score Calculator For Enrollment: The flow processes the calculations in Score Definition (Reach) records where the base entity is Enrollment.

Notes:

  • If multiple score definitions are associated with the same scoring factor records and the same entity instances are evaluated in the score definitions, the value of the field in the base entity where the final score is recorded will display the most recent value of the score based on when the logic is last run.

    For example, score definitions A and B are based on the contact entity and are associated with the same scoring factor records 1, 2, 3 and 4. The final score is recorded in the Current Retention Score field of the contact entity. The field stores the value of the most recently run logic which could be associated with either Score Definition (Reach) record.

Prerequisites

  • To implement the Reach Scoring Model framework:

    • For the Account, Contact, and Inbound Interest entities, the same base entity must be selected across associated Score Definition (Reach), Scoring Factor (Reach) and marketing list records.

    • For the Lifecycle and Application entities, the marketing list records with the base entity as contact must be associated with Score Definition (Reach) and Scoring Factor (Reach) records in which the application and lifecycle base entities are set.

    • For the Enrollment entity, the same base entity must be selected across the associated Score Definition (Reach), Scoring Factor (Reach) records and in the query condition created for the Score Definition (Reach) record in the Query Condition tab.

      The following table summarizes these prerequisites:

      Base Entity of the Score Definition (Reach) Associated Marketing List Entity Associated Scoring Factor (Reach) Entity
      Account Account
      Application Contact Application
      Contact Contact
      Inbound Interest Inbound Interest
      Lifecycle Contact Lifecycle
      Enrollment

      Not Applicable

      Note: For the Enrollment entity, logic is run on a user-defined query condition created in the Query Condition tab of the Score Definition record of the Enrollment entity.

      		 Enrollment
  • Enable the following roles / privileges:
    • The user will require the CMC - Student Advisor / Recruiter role.
    • User level delete privilege must be enabled on the Saved View entity. By default, the privilege is enabled in the CMC - Base role.

  • Scoring will be done on:

    • Applications that are not closed or canceled.
    • Lifecycles records with the value Open as their status.

Example

To assess a group of students based on factors like age and SAT scores where older students receive more points, the Advisor in Reach sets up the following criteria to calculate the Current Retention Score for each student record:

Student Age Recent SAT (Max - 1600) Points Awarded (for Age) Points Awarded (For Marks) Current Retention Score
Stan 45 8 40 50 90
William 25 7 20 40 60

To implement the above example:

  1. Create the following Scoring Factor (Reach) records for the Contact entity:

    • SF_Agerange_21to30 – the value in the Points field is 20
    • SF_Agerange_31to40 – the value in the Points field is 30
    • SF_Agerange_41to50 – the value in the Points field is 40
    • SF_Recent SAT_1201to1600 – the value in the Points field is 50
    • SF_Marks_801 to1200 – the value in the Points field is 40
    • SF_Marks_400 to 800 – the value in the Points field is 20
      The value in the Points field is awarded if the condition is fulfilled.

  2. Create a Score Definition (Reach) record for the Contact entity and configure the following:

    • In the Score Attribute field, select Current Retention Score.

    • Create a marketing list record that is based on the contact entity and that includes Stan and William.
    • Associate the Scoring Factor (Reach) records created in Step 1.

When the logic to calculate the score for the Contact entity is executed on the marketing list record, the student record for Stan and William will display the values 90 and 60 in the Current Retention Score field.

Use Cases for Reach Scoring Modelframework

Administrators can use the Reach Scoring Model framework for any or more of the following use cases:

  • Take remedial action to help students improve their score.

  • Extrapolate the count of applicants expected from high schools based on the previous academic year’s admission percentage.

  • Determine the inbound interests that the admissions office needs to focus on based on a combination of inbound interest’s SAT scores and distance from the institution.

  • Extrapolate student performance in future tests based on past performance.

Error Logging in the Reach Scoring Model Framework

Error logs are created when unhandled exceptions occur in the Reach Scoring Model framework. For more information, see Viewing Error Logs.

Best Practices for Using the Reach Scoring Model Framework

<Content to be added>