A Political Science or IR thesis lives or dies, for most readers, on 200 words they will read before deciding whether to read anything else — and most of your programme’s abstracts are not written to survive that test. They summarise the topic instead of stating the argument, they never name the case-selection logic or the theoretical framework the thesis actually uses, and they bury the finding on page one of the introduction rather than the first sentence of the abstract. Every external reader who only ever sees the abstract — a REF or quality-audit panel, a policy contact, a future employer — is forming a judgement about your programme’s rigour from exactly the section your supervisors spend the least time teaching. That gap between how much a paragraph is read and how little it is taught is the actual problem this piece addresses, not a general complaint about student writing quality.
Why Political Science and IR abstracts fail in a specific, recurring way

The generic abstract-writing advice every student has already seen — state the topic, the method, the findings, the implications — is not wrong, but it is not specific enough to fix what actually goes wrong in this field. A Political Science or IR abstract needs to do four things a generic template does not prompt for: name the research question as a genuine puzzle, not a topic (“why did X policy fail in Y country” rather than “this thesis examines X policy in Y country”); state the case-selection logic, because in a discipline built on comparative and single-case designs, why this case and not another is itself part of the contribution; name the theoretical framework being applied or tested — realist, liberal, constructivist, or a specific middle-range theory — since a reader in this field is scanning for that positioning in the first few lines; and state the finding, not just the topic, in the abstract’s final sentence, because a policy-facing or comparative-politics reader wants the conclusion before deciding whether the argument that gets them there is worth their time.
What this is actually costing your programme
A weak abstract does not just under-sell a good thesis to an external reader — it is graded, and it shapes the first impression an internal examiner brings into the viva before a single question is asked. Multiply that across a cohort and the cost compounds: examiners writing the same corrective comment on abstract after abstract each cycle, supervisors spending review-meeting time re-explaining case-selection logic individually rather than teaching it once at cohort level, and — for departments tracked on research quality metrics — a programme’s public-facing thesis abstracts consistently under-representing work that is often methodologically sound but poorly framed in the one paragraph most people will ever read.
A rubric that names what “good” actually contains

| Element | What weak abstracts do instead | What the rubric should require |
|---|---|---|
| Research question | States a topic (“this thesis examines…”) | States a genuine puzzle or tension the thesis resolves |
| Case selection | Names the case with no justification | States why this case, and what it is a case of, in comparative or theory-testing terms |
| Theoretical framework | Often absent entirely from the abstract | Names the framework or tradition being applied or tested in one clause |
| Finding | Ends on the topic, not the conclusion | States the actual finding as the abstract’s final sentence |
Publishing this table, not just an abstract word-count limit, in the dissertation handbook gives students and supervisors a shared, checkable standard rather than an implicit, supervisor-dependent sense of quality that varies across a cohort. A rubric this specific also gives a moderation meeting something concrete to check against when two supervisors compare a sample of abstracts before grades are finalised — the same cross-marker calibration exercise that other departments on this site already run for extended written work, applied here to a single, high-leverage paragraph rather than the whole document.
The introduction has the same problem, one level deeper
The first page of the introduction inherits the same failure mode at greater length: a scene-setting paragraph about the general importance of the topic, several paragraphs in before the actual research question and its puzzle are stated plainly. A reader — examiner or otherwise — should be able to identify the research question, the case, the theoretical lens and the argument’s headline claim from the first page alone, the same four elements the abstract rubric above requires, just given room to breathe. Teaching the abstract and the introduction’s opening page as one connected skill, rather than two separate assignments, is what makes the standard actually stick — students who learn to compress their argument into 200 words write a sharper first page, not just a better abstract.
A worked comparison: the same thesis, two abstracts
A weak abstract for a thesis on electoral reform might read, in substance, as a topic summary: this thesis examines the introduction of proportional representation in a given country and its effects on party system fragmentation. It names a topic and a country and stops there — no puzzle, no case-selection logic, no framework, no finding. A rubric-compliant abstract for the identical underlying research states the puzzle (why did fragmentation increase sharply in some post-reform cases but not others), the case-selection logic (this country selected as a most-similar case to isolate the reform’s effect from confounding institutional variables), the framework (institutionalist theory of party-system formation), and the finding (fragmentation increased specifically where district magnitude exceeded a certain threshold, a conditional relationship the existing literature had not specified). The underlying research and its quality have not changed between the two versions — only whether the abstract actually communicates why the finding matters and how it was reached, which is precisely the difference an external reader who never opens the full document will notice.
Where this sits relative to other institutional quality-assurance work
A published abstract rubric is a small, specific instance of the same calibration discipline covered more broadly in how to get consistent marking on extended written work — criteria specific enough that two examiners would flag the same gap identically, decided before students draft rather than corrected individually afterward. It is also worth pairing with attention to the deposit-stage formatting check described in why your deposit desk keeps holding degrees for metadata — a well-written abstract that fails the deposit desk’s format check on the same page still delays a conferral date, so the content fix and the format fix are worth solving together rather than as two separate, uncoordinated problems.
Where Tesify removes the actual bottleneck

