Semmelweis University

Most of the structural problems examiners flag at medical institutions show up in predictable places. A common one: an introduction that describes a broad topic rather than a specific, answerable question. Another: a literature review that summarizes sources one by one instead of showing where they disagree or where a gap remains — which then leaves the methodology chapter with nothing clear to justify. Results sections sometimes drift into interpretation that belongs in the discussion instead, and conclusions occasionally introduce new claims that were never actually argued in the body of the thesis. Knowing the twelve-part shape (title page, abstract, acknowledgements, contents, introduction, literature review, methodology, results, discussion, conclusion, references, appendices) is only useful once each part is doing the specific job it's meant to do, not just occupying the expected slot.

A few patterns account for a disproportionate amount of lost thesis time: rereading sources because citation details weren't captured the first time, rewriting an introduction repeatedly before the research it introduces is actually finished, and trying to fix grammar and structure in the same editing pass.

The fix for each is roughly the same idea — capture details once, in the right order: log full citations as you read; draft the introduction properly only after the analysis and discussion are largely settled, since it needs to describe the thesis you actually wrote; and revise structure and evidence before you touch sentence-level wording, since a paragraph that gets cut doesn't need its grammar fixed first.

Medicine, dentistry, pharmacy is a reasonable description of the kind of work students at this institution are commonly pursuing, and program type is one of the clearest predictors of what a thesis here will actually demand. Technical and STEM-leaning programs typically require more rigor in the methodology chapter — data collection procedures, analysis technique, validity — while business- or applied-field programs more often require rigor in framing: picking a case or context that's genuinely worth analyzing, and building an argument from it that goes beyond description.