You send a grading policy email in the first week of September, everyone reads it once (maybe), and by November you're fielding the same three questions from parents and students as if it never went out: does a late assignment lose points every day or just once, does the lowest quiz score get dropped, can a test be retaken. The policy was correct. It just wasn't written in a way anyone could actually recall or reference three months later.
Why the first email doesn't stick
Most grading policy emails are written as a single dense paragraph or a wall of bullet points buried in a longer welcome-back message. Both formats are technically complete and practically unreadable, nobody skims a paragraph for the one rule they need in November, and nobody remembers a bullet point that was item nine of fourteen back in September. The information was sent. It wasn't made findable.
Writing a policy that survives the semester
1. Separate the policy from the welcome message entirely. A grading policy buried at the bottom of a "welcome to my class" email gets read once, in a rush, alongside ten other things. Send it as its own clearly labeled message so it's easy to search for later.
2. Organize by the question a parent will actually type into search, not by your internal logic. "Late work policy," "retake policy," "how grades are weighted" as separate labeled sections beats one flowing explanation, because in November, someone is scanning for one specific answer, not reading the whole thing again.
3. Give one worked example per rule. "Late work loses 10% per day, capped at 50%" is a rule. "A 90 turned in three days late becomes a 63" is the same rule in a form nobody misreads.
Our [syllabus generator](/syllabus) builds a structured, section-by-section policy document, grading weights, late work, retakes, academic honesty, formatted so each rule is its own labeled, scannable block rather than one long paragraph, which is most of what makes a policy easy to reference later instead of only easy to send once.
What still needs a human decision
- Which exceptions are worth stating up front. Every policy has edge cases. IEP accommodations, family emergencies, and deciding which ones to name explicitly versus handle case by case is a judgment call about your specific students, not a template default.
- The tone for repeat offenders. A policy document states the rule. How firmly you enforce it for a student who's clearly struggling versus one who's clearly not trying is a conversation, not a document update.
- Updating it mid-year without confusion. If you adjust a rule in November, deciding how to communicate the change so it doesn't read as an inconsistency is entirely yours to manage.
The policy itself doesn't need to change much year to year. How findable it is in November, not just how complete it was in September, is what actually determines whether you're still fielding the same three questions at conference time.
