Skip to main content

Assessing student work using proficiency scales

Proficiency-based assessment starts with a simple question: what evidence does this submission show for each learning objective? TeachFront keeps objectives, proficiency levels, and feedback in one place so students see the same breakdown you use to calculate grades.

How assessment works in proficiency-based grading​

Unlike points-based systems where a score is a single number, proficiency assessment breaks down a student's work by learning objective:

  • Each objective gets its own proficiency level (e.g., "Developing", "Proficient", "Advanced").
  • Feedback is objective-specific, explaining what the student did well and what to work on.
  • Grades emerge from patterns across objectives, not from adding up points.

This approach gives students (and families) a clearer picture of what they know and what they still need to practice.

Basic assessment workflow​

  1. Student submits work for an assignment linked to specific objectives.
  2. You open the submission in the grading workspace.
  3. You rate each objective on your proficiency scale (e.g., Beginning, Developing, Proficient, Advanced).
  4. You add objective-level feedback explaining the evidence and what's needed next.
  5. You publish the rating when ready for students to see; you can invite resubmission if your policy allows.
  6. Student receives feedback, sees their proficiency level, and (if allowed) resubmits.
  7. You re-rate the resubmission, updating the proficiency level as growth is shown.

Key differences from points-based grading​

AspectPoints-basedProficiency-based
What's recordedOne number (points or %) per submissionOne level (e.g., "Proficient") per objective
Feedback focusGeneral comments; tied to point deductionsObjective-by-objective evidence; named growth areas
What students seeA score; they infer what was good/weakClear breakdown by objective; explicit next steps
RevisionsStudents may retake, but the original score often countsStudents can resubmit and update proficiency; you decide what counts
GradingTime-consuming point verificationFaster assessment once you know the scale well

Guides in this section​

Typical scenarios​

Scenario 1: A student shows emerging understanding​

You rate an essay submission on Organization as "Developing" because the student has a clear introduction and conclusion but no coherent structure in the middle.

Feedback: "You have a strong opening paragraph that introduces the topic. Your thesis statement is clear. The supporting paragraphs need a topic sentence at the start of each to guide readers. Try adding one sentence at the beginning of each paragraph that connects back to your main idea."

The student can resubmit after revising the middle sections.

Scenario 2: A student masters an objective early​

In a math unit on fractions, a student solves all fraction-multiplication problems correctly on their first attempt.

Rating: "Proficient" on Multiply Fractions Correctly.

Feedback: "All work shown; calculations correct. You're ready to move on. Try one of the challenge problems on the board for extra depth."

Scenario 3: A student is absent​

A student was absent during a lab and submits a lab report based on a lab partner's work.

Rating: "Excused" (not "Not Yet" or a low proficiency).

Reason: Absence; not a fair measure of this student's understanding. They can complete a make-up lab later.

What to assess​

Before you start rating, confirm:

  • Objectives are clear — students know what they're being assessed on.
  • Assignments map to objectives — students understand which objectives the work addresses.
  • Proficiency scale is defined — you've shared what each level (Proficient, Developing, etc.) means.
  • Evidence is visible — the submission shows whether the objective was met (work shown, reasoning explained, etc.).

When to publish grades​

Publish immediately if:

  • Grades are ready and students don't need time to revise.
  • You want to invite resubmission now.

Hold and publish later if:

  • You're still collecting other ratings for context (e.g., you'll rate all objectives before showing results).
  • You want to give students feedback before they see the proficiency level.
  • Your policy requires you to wait (e.g., after a review period).

Product references​