Rubric scales are a way to quantitatively review a student in progress reviews. It may happen that different rubric scales are used to rate the same goal. This happens when a student has chosen a different rubric scale in different progress reviews which include the same goal. How do you ensure that the growth chart in a goal card, and the spider web that includes multiple goals and progress reviews, still provide useful insights? Image you want to make the following rubric scales available to students:

The rules

Rule 1: Make sure the lowest level is always 0% and the highest level is 100%. Divide the other levels in between. This can be proportional, but this is not the most important principle. Rather, look at rule 2 for the distribution between 0 and 100:

Rule 2: Make sure that the level that elicits a certain 'feeling' in a different rubric scale also has the same percentage. For example, 'Sufficient' in one rubric scale has the same percentage as ':)'. For example, both 50%. It is not recommended to create multiple scales in which the word 'sufficient' appears, but each time actually means something else. For example: 'Unsufficient, sufficient, good, excellent' and 'Unsufficient, sufficient, good' do not go well together. Then 'Voldoende' and 'Goed' suddenly have a completely different meaning at the global level.

Rule 3: These scales do not need to correspond to what you mean with "voldoende" during your formal assessment: the ratings in Portflow indicate growth and not absolute "grades". Some programs use an 8 as sufficient for formal assessment, others 5,5. For rubric scales to be used and combined across the institution, it is important to be consistent in Portflow and to separate these scales from grades in formal assessments. That 6 can be assigned in the LMS or the assessment program.

From these rules the following rubric scales can follow:

These rubric scales can then be used interchangeably by a student because the percentages are used in a growth graph. A single progress review where the "words" or emojis matter still has value on its own.

How are these percentages reflected in Portflow?

We take the following example of executed progress reviews:

First review of 'goal 1', time point 1

Teacher 1: 60%

Teacher 2: 80%

Second review 'goal 1', time point 2

Teacher 1: 70%

Teacher 2: 90%

Growth Chart

In the growth chart (by goal), the average rating (in percentage) by role per evaluation is taken as a data point. A line is drawn between different data points.

Example: In growth chart of 'goal 1', we will now see 2 data points. The datapoints are the average per role: 70% (60+80/2) on time point 1 and 80% (70+90/2) on time point 2.

Spider diagram

Results in a spider diagram (multiple goals, aggregated from multiple progress reviews) are based on a decaying average: the last rating weighs 65% and the average of the previous results weighs 35%. The rating (in percentage) of the same role is averaged.

Example: In the spider graph after the first review we will see 70% for 'goal 1'. After the second review we will see 76.5% for 'goal 1'. (Calculation decaying average: 35% * 70% + 65% * 80% = 76.5%)

Progress Review

Results in a spider diagram of 1 progress review (multiple goals, 1 progress review) are averaged by role.

Example: In the progress review chart we will see the average score per role: 70% after review 1 and 80% after review 2.