First locate the source of authority
A program handbook controls different questions than an advisor preference. An instructor controls an assignment differently from the Graduate School controlling degree requirements. Knowing who owns the decision tells you where clarification should come from.
Search for the written rule before asking for interpretation
Program handbooks, syllabi, rubrics, milestone forms, and graduate-school policies often answer part of the question. Reading them first lets you ask about the remaining ambiguity instead of asking someone to repeat what is already documented.
Ask bounded questions
“How long should this be?” may be too broad. “The rubric does not specify a length; would 12 to 15 pages be appropriate if the analysis is complete?” gives the other person something concrete to confirm or adjust.
Use examples carefully
Prior theses, successful proposals, sample assignments, or advanced students can reveal local conventions. But examples are evidence of what has been accepted, not necessarily rules that every student must copy.
Recognize the hidden curriculum as a real information problem
Brown’s Graduate School has explicitly run programming around the “hidden curriculum” and unspoken language of graduate education. The existence of such programs reflects a broader reality: some expectations are transmitted socially rather than through formal documents.
The practical response is to build multiple information channels rather than assuming uncertainty means you are missing something obvious.
Convert the ambiguity into a list of decisions
"I do not know what they expect" can refer to several different uncertainties: the quality standard, the required format, the deadline, the amount of independence, the advisor's preferred workflow, or what counts as satisfactory progress. Write down the specific unknowns. Each one may have a different source of truth.
Program handbooks, syllabi, milestone forms, rubrics, and written policies should be checked before relying on informal assumptions. For expectations that are genuinely discretionary, a short conversation can clarify whether the supervisor wants an outline, full draft, preliminary analysis, regular updates, or a more independent approach.
Confirm high-cost assumptions early
If an assumption could cause weeks of unnecessary work, verify it before proceeding. Examples include whether a dataset is acceptable, whether a method satisfies the program requirement, whether a committee member can serve, or whether the scope is appropriate for the milestone. Early clarification is usually cheaper than correcting a polished deliverable built around the wrong interpretation.
