Argument essay rubric prompt

When to use it

Use this when you need an analytic essay rubric and want a concrete starting point rather than generic advice. Replace the fictional details with your own confirmed facts before using the result in a real setting.

The prompt

## Role
Act as a assessment designer. Apply professional judgment while keeping your reasoning understandable to someone who is not a specialist.

## Context
Students aged 14–15 are writing an 800-word argument about whether the school day should start later. The assignment requires a clear position, evidence from a teacher-provided packet, a counterargument, and a conclusion. The rubric must support revision, not just produce a grade. There is no prescribed grading scale.

## Objective
Design an accessible analytic rubric aligned with the assignment and usable for both peer feedback and teacher assessment.

## Audience
The primary users are secondary English teachers. Make the deliverable usable in their day-to-day work, with enough explanation to support decisions but no unnecessary background lecture.

## Requirements
Use four performance levels with observable distinctions across claim, evidence and reasoning, counterargument, organization, and sentence clarity. Keep language student-friendly. Include two short fictional examples showing different quality of reasoning, and demonstrate how to apply one criterion to each. Provide a calibration routine for teachers and a five-minute student self-assessment; label any suggested scoring weights as optional rather than required.

## Constraints
Do not reward a particular viewpoint, equate sophisticated vocabulary with strong reasoning, double-count the same error, or penalize disability-related needs contrary to agreed accommodations. Work only with the scenario and any material explicitly supplied. Label assumptions and distinguish proposed actions from confirmed facts.

## Tone & style
Be direct, thoughtful, and specific. Prefer plain English, concrete examples, and short paragraphs. Match the language to the intended reader rather than relying on jargon or generic motivational phrasing.

## Output format
Present the requested deliverable first, using descriptive headings and tables only where they improve usability. Keep supporting notes separate from copy intended for publication or direct use. Finish with a short checklist of outstanding decisions or verification steps.

## What to avoid
Avoid filler, unsupported certainty, and details invented to make the result seem more complete. Do not let a polished presentation conceal missing information or conflicting requirements.

## Success criteria
Students can identify one concrete revision action from each descriptor, and teachers can explain why adjacent levels differ. Check the result against the stated constraints before presenting it and correct any inconsistencies you find.

## Clarifying questions
Ask up to three focused questions only if missing information would materially change the result. Otherwise proceed with the fictional scenario, state any necessary assumptions briefly, and identify what a real user should confirm before relying on the output.

Why it works

• The scenario gives the model concrete facts and boundaries instead of asking it to invent a brief.
• The requirements specify the actual deliverables and the important edge cases for this task.
• The constraints make unsupported claims and unapproved commitments harder to slip into the result.
• The success criteria turn review into a practical check: students can identify one concrete revision action from each descriptor, and teachers can explain why adjacent levels differ.

Make it yours

Build a tailored version with PromptDeck by replacing the fictional scenario with your own context, audience, and constraints. Keep the verification steps so the final result reflects what you actually know.