Skip to content Skip to navigation

Important Information Regarding COVID-19

See the Registrar's COVID-19 and Academic Continuity page for information for students, faculty, and staff relevant to classes and academic activities and administration. (updated August 21, 2020)

Bulletin Copy Standards

Our aim in the Bulletin is to produce clear understandable prose that informs the reader about how to get a degree at Stanford. All submissions to ExploreDegrees are subject to Bulletin editing standards. Consult the Course Catalog Descriptions section of this site.

  • Be clear and plain! The degree requirements section of a course catalog is a description of how to get a degree, nothing more, nothing less.
  • Do not use flowery or repetitive language.
  • Any statement about a degree program is either a requirement, a recommendation, or a suggestion.
  • Look at last year’s Bulletin for clues. If we did it last year, we’ll do it again. If we didn’t do it last year, we won’t do it this year.
  • Do not use emphasis of any kind ... no bold, no italics, no ALL CAPS.
  • Do not use the first person (we/us/our).
  • Do not use the future tense … “will or shall”.
  • Do not use non-standard spellings … use the standard spellings that we use: coterminal, adviser, crosslisting.
  • Never use double spaces.
  • Capitalize only things that we capitalize … don’t change our lower case to caps.
  • Just say no! No fancy words … no exhortations … keep it flat and plain.
  • Nothing is “strongly” recommended. Nothing is “extremely” useful.
  • The Bulletin has a style which we apply throughout the book. Every year, I carefully delete capitalizations, variant spellings, "enthusiastic" wording, etc. So, to save everyone time, we ask that you not restore changes which we have persistently deleted. Drop me a line if you have a specific question.
  • Proofread before submitting.
  • Verify that the major or majors you list in your requirements section match the "plans" on PeopleSoft. A student reading your section should find an exact correspondence between what we print and what s/he would see on Axess.
  • Be clear and plain! ... not to repeat myself ;-}