When several teachers in a department all teach Silas Marner, it is tempting to let each design their own assessment. That respects autonomy, but it makes it difficult to compare results or spot department-wide trends. A common assessment gives everyone shared evidence about what students can do.

The goal is not to standardize teaching. Teachers can still use their own activities and discussions. The common assessment simply ensures that the final measure is the same for everyone.

Start by agreeing on what the assessment should measure. Most departments focus on a small set of skills, such as making a claim, using textual evidence, and explaining analysis. Too many targets make the task unwieldy.

Involve the whole team in design. Teachers are more likely to trust and use an assessment they helped build. It also surfaces different ideas about what strong writing looks like.

Building the Assessment

Keep the task manageable. A single prompt, a shared rubric, and a clear time frame are enough. The following components make a solid foundation.

• One agreed-upon prompt that asks students to argue a claim about a central idea in Silas Marner
• A four-level rubric with descriptors written jointly by the department
• A set of anchor papers scored together to define each performance level
• A common timeline for administration, scoring, and returning results
• A brief plan for how results will be discussed and used to adjust instruction

Scoring Together

Hold a calibration session before scoring. Everyone reads and scores the same sample papers, then compares. Disagreements are useful, because they reveal where the rubric language is unclear.

Consider double-scoring a sample of essays across classrooms. Comparing the scores shows whether the department is applying the rubric consistently. Small differences are normal, but large ones warrant a conversation.

Using the Data Well

Look at results by criterion rather than only by overall score. If evidence use is strong but analysis is weak across the department, that points to a shared instructional need. Teachers can then plan lessons around it.

Administrators and department heads benefit from this kind of clarity as well. Data tied to specific skills is far more useful than a single average. It supports conversations about professional development and curriculum decisions.

Reducing the Scoring Burden

Scoring hundreds of essays across a department is a big commitment. GraideMind can apply the shared rubric to every essay and produce a consistent first pass, along with criterion-level data the department can review. Teachers still verify and adjust scores, but the baseline is the same across classrooms.

That consistency addresses one of the biggest weaknesses of common assessments, which is variation between graders. It also gives teams more time to analyze results and plan next steps. Time spent on discussion is usually where the real improvement happens.