How a thesis proposal is written: six questions I ask myself
Question 1: What exactly needs to be submitted for a thesis proposal?
Most schools require three things: the basis for topic selection (background + current research status + significance), the research content and technical route, and the schedule. First get the template for your school and major, then break down the tasks backward according to the template sections; this saves more time than writing by feel.
Question 2: I still can't settle on a title—what's the problem?
The problem is that the research question hasn't been written as one sentence. My approach is first to write clearly "what problem I want to solve, what the research object is, and where the boundaries are," then give this sentence to a tool to break down the literature search dimensions—it provides the search terms, I choose the direction, rather than repeatedly piecing together keywords in the search box. I use MuchSci's Paper Search Assistant to validate the direction: the literature comes from 180 million articles in Crossref, supports exact or fuzzy search by title, author, and DOI, and can also filter by year and citation count. After a hit, it provides the DOI and automatically fills in citation information such as authors, journal, year, volume, issue, and page numbers. When you can't find anything, at least you can tell whether it's a "blank direction" or "the keywords weren't chosen correctly."
Question 3: How can I write the current research status so it doesn't look copied?
The status isn't rearranging abstracts; it's answering "where others have gotten to, where they're stuck, and therefore what I need to do." Before writing, I first build a literature ledger (number, author-year, research question, method, conclusion, limitations, whether cited, citation location), have the tool break down paper by paper the research question, method, conclusion, and limitations to fill in the table, then rearrange by theme—the order of paragraphs emerges on its own.
Question 4: Can't draw the technical route diagram?
If you can't draw it, usually the steps haven't been broken down finely enough. I first use the Office Assistant Agent to generate a first draft of the proposal PPT (input the project title, research question, and preliminary ideas; output includes research background, current status, methods, and technical route structure), then ask of each page "what are the inputs and outputs of this step," and places missing links are immediately exposed.
Question 5: What if I can't finish reading English literature?
Two layers: read review articles thoroughly to build understanding, and read the original text of highly relevant original papers. For translation, I use paragraph-level parallel reading (two-way Chinese-English academic translation, preserving formula and terminology consistency, supporting full PDFs). The translation only helps me understand; parameters, values, and chemical formulas are always checked against the original. Keep a separate glossary of "Chinese translation + original English term"; do not use the Chinese translation for searching.
Question 6: What will the teacher ask?
Mostly "why do this" and "how do you prove it." Before the defense, explain the outline to the air once: if you only talk about these, does the main line hold up? The places you can't explain clearly are where the structure has problems.
For this Graduate Student AI Assistant, I divide usage by three tasks: "search, organize, produce a first draft," and do the rest myself.
Three boundaries: keep the line of academic integrity yourself—the viewpoints and conclusions must be your own; translations are not factual evidence; confirm your target school's plagiarism check and AI use regulations yourself. Costs are billed by usage—MuchSci is measured by credits, paper analysis and document generation deduct credits based on actual processing volume, free registration gives 3960 credits as a trial quota, and uploaded papers and data are not used for model training.