Otago Polytechnic

Most of the structural problems examiners flag at technical and engineering-focused 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.

Most thesis timelines don't fail because of one big mistake — they slip a little at a time. Sources get read but not logged with full citation details, so a useful quote later has no traceable origin. A chapter gets polished at the sentence level before its structure has been checked, so the polishing has to be redone once a paragraph gets moved or cut. Feedback comes back from a supervisor but doesn't get turned into a specific action, so the same comment resurfaces on the next draft.

Building in a running reference list, a structural revision pass before a line-level one, and a simple log of supervisor feedback (comment, action, done) tends to prevent most of this before it compounds.

Thesis scope tends to track the kind of program a student is in more than almost anything else. Given the programs typically associated with this institution — IT, construction, hospitality — a thesis here plausibly sits somewhere on a spectrum from data- and methodology-heavy (common in technical, engineering or computing programs) to applied and case-study-driven (common in business, management and other professionally oriented fields). Knowing roughly where your own program sits on that spectrum is more useful early on than any generic length or difficulty guideline.