Two other CASRAI guides cover how to build a dissertation committee: How to Choose a Dissertation Committee walks through typical composition, size, and the selection mistakes that cause the most friction, and How to Ask Someone to Serve on Your Dissertation Committee covers the actual request — timing, email templates, and handling a decline. Neither addresses what happens once the committee exists: what each member actually does between meetings, and how to prepare for and run a productive committee meeting once you are years into candidacy. This guide picks up there.
What each committee role does once the committee is formed
Committee composition varies by institution and field, but most doctoral (and many master’s-level thesis) committees split responsibility across a small number of recurring roles. The labels differ — some programs use “chair,” “first reader,” or “thesis director” interchangeably, and “outside member” and “external member” both show up depending on the school — but the underlying functions are consistent enough to describe generally. Always confirm your own program’s specific role definitions and required signatures in its graduate handbook; the descriptions below are the common pattern, not a universal rule.
Advisor / chair
The advisor (often also the committee chair, though some programs separate the two roles) is the person with day-to-day responsibility for the student’s progress between formal committee meetings. In practice this means setting the cadence of one-on-one check-ins, helping the student decide what is ready to bring to the full committee, flagging problems (a stalled analysis, a methods issue, a slipping timeline) before they reach a committee meeting, and often handling administrative steps like IRB/IACUC approvals or funding logistics tied to the research. At a committee meeting itself, the advisor is typically the one who convenes the group, and in many formats briefly meets with the committee separately from the student — either before or after the student’s portion — to discuss progress candidly.
Committee members
Committee members outside the chair are usually chosen for specific expertise the project needs (a particular method, a subfield, a piece of theory) and are expected to engage with the work between meetings, not just show up to them — reading proposals and draft chapters, responding to material the student circulates in advance, and coming to meetings prepared with substantive feedback rather than a first read of the material in the room. Their ongoing job is less about day-to-day supervision and more about periodic, informed critique: catching gaps in the argument or methodology that the advisor, being closer to the work, might not see.
External / outside member
Many programs require at least one committee member from outside the student’s home department, or in some cases from outside the university entirely. The University of Delaware’s undergraduate thesis program, for example, calls this the “third reader” and describes the role as representing “the University at large,” bringing a perspective independent of the student’s home department to review proposals, progress reports, and the final defense. The specifics vary by school (whether the outside member must be a full committee participant throughout or is added only for the defense, for instance), but the underlying purpose — an evaluator without a stake in the student’s home department’s internal politics or a mentoring relationship with the advisor — is broadly consistent across institutions that require the role.
When thesis committee meetings happen
Most programs schedule committee meetings around a few recurring milestones, though exact names and required frequency vary by institution and department:
- Proposal or prospectus meeting — the committee’s first substantive meeting, where the student presents a research plan for feedback and, usually, formal approval before proceeding.
- Annual or biannual progress meetings — recurring check-ins, commonly required at least once a year, where the student reports progress, discusses timeline and any risks, and gets committee input before the next stretch of work. Some programs set a firm cadence; MIT’s Biological Engineering graduate program, for instance, requires an annual thesis committee meeting scheduled for 1.5 hours, with the first meeting required within a year of the thesis proposal.
- Comprehensive or qualifying meeting — in programs that separate this from the proposal, a meeting focused on assessing whether the student is ready to advance to full candidacy.
- Final defense — out of scope for this guide; see What Is a Dissertation? Structure, Defense, and Deposit and What Happens If You Fail Your Dissertation Defense? for what that meeting specifically involves.
Required frequency is set by the program, not the student or advisor informally — check your graduate handbook for the actual minimum, since “annual” is common but not universal, and some departments require more frequent meetings in the first year or two of candidacy.
How far ahead to schedule
Committee meetings need calendar time from several busy people at once, which makes them harder to schedule the closer you get to when you actually want to hold one. A useful rule of thumb echoed across program guidance is to start scheduling well before the meeting is actually due — weeks, not days — and to be especially cautious around the summer, when faculty travel and reduced availability can push a meeting back by a month or more if you wait too long to start finding a date. In most programs, scheduling and room-booking is the student’s responsibility, not the advisor’s or the department’s, so build that lead time into your own planning rather than assuming it will happen automatically.
What to prepare and circulate beforehand
Committee members give better feedback when they’ve had real time with material before the meeting, not five minutes in the room. A reasonable preparation package, drawing on the kind of materials several graduate programs’ committee-meeting guidance asks for, includes:
- A written progress report or updated aims document, circulated roughly a week before the meeting. MIT’s Biological Engineering program, as one concrete example, asks students to share an annotated set of specific aims with the committee about a week ahead, roughly one to two pages, alongside a required progress form.
- A slide deck that mirrors the progress report rather than introducing new material cold — typically covering what’s been accomplished since the last meeting, current results, obstacles encountered, and a proposed plan and timeline for the next stretch of work.
- A realistic time budget for the presentation itself, since committee meetings are usually fixed-length (commonly 60–90 minutes total including discussion) and running long on early slides leaves no room for the discussion that’s the actual point of the meeting.
- Any required program paperwork — many departments have a standard progress-report or committee-meeting form that needs to be completed and signed at the meeting; check whether yours does well before the date, not the morning of.
How to structure the meeting
Formats vary, but a common pattern looks roughly like this:
- Student presentation. A focused summary of progress, results, and open questions — not a full re-explanation of the whole project from scratch each time.
- Committee discussion with the student present. Questions on methods, interpretation, and next steps; this is where most of the substantive feedback happens.
- A private committee-only segment. Some programs build in time for the committee to speak candidly without the student (and sometimes without the advisor) in the room — MIT’s format, for example, has the student step out while the committee confers with the advisor, then has the advisor step out while the committee speaks directly with the student. This is meant to surface concerns that might not come up in front of everyone at once, not to be adversarial.
- A closing summary. Before everyone leaves, it’s worth explicitly restating what the committee expects before the next meeting and any changes to timeline or plan, so there’s no ambiguity afterward about what was actually agreed.
Do’s and don’ts
- Do circulate materials far enough ahead that committee members have genuinely read them, not skimmed them in the hallway beforehand.
- Do come with a specific list of open questions or decisions you need the committee’s input on, rather than a purely retrospective “here’s what I did” presentation.
- Do take notes during the meeting yourself, even if someone else is also recording minutes — you will remember the discussion better than you expect to.
- Don’t spring major changes in direction, methods, or scope on the committee for the first time in the meeting itself; flag anything significant to your advisor beforehand so it isn’t a surprise to the person who ultimately has to sign off on your progress.
- Don’t treat a lukewarm or critical response as the final word in the room — ask clarifying questions so you leave with an actionable understanding of what changed, rather than a vague sense that something went badly.
- Don’t let scheduling slide past your program’s required interval; a missed or badly overdue committee meeting can complicate a later milestone review, even when the actual research is on track.
After the meeting: recording and acting on feedback
Once the meeting ends, write up a short summary — often called committee-meeting minutes — while the discussion is still fresh, even if your program doesn’t formally require one. At minimum this should capture: what was presented, the specific feedback and concerns raised, any decisions or required changes, and the agreed timeline or expectations before the next meeting. Circulate it to your committee (or at least your advisor) for confirmation that it accurately reflects what was discussed. This does two things: it protects you if there’s ever a dispute later about what was or wasn’t agreed, and it gives you a working checklist to actually act on rather than a memory of a conversation that fades within a few weeks. Some programs require a signed committee-meeting form as the official record instead of, or alongside, informal minutes — check what your department expects.
Frequently asked questions
How often do thesis committees meet?
Most programs require at least one full committee meeting per year after the proposal stage, though some departments require more frequent check-ins, especially early in candidacy. There is no single cross-institutional standard; the required minimum is set at the program or department level, so confirm it in your graduate handbook rather than assuming an annual cadence applies to you.
Who runs a thesis committee meeting?
Typically the advisor or committee chair convenes and moderates the meeting, but the substantive content — the presentation and the discussion that follows — centers on the student. Scheduling and logistics (booking a room, sending the calendar invite, circulating materials) are commonly the student’s own responsibility, not the advisor’s.
What if the committee disagrees with my advisor’s assessment of my progress?
This is one of the reasons committees exist rather than relying on the advisor’s sign-off alone: committee members are expected to form an independent judgment, not simply ratify the advisor’s view. If a disagreement surfaces, it should be discussed openly in the meeting rather than resolved separately afterward without the student’s knowledge; ask for specifics on what would resolve the disagreement so you have something concrete to act on.
Do I need to write minutes after every thesis committee meeting?
Not every program formally requires it, but writing a short summary of decisions and feedback is good practice regardless — it creates a record you and your committee can both refer back to, and some programs’ required progress-report forms effectively serve the same purpose. Check whether your department has a standard form before creating your own informal version.
What’s the difference between a committee meeting and a dissertation defense?
Progress or annual committee meetings are formative — feedback and course-correction along the way — while the final defense is a formal, often public evaluation of the completed dissertation with a pass/fail (or revise-and-resubmit) outcome. See What Is a Dissertation? Structure, Defense, and Deposit for how the defense itself is structured.
Related guides
- How to Choose a Dissertation Committee — composition, size, and selection pitfalls.
- How to Ask Someone to Serve on Your Dissertation Committee — timing, email templates, and handling a decline.
- What Is a Dissertation? Structure, Defense, and Deposit — the final defense and deposit process.
- What Happens If You Fail Your Dissertation Defense? — outcomes and next steps if a defense doesn’t pass.
