Policy Brief Grading Rubric
CRJU/POSC 320 – Introduction to Public Administration
📊 Overview
Your Policy Brief Project is worth 45% of your total course grade. This rubric explains how your work will be evaluated each week and at the end of the project. Please refer to this guide as you draft, revise, and finalize your brief.
✅ Grading Breakdown (Total: 55 points)
| Category | Criteria | Points |
|---|---|---|
| Content & Analysis | Clearly defines the problem; supports claims with evidence; provides thoughtful stakeholder, organizational, and management analysis | 20 |
| Kettl Integration | Accurately applies weekly textbook concepts; includes page citations; deepens use of theory across project stages | 15 |
| Structure & Organization | Logical section flow; clear headers and transitions; consistent formatting | 5 |
| Writing Quality | Professional tone; clear and concise writing; minimal grammar or usage issues; follows memo formatting guidelines | 5 |
| Revision & Process | Shows weekly progress with tracked changes and comments; revision history demonstrates active engagement | 5 |
| Final Polish | Includes executive summary; cohesive and well-cited in APA; meets length and style expectations | 5 |
| TOTAL | /55 |
🧾 Evaluation Notes
🟢 Strengths
Where did you demonstrate insight, depth, or strong integration of theory?
🟡 Suggestions
What would improve your analysis, clarity, or use of evidence?
🔴 Concerns
Any issues with citations, source quality, writing integrity, or development process?
🚫 Academic Integrity Reminders
The following will result in automatic zero for that week’s assignment:
- Large blocks of text appearing suddenly without revision
history
- Generic, off-topic, or AI-generated analysis without
citation
- Inaccurate or missing references to Kettl
- Research logs that don’t match document development
- Copy-paste content without attribution
💡 Tips for Success
- Follow the weekly prompts closely and cite Kettl every time
- Write incrementally: don’t paste in large sections all at once
- Use tracked changes in Google Docs to show your process
- Be specific. Avoid generic or vague analysis—use real cases, data, and clear logic
- Use your Research Log to explain what you’re learning and how your thinking is evolving