What the silence usually is
Candidates hear a verdict. In the great majority of cases it is administration. A chair carries a teaching load, a service load and several other candidates at different stages, and your chapter landed in a week that already had two proposals and a defense in it. Term boundaries make it worse, since the weeks either side of a break are precisely when faculty are least reachable and candidates most anxious.
There are two other causes worth knowing. The first is that a document arrived without a question attached to it, and a file with no question is not an obligation, merely a thing to read eventually. The second is deference: members frequently wait for the chair to comment first, so one unopened message at the top of the chain holds up three people underneath it, none of whom regards the delay as theirs.
Send something that is easy to answer
The remedy is to make replying cheaper than not replying. What the desk sends on a candidate's behalf is a status memo, in the body of the message rather than as an attachment, built so a reader on a phone can respond in one line.
- ◆A single page, in the message itself. Nobody opens a document to discover whether it needs them.
- ◆Three lines on what has changed since the last version, named by section, so a reader can skip what they have already approved.
- ◆The decision you actually need, written as a closed question with two options rather than an invitation to comment freely.
- ◆The date beyond which the answer stops being useful, with its cause attached: a term end, a data collection window, a board meeting.
- ◆The document itself, attached, with a version number and a date in the filename so nobody marks up last month's copy.
A cadence, and the point at which you escalate
One follow-up a week after the memo, quoting your own message beneath it so nothing has to be searched for. A second a week later. If both pass unanswered, change the question rather than repeating it: ask whether the chapter should sit until the term turns, which is a question people answer even when they cannot face the chapter.
After roughly a month of nothing, write to whoever administers doctoral candidates in your school, and write it as a scheduling matter rather than a complaint. Say what you sent, when, what decision is outstanding, and which milestone it threatens. Programs keep somebody for exactly this and they would rather move a candidate on than lose one. What you should not do is write around the chair to a member, or copy a member into a message about the chair's silence. Committees are small rooms, and that message is remembered long after the chapter is forgotten.
Work that does not depend on their answer
Waiting candidates do one of two things. They stop entirely, or they rewrite the chapter under review, which is worse: the version being read stops matching the version you hold, and every comment that eventually arrives has to be translated before it can be used. Freeze the chapter that is out. Nothing in it moves until the comments come back.
Then take up whatever the committee's answer cannot change. References brought into a single current style, the appendix of instruments, the methods detail that will be needed whichever design survives, the ethics training certificate, the data cleaning that has to happen in any event. A literature chapter can also be strengthened independently, and a review built on a synthesis matrix tends to survive committee comment better than one built on a stack of summaries.
When the silence is telling you something
Occasionally it is a signal, and there are two shapes to it. A chair who cannot bring themselves to say a document is not ready sometimes says nothing instead. A committee split between two members, or between a member and the chair, may also stall rather than write down the disagreement. Both are visible to the direct question: ask, in one sentence, whether the chapter is ready to move forward or whether something in it needs rethinking first. Most people answer that honestly when it is put plainly.
If the answer is that something needs rethinking, you have recovered months. If the answer never comes at all, the obstruction is procedural rather than intellectual, and it is usually the moment patrons ask for a mentor outside the committee: someone to triage the feedback that does arrive, hold the chapter calendar, and keep the project moving during the weeks when the committee cannot.
Questions put to the house
How long is too long to wait for committee feedback?
Two weeks without acknowledgment merits a short follow-up, and a month without any substantive response merits a conversation with whoever administers doctoral candidates in your school. Many programs publish a turnaround expectation in the candidate handbook; read it before you decide you are being ignored, because a chair inside their published window is not late, only slow.
Should I contact a committee member directly?
For their own area, yes, with the chair copied in. About the chair's silence, no. Committees function on a clear chain, and a candidate who routes around the chair creates a problem that outlives the delay being complained about. If the chair is genuinely unreachable, the correct next door is the program or doctoral office, not another member.
Can a chair be changed if the silence continues?
It happens, and programs have a process for it, usually beginning with the doctoral office rather than with the chair. Consider the cost honestly first: a new chair reads the work fresh and may want changes the old one did not. Change chairs for an absent supervisor or a genuine mismatch of method, not for slow replies.
What should I do with the chapter while I wait?
Freeze it. The copy under review must stay identical to the copy you hold, or the comments that eventually arrive will refer to text that no longer exists. Spend the wait on work no comment can invalidate: references, appendices, instruments, ethics training, data preparation. That way the pause costs you calendar time rather than progress.