How a Stanford CS PhD thesis actually gets written

In plain terms: at Stanford CS, the dissertation (also called the thesis) is usually not one giant paper written from scratch at the end. It is more often a coherent stack of related research papers, with opening and closing chapters that explain what the whole project means.

This page is a working rundown of that process ... milestones, formatting rules, and how students actually write. It is an independent portfolio research note. It is not Jade’s thesis, not peer-reviewed, and not affiliated with or endorsed by Stanford or Indiana University (IU).

what the document actually is

A Stanford CS PhD student would approach the dissertation as the culmination of multi-year research, not a standalone “paper” written from scratch. In CS (especially systems, artificial intelligence / machine learning (AI/ML), theory, graphics, human-computer interaction (HCI), and similar areas), the document is usually built around a coherent body of work ... typically 2 to 4 related conference or journal papers ... rather than a pure monograph.

Many advisors accept a “stapler” or “sandwich” style (papers as core chapters, plus a strong introduction and conclusion that ties everything together), while others want more rewriting for a unified narrative. The official bar is an original contribution to knowledge that the reading committee accepts.

overall process & timeline (CS milestones)

Stanford CS has clear progress guidelines:

• Years 1 to 2: align with advisor (end of Year 1 ideally), complete foundation/breadth courses, start research rotations/publications, partial teaching requirement, candidacy.
• Year 3: qualifying exam in the dissertation area (by Spring).
• Within 1 year of quals: form reading committee (principal advisor + at least one other CS Academic Council member; at least two CS-affiliated overall) and submit form.
• Year 4 (by Spring): oral thesis proposal to the full reading committee + submit form. Suggested content: problem + significance, prior work / state of the art, your preliminary results, remaining work + timeline. This is private formative feedback, not a public defence.
• Later: university oral exam (dissertation defence) ... typically after substantial research is done; schedule about one quarter before intended conferral. Teaching requirement finished by Year 4. Defence often happens when the student has enough publishable results and the advisor gives the “thumbs up.”
• Final: submit electronic dissertation via Axess (Stanford’s student portal) after applying to graduate. Deadlines are strict (tied to quarterly conferral). Registration (or Graduation Quarter) required in the submission term.

Research is continuous: publish papers as you go (the real “writing” happens there). The dissertation writing phase is often short (weeks to a few months) once the research is mature ... many students describe combining papers, adding glue chapters, polishing, and defending. Advisor feedback is central; students iterate heavily. Resources like the Hume Writing Center (boot camps, consultations) and peer writing groups help.

Info sources students actually use: official CS PhD pages + Student Services dissertation site (primary), prior lab/group theses (search Stanford Libraries or advisor examples), The Redbook (unofficial CS PhD survival guide by students), Overleaf/GitHub LaTeX templates, Reddit (r/stanford, r/PhD, r/cscareerquestions for anecdotes), YouTube (Stanford Learning Lab “10 Tips for Completing a Dissertation,” general CS thesis advice), advisor/labmates, and citation managers (Zotero and similar). Search is mostly for official docs and templates; Reddit/YouTube for real student experiences (“stapler theses are common but coherence still matters”).

formatting requirements (university-wide, strict)

Everything must be a single Portable Document Format (PDF) file (≤1 GB), ready-for-publication appearance. Key rules from the Registrar:

• Page size: US Letter (8.5 × 11 in).
• Margins: 1.5 in on the binding (inner) edge; 1 in on the other three sides. Applies to title page too.
• Fonts: black only. Main body 10/11/12 pt. Preferred/acceptable: Times New Roman, Computer Modern, Helvetica, Courier, Times, Symbol. Embed math/scientific fonts. No script/ornamental/proprietary fonts.
• Spacing: main text 1.5- or double-spaced. Single spacing OK for footnotes, quotes, tables, appendices, etc.
• Pagination: title page counts as i but is unnumbered. Do not include copyright page (ii) or signature page (iii) ... the system inserts them. Start physical numbering at Abstract as iv (or blank iv + Abstract as v for double-sided right-hand starts). Then continuous Arabic numerals (1, 2, …) from Chapter 1 / Introduction onward. Consistent placement (≥0.5 in from edge).

order of contents

1. Preliminary: title page (exact format, uppercase, meaningful title, submission month/year), Abstract (no length limit in PDF; online form limited to 5,000 characters plain text), optional Preface/Acknowledgments/Dedication, table of contents (TOC) with pages, optional Lists of Tables/Figures.
2. Main text: Introduction + chapters with consistent headings.
3. Optional: Appendices, Bibliography/References.

other rules

• English (rare language exceptions need approval + English summary).
• Style guide consistent (advisor/department choice; Turabian/MLA common options).
• Images ≥72 to 150 dpi, JPEG/EPS preferred; landscape facing away from binding.
• No embedded multimedia (submit as supplemental files, max 20 × 1 GB each).
• Spell out URLs fully.
• Previously published work OK if contribution is clear, permissions obtained for copyrighted material, and format requirements met.

LaTeX is dominant in CS. Unofficial but widely used: suthesis-2e.sty (Overleaf templates exist; also GitHub forks and modern Typst/Quarto variants). Always verify the final PDF against current official rules ... templates are not endorsed by the Registrar. Word is allowed but less common.

Common pitfalls: wrong preliminary pagination (most frequent error), including ii/iii pages, inconsistent margins/fonts, non-embedded fonts, or using old theses as format guides (rules change).

research & writing approach (CS flavor)

• Core work first: do research → publish papers → get advisor “enough for a thesis” signal. Typical: several strong papers on a coherent theme.
• Structure the document: substantial Introduction (problem, significance, contributions, roadmap, how chapters fit), core chapters (often adapted papers with unified notation/style/examples/intuitions expanded), Conclusions (summary, limitations, future work). Add value beyond the papers ... tutorial explanations, extra experiments/proofs, broader framing ... so people prefer the thesis over just reading the papers.
• Writing process: inside-out (research chapters first). Use a citation manager. Write early and iteratively. Get feedback early (advisor, committee, writing centre). Active voice, precise language, avoid vague adverbs/superlatives. For stapler style: still make terminology/notation consistent and add connecting tissue.
• Defence: public oral exam after most research is done. Present scholarly material clearly. Food is traditional advice in student guides.

practical tips

From Stanford resources and student experience:

• Keep the project scoped to something finishable.
• Break into manageable steps; track with tools.
• Embrace revision ... everyone gets “revise and resubmit.”
• Writing is not solitary; use campus support.
• Length varies wildly (under 100 to several hundred pages); quality and coherence matter more than bulk.
• After acceptance, electronic submission via Axess; optional embargo; ORCID (Open Researcher and Contributor ID) encouraged.

Official starting points: CS PhD progress guidelines + forms pages, Student Services “Prepare Your Work for Submission” / Format Requirements, and the Dissertation & Thesis Center in Axess. Always cross-check the latest rules, as they can update. Talk to your advisor early about preferred structure (stapler vs. more original synthesis).

← How to Apply · Stanford CS PhD notes index