Divide the next steps by dependency
Imagine a fictional student waiting for approval of an analysis plan. They might still document variables or organize references. Running the final analysis and treating it as approved would be a different choice.
The useful distinction is between reversible preparation and work that commits the project to an unapproved direction. Institutional ethics or data-access requirements cannot be bypassed simply because a response is slow.
Make the request answerable
“I am waiting on whether to use outcome A or B. That choice affects the analysis due next week. Could we confirm the choice by Thursday, or identify an alternative reviewer? I can continue the data documentation in the meantime.”
This invented message names the bottleneck and offers context. It does not prescribe the right deadline or communication style for every relationship.
Clarify the review arrangement
Cornell's faculty advising guide discusses expectations and regular feedback. In any program, useful agreements can include the amount of material to send, expected turnaround, and what happens when the usual reviewer is unavailable.
A reminder is easier to interpret when it refers to an agreed process rather than an unspoken expectation.
If the delay becomes a pattern
Repeated delays that threaten milestones may require help from a director of graduate study, committee member, or other appropriate program resource. The route depends on the institution and the nature of the concern.
The student is not necessarily responsible for solving every capacity problem in the advising relationship. Keeping a factual record of requests and affected milestones can make the problem easier to discuss.
While waiting, the goal is to preserve useful work and make dependencies visible. Filling every hour with activity is less helpful than knowing which missing decision is actually preventing the project from moving.
