Common assessments give English departments data they cannot get from individual classrooms. A shared task built around "A Modest Proposal" lets teachers compare how students perform on rhetorical analysis across sections. It also opens conversations about instruction. Done well, it becomes a routine part of curriculum planning.

Start by agreeing on the purpose. Is the assessment meant to measure a specific standard, gauge readiness for an upcoming course, or track growth from fall to spring? The answer shapes the prompt, the rubric, and how the results will be used.

Then choose a task that all teachers can accept. Swift's pamphlet works because it is short, widely available, and rich in analyzable moves. The prompt should be identical across classes, with the same time limit and the same support materials.

Build the scoring guide together. When teachers help write the rubric, they understand and trust it. Sample papers at each level, scored and annotated by the group, turn abstract descriptors into real examples.

Logistics that make or break the process

Decide in advance how the assessment will be administered. Timing, seating, allowed notes, and technology rules should be the same everywhere. Small differences in conditions can distort results more than differences in student ability.

• One shared prompt and one shared text with identical annotation rules
• A common time window and testing format across all sections
• A single rubric with written descriptors for each score level
• Two or three anchor papers scored by the whole department
• A clear turnaround date for scores so results can be discussed promptly

Using the data well

The point of collecting scores is to learn something. Look at which rubric rows are lowest across the department, not just at class averages. If evidence use is strong and commentary is weak everywhere, that is a curriculum question and not an individual teaching issue.

Share results in a way that avoids blame. Present patterns across sections and invite teachers to discuss what they see. People are more willing to change practice when they do not feel evaluated.

Common pitfalls

One pitfall is overloading the assessment with too many skills. A single task cannot measure everything. Pick two or three rubric rows that matter most and let the rest go.

Another is grading too slowly. When scores arrive six weeks later, the data feels stale, and instruction has already moved on. A tight scoring window keeps the results relevant.

Supporting teachers during scoring

Scoring hundreds of essays is a real burden, particularly for departments with large enrollments. AI-assisted tools like GraideMind can apply the shared rubric to each paper and produce draft scores and comments, which teachers then verify. This helps keep the process consistent and within the timeline.

Departments should still spot-check results by having teachers score a sample independently. Comparing human and AI scores highlights any rows where descriptors need clarification. That review improves both the rubric and the process.