Your supervisors know exactly what a strong abstract and opening page look like — the constraint is never expertise, it is that giving every student in a cohort individual, structured feedback on this specific skill, at the specific point in the term when they are drafting it, does not scale to a supervisor’s actual available hours. The Tesify AI Writing Editor for Institutions walks a student through a structured prompt sequence built around exactly the four rubric elements above — puzzle, case, framework, finding — inside a workspace supervisors can see, so what arrives at the supervision meeting is a draft that already names its case-selection logic and theoretical framework, rather than a topic summary a supervisor has to redirect from first principles. That converts a recurring, cohort-wide coaching task into a structured first pass, freeing supervision time for the argument itself.
A free departmental pilot, not a procurement process
You do not need a business case, a committee cycle, or a signed institutional contract to find out whether this actually changes your next cohort’s abstracts. A free departmental pilot puts the structured prompt sequence and supervisor visibility in front of one Political Science or IR cohort for one dissertation cycle, with no procurement process and no commitment beyond that cycle — a low-friction way to test one specific, narrow problem before deciding whether a department-wide rollout is worth a formal evaluation.
Where this connects to the writing-standard your department may already have
If your department already has a broader departmental writing standard, this rubric is the Political Science and IR-specific instance of the same underlying discipline — see how to write a departmental writing standard for theses for the general framework. A field-specific abstract rubric is exactly the kind of concrete, checkable addition that general writing standard is designed to host, rather than a competing, separate document supervisors have to reconcile with it. Adding this rubric as a named appendix to the existing standard, rather than a stand-alone handout circulated separately, also avoids the version-control problem of two documents drifting out of sync the next time either one is revised.
Frequently asked questions
How much does this cost?
The departmental pilot is free and time-boxed to one cohort’s dissertation cycle. Institutional licensing beyond the pilot is priced against your department’s cohort size once the pilot has shown it is worth scaling.
Where is student data processed, and does that raise data-protection concerns?
Data residency and processing terms are set out in the institutional data processing agreement provided before any pilot begins — confirm the specific residency terms relevant to your jurisdiction with your procurement or data-protection office before starting.
Does this replace a supervisor’s judgement on whether the abstract is actually good?
No. It structures the student’s first draft against the four rubric elements so supervisor time goes to judging whether the puzzle, case-selection logic and theoretical positioning are actually sound, not to prompting a student toward the basic structure a rubric can prompt for directly.
What is the integration effort for one department to run a pilot?
Minimal — a departmental pilot does not require SSO or LMS integration to start; students access the workspace directly, and integration becomes relevant only if a wider institutional rollout follows.
Does structured prompting for the abstract raise an academic-integrity concern?
No — the prompts ask the student to state their own research question, case, framework and finding; they do not generate content on the student’s behalf, and supervisors see every draft exactly as they would any other supervised drafting stage.
Does the rubric apply to comparative politics and single-case IR theses equally?
Yes, with the case-selection element phrased differently for each — a comparative design states why these specific cases were selected for comparison, a single-case design states what the case is a case of and why it tests or extends the chosen theoretical framework.
Should the abstract rubric be taught separately from the introduction-writing session?
No — teaching them together as one connected skill is what makes the standard stick. Students who learn to compress their argument into a rubric-compliant abstract consistently write a sharper opening page of the introduction as well, because both sections require naming the same four elements.
Who should own the abstract rubric once it is published?
The programme lead or dissertation-module convenor, introduced at the same session where the research question and case-selection logic are first taught, not left as a late-stage editing note supervisors each apply differently.
