Skip to main content

Scoring: How Ratings Become an Overall Score

Set up scoring per framework role: weights or rules, the Scoring readiness panel and yellow warning icons, and a test evaluation before year end.

Written by Maxwell Bass

Scoring turns the ratings your evaluators assign into domain scores, a Professional Practice score, and one Overall Evaluation Score for each staff member. Your district sets it up once per framework role, and Ascend tells you what is missing until it can produce a rating. This article covers the setup in order.

Prefer to watch? The two-minute video below goes from a yellow warning icon to "No scoring issues found": the readiness panel, weights, rule-based districts, and a test evaluation. Read on for the details.

If the video doesn't load here, watch it on YouTube (2:16).

Looking for the rating levels themselves, or the score ranges that turn a number into a level? That is the rating scale: Ratings: The Levels Your Evaluators Choose.


Three Things to Keep Apart

Districts often use "rubric", "ratings" and "scoring" to mean the same thing. In Ascend they are three separate setups on Settings → Ascend → Framework.

Setup

What it is

Where

Set per

Rubric

The domains and components evaluators rate, with a description of what each level looks like for each component

Select a role → Rubric

Role

Ratings

The levels themselves (1 to 4, their names) and the score ranges that map a calculated score to a level

Shared settings → Rating scale

District (shared by every role)

Scoring (this article)

How component ratings roll up into domain scores and one Overall Evaluation Score: weights or rules

Select a role → Scoring & weights

Role

The Framework page with the rubric, the shared rating scale and the Scoring & weights section labeled

Before You Begin

  • Scoring is part of State Reporting. The Scoring & weights section appears on each role's page only when Lebra has turned on State Reporting for your district. If you select a role and don't see that section, contact Lebra support

  • You have Admin access. Group Admins and Evaluators cannot configure framework or scoring settings

  • Your framework already exists. You need at least one framework role, domains, and components before weights mean anything. Build those first using Setting Up Ascend: A Step-by-Step Guide

  • Your rating scale has score ranges. Both scoring methods map the final number to a level through them. See Ratings

Your district sets up scoring; Lebra does not configure it for you. When Lebra uploads a framework role, its weights start empty and the role shows a yellow warning icon until you fill them in.


Which Scoring Method Does Your District Use?

Ascend supports two methods, set for the whole organization:

Method

How ratings become scores

What you set per role

Math-based

Weighted averages across domains and the Student Achievement Indicator (SAI)

A weight for every domain, SAI, and DDM if used, totaling 100%

Rule-based

Ratings determined by conditions you define (for example "no more than one Basic")

The SAI weight (and DDM), plus two rule sets

The method is the same for every role, and there is no admin control for it. Contact Lebra support to switch between math-based and rule-based scoring.

Tip: the Weights table tells you which method you're on. A weight field for every domain means math-based; a single SAI weight with Professional Practice "derived automatically" means rule-based.


Step 1: Set Weights for Each Role

  1. Go to Settings → Ascend → Framework and select the role in the left sidebar

  2. Expand the Scoring & weights section, below the role's Rubric

  3. Enter the weights in the Weights table:

    • Math-based: a Weight (%) for each domain, for Student Achievement Indicator (SAI), and for District Determined Measure (DDM) if your district uses one. The Total row must read 100%. Until it does, it shows in red with Must equal 100%, and evaluations for that role produce no score

    • Rule-based: only the SAI weight (and DDM, if used). Professional Practice is calculated for you as whatever remains of 100%

  4. Repeat for every framework role

The Scoring & weights section with weights totaling 85% in red and the readiness panel naming the problem

Weights save when you click out of the field. There is no Save button on this table. Tab or click away from the last weight you typed before leaving the page, then confirm the Total row reads 100%.

Tip: weights accept two decimal places, which is how thirds are handled: 33.33 + 33.33 + 33.34 totals 100%. If your district doesn't use SAI, set its weight to 0 and give the rest to your domains.

The Score Ranges card below the Weights table is a read-only summary of the shared rating scale. Any level showing Not set needs a range; click Edit shared rating scale to open the Rating scale page.


Step 1b: Build Your Scoring Rules (Rule-Based Districts Only)

Skip this if your district uses math-based scoring.

Rule-based scoring needs both rule sets below. If either is empty, evaluations for that role produce no score, and the readiness panel says so.

  • Domain Scoring Rules turn the component ratings inside a domain into that domain's rating

  • Professional Rating Rules then turn those domain ratings into the Professional Practice rating

The Scoring & weights section for a rule-based district: a derived Professional Practice weight, an SAI weight, and two rule sets

To add a rule:

  1. Scroll to Domain Scoring Rules and click Add Rule

  2. Choose the Result rating the rule produces when it matches

  3. Click Add next to Conditions, then set the rating level being counted, an operator (>=, <=, =, or >= %) and a value (a count of components, or a percentage with >= %)

  4. Add more conditions if the rule needs them. All conditions in a rule must be true for it to match

  5. Click Save Rules, then do the same for Professional Rating Rules

How conditions are read: each one counts how many ratings landed on a level. Count at Distinguished >= 3 means "at least three components rated Distinguished." Count at Unsatisfactory = 0 means "nothing rated Unsatisfactory." >= % uses the share of scored items instead of a count. Only scored components count; anything left blank is ignored.

Rules are evaluated top to bottom, and the first match wins. Order them from most selective to least: put the Distinguished rule above Proficient, and add a catch-all rule at the bottom (for example Count at Unsatisfactory >= 0 → Unsatisfactory) so no one ends up unrated.


Step 2: Clear the Flags

Ascend checks every role against how final ratings are calculated and shows the result in two places. Districts often call these "the flags."

  • Yellow warning icons. A yellow warning icon next to a role in the left sidebar means something in that role's setup would stop a rating from computing. Hover over the icon to read the reason. The same icon appears on the section that needs the fix: Rubric, Scoring & weights, or (Idaho districts) the Evaluation type in the role header

  • The Scoring readiness panel at the top of Scoring & weights spells out each problem. Red means it blocks scoring; amber means check it. Problems on the shared rating scale that affect this role are listed under "Shared rating scale affecting [role]"

The Framework page with yellow warning icons next to two roles in the sidebar and on the Scoring &amp; weights header

What the panel flags, and what to do:

Message

Fix

Weights total 85%. Domains, SAI must add up to 100%…

Adjust the weights in the table above until the Total row is green

Domain 4 "…" has no components. An empty domain stops the whole summative from scoring.

Add a component to that domain in the Rubric section, or delete the domain

SAI carries 10% of the rating, but no rating level has an SAI range…

Enter SAI Min % and Max % on each level of the Rating scale

No domain scoring rules apply to this role, so no rating can compute.

Rule-based districts: add and save both rule sets (Step 1b)

Rounded scores 2.40–2.49 match no rating between "Basic" and "Proficient"…

Close the gap on the Rating scale page (see Ratings)

Scoring every component at one level doesn't produce that level…

Your cut points and weights disagree, for example all 3s averaging into the Basic range. Review the score ranges

No state evaluation type… (Idaho)

Click Edit role and choose an Evaluation type, or Does not apply

Click Check again after each fix. When the panel reads No scoring issues found for [role] and the role has no warning icon in the sidebar, that role is ready.

The readiness panel reading No scoring issues found for Teacher, with weights totaling 100%

A warning icon on a role that nobody holds yet is shown as a warning rather than an error. It still needs fixing before anyone is assigned to that role.


Step 3: Test One Evaluation Before Year End

Flags clear all year, but the day they matter is the day a summative is finalized. Confirm the setup produces what you expect well before summative season:

  1. Confirm the role's Scoring readiness panel reads No scoring issues found

  2. Create a summative evaluation for one staff member in that role

  3. Rate every component and enter an SAI percentage

  4. Check the Evaluation Score Summary table

An Evaluation Score Summary showing each domain's score, weight, contribution and rating, and an overall score of 3.06, Proficient

Every domain should show a score and a rating, the footer should show an Overall Evaluation Score with its rating, and on math-based scoring the Weight and Contribution columns should match the weights you entered. If anything is blank, see Troubleshooting below.

Run this for each framework role. Weights and rules are per role, so one role being right says nothing about the others.


How the Overall Score Is Calculated

Math-based

  1. Each domain is averaged across its scored components, and that average maps to a rating through your score ranges

  2. Professional Practice is the weighted average of the domain averages, using your domain weights

  3. The Overall Evaluation Score adds each domain average times its weight, plus SAI times its weight, plus DDM times its weight where used

  4. That overall score maps to a final rating through the same score ranges

Rule-based

  1. Each domain's rating comes from the Domain Scoring Rules

  2. Professional Practice comes from the Professional Rating Rules, applied to those domain ratings

  3. The Overall Evaluation Score is Professional Practice times its weight, plus SAI times its weight, plus DDM times its weight where used

A rule-based Evaluation Score Summary with Professional Practice times 67% and SAI times 33%

One thing that surprises districts: SAI and DDM enter the overall score as the rating level their percentage maps to, not as the raw percentage. An SAI of 68% that falls in your Proficient range enters the calculation as a 3. Your SAI percentage ranges on the rating scale therefore decide how much a given SAI moves the final score.

Every domain needs at least one scored component. If a domain has none, Ascend won't produce a Professional Practice or overall score for the evaluation.


Why It Matters

Summative reports and State Reporting both read the Overall Evaluation Score. A role with a flag produces summatives with no overall rating, and State Reporting fields such as Evaluation Result stay empty for everyone in that role. Clearing the flags is your district's job; Lebra uploads frameworks but never sets weights, rules, or cut points for a district.


Troubleshooting

What you see

Why

Fix

No Scoring & weights section on a role's page

State Reporting isn't enabled for your organization

Contact Lebra support

A role has a yellow warning icon in the sidebar

Something in that role's rubric, scoring, or evaluation type would stop a rating from computing

Hover over the icon to read the reason; select the role, expand the Scoring & weights section and follow the Scoring readiness panel

Total shows in red with Must equal 100%

Math-based weights don't sum to 100%

Adjust the weights; use two decimals if needed

A weight didn't stick

The field never lost focus, so the change was never saved

Click out of the field, then reload and confirm

No overall score on a completed evaluation

A domain has no scored components, weights don't total 100%, a score range is missing, or a rule set is empty

Follow the Scoring readiness panel for that role

A domain shows a score but no rating

The score fell in a gap between score ranges

Close the gap on the Rating scale page; its banner names it

Everyone lands on the same rating, or ratings look one level low

Overlapping score ranges match the lower level first, or a broad rule sits above a selective one

Make ranges exclusive; reorder rules most selective first

Weights look right for one role, wrong for another

Weights and rules are per framework role

Select each role in the sidebar and open its Scoring & weights section


Frequently Asked Questions

Can different roles use different weights?

Yes. Weights and rules are per framework role, and that's the intended setup. The scoring method and the rating scale are district-wide.

Can a role use different weights per school year?

No. Weights are current settings, not historical ones. Evaluations already finalized keep the scores they were calculated with, but changing weights mid-year affects any evaluation scored after the change.

Do I have to use SAI?

If your district doesn't use a Student Achievement Indicator, set its weight to 0 and give the rest to your domains so the total still reaches 100%.

Will Lebra set this up for us?

No. Lebra uploads your framework roles and can switch the scoring method, but weights, rules and cut points are your district's decisions, and only a district administrator can enter them. If something in this article doesn't match what you see, contact us.

Do staff see this?

Staff see the resulting Evaluation Score Summary on their self-evaluations and summative evaluations. They don't see the setup screens.

Does someone with two framework roles get two scores?

Yes. Each role is scored on its own framework, weights, and rules, and reported separately. See Staff Who Hold Two Framework Roles.


Related Articles

Did this answer your question?