A research-methods committee evaluates a History thesis’s problem statement by checking that it names a specific, bounded historiographical gap — not just a topic — states why that gap matters to the field’s current conversation, and is answerable with the sources actually available to the student. A sound topic with a vague or unanswerable problem statement is the single most common reason a proposal comes back for revision before it ever reaches full committee review. This is a narrower, earlier check than the calibration work this site has documented for consistent marking on extended written work and departmental thesis writing standards — those cover the finished document; this covers a single paragraph, reviewed before a student has written anything else.
What is a research-methods committee actually checking for in a problem statement?
Three things, checked in a fixed order rather than as one impressionistic read. First, specificity: does the statement name a bounded period, place, actor group or documentary corpus, rather than gesturing at a broad era or theme. Second, the historiographical gap itself: does the statement identify what existing scholarship has not addressed, misread, or left under-evidenced, rather than simply describing what happened. Third, feasibility: given the archives, digitised collections or oral-history access the student has actually identified, can the stated problem be answered within the thesis’s scope and timeline, or does it implicitly require sources the student has not confirmed access to. A statement can pass on specificity and gap while failing on feasibility, and a committee that only checks the first two will approve proposals that stall months later at the archive door.
Why do problem statements fail even when the topic itself is sound?
The most common failure is a topic dressed as a problem statement: a student names an interesting period or figure, describes it accurately, and stops there, without stating what question about it remains genuinely open. A second common failure is a gap claimed but not demonstrated — the student asserts existing scholarship has “overlooked” something without having actually surveyed the relevant literature closely enough to know whether that is true, which a committee catches by asking the student to name the two or three closest existing works and state precisely what they do and do not address. A third failure, more specific to History than to some other fields, is a problem statement built around a source the student has not yet confirmed is accessible — a specific archive box, a private family collection, an oral-history subject — discovered to be restricted, lost or unwilling only after the proposal is approved.
What does a strong versus a weak problem statement actually look like?
The pair below is illustrative and fictional, built to show the difference in kind rather than to represent any real thesis or any real claim in the literature. Weak (topic, not problem): “This thesis examines the role of women in the local textile industry in a mid-sized English town during the Industrial Revolution.” This describes a subject area but names no gap and no question. Strong (bounded, gapped, feasible): “Local labour histories of this town’s textile mills treat women’s wage disputes as largely undocumented before trade-union records begin; this thesis asks whether the surviving 1830s–1850s petty-sessions records for the town, in which some wage disputes between mill workers and employers came before local magistrates, can recover an earlier and more specific picture of how women workers contested wages before formal union representation existed.” The strong version names a specific claim in the existing literature, the specific source that might close the gap (a defined run of court records over a defined date range), and implicitly signals feasibility by naming a source the student would need to have already located.
How does a committee turn this into a repeatable rubric rather than subjective judgment?
A workable rubric scores each of the three checks (specificity, gap, feasibility) on a simple three-point scale — not present, partially present, clearly present — with a short required justification line for any score below the top mark, rather than a single holistic pass/fail judgment that varies by which committee member happens to read it. Feasibility should carry a mandatory sub-question: has the student named the specific archive, collection or repository the problem statement depends on, and is there documented evidence (a catalogue reference, a prior email confirming access, a digitisation project’s public listing) that it is actually reachable within the thesis timeline. A proposal that scores well on specificity and gap but cannot answer this sub-question should be returned for a feasibility check before any further review, not approved on the assumption the student will sort out access later. The scoring itself should be recorded, not just discussed — a one-page form per proposal, kept alongside the proposal file, with the three scores, the justification lines, and the reviewer’s name and date. This record does two things a purely verbal review cannot: it gives a student concrete, dated feedback to work from rather than a remembered conversation, and it gives the programme a body of evidence, accumulated proposal by proposal, that a later curriculum review or accreditation self-study can draw on to show the review process is applied consistently rather than left to each committee member’s individual judgment.
How does this differ from assessing the whole proposal?
A problem-statement review is deliberately narrower than a full proposal review: it is a single, early gate on one paragraph, not an evaluation of the theoretical framework, methodology or literature review that come later in the same document. This site’s piece on how a research-methods committee assesses hypothesis and variable quality covers an analogous early-stage quality check for a different discipline and a different unit of analysis — variables and hypotheses rather than a historiographical problem statement — and the two exist for the same institutional reason: catching a structural weakness in the first paragraph before a student and supervisor invest months building a full proposal on top of it. Running the check this early, on this one paragraph, is what makes it fast enough to actually happen before the rest of the proposal is written, rather than being folded into a single slower review at the end.
Should the review differ for a documentary-history thesis versus an oral-history thesis?
The three checks stay the same, but the evidence a committee should ask for under feasibility differs materially by sub-field. For a documentary-history proposal built around archival material, feasibility evidence looks like a catalogue reference, a confirmed reading-room appointment, or a digitisation project’s public listing showing the material is already available online. For an oral-history proposal, feasibility evidence looks different again: has the student identified specific, named or nameable potential interview subjects, confirmed at least provisional willingness to participate, and secured the ethics approval an interview-based project requires before data collection can begin — a step a documentary-history project reliant on already-deposited archival material typically does not face in the same form. A committee applying a single generic feasibility question across both sub-fields risks either being too lax with the oral-history proposal’s ethics-and-access chain or asking a documentary-history proposal for a form of evidence, such as named participants, that does not apply to its source base at all.
What happens when a problem statement fails the review?
The proposal should return to the student and supervisor with the specific failed check named — not “needs more work,” but “the gap claim is asserted without naming the closest existing scholarship” or “the feasibility of accessing the named archive is not yet confirmed” — so the revision addresses the actual deficiency rather than a general tightening of prose. A committee that tracks which of the three checks (specificity, gap, feasibility) most often causes a return, across a full cohort and over several years, gains a genuinely useful piece of programme-level information: if feasibility is the recurring failure, that points to a gap in how early students are taught to confirm archive access, not a weakness in individual students’ writing. A programme that finds specificity is the recurring failure, by contrast, is telling itself something different — that students are arriving at the proposal stage without enough grounding in how a bounded historical question differs from a broad thematic interest, which points toward an earlier intervention in coursework rather than a fix at the proposal-review stage itself. Either finding is only visible if the review is recorded consistently enough, across enough proposals, to spot the pattern — which is the practical argument for the one-page scoring record described above, independent of its value to any single student’s revision.
Should the same review apply to a Master’s thesis and a doctoral dissertation?
The three checks — specificity, gap, feasibility — apply at both levels, but the bar for each should scale with the degree. A Master’s-level problem statement can reasonably narrow an existing debate without claiming to resolve it; a doctoral-level statement is generally expected to identify a gap substantial enough to sustain several years of original research, not just one chapter’s worth of new material. A committee applying an identical rubric with an identical pass bar at both levels risks either holding Master’s students to an unreasonably high originality standard or approving doctoral proposals whose gap is too narrow to sustain a full dissertation, so the rubric’s three checks should stay constant while the department documents, separately for each degree level, what “clearly present” concretely requires.
Where Tesify fits
None of the specificity, gap or feasibility judgments above are ones a writing platform makes — that stays with the research-methods committee and the student’s own archival groundwork. Tesify is a thesis-writing workspace already used by 9,000+ students across more than 15,000 chapters, and every chapter in it is 100% written by the candidate. For a History committee, that matters in one narrow way: the problem statement it scores remains the student’s own formulation, so the rubric is assessing the candidate’s judgment rather than a tool’s.
Frequently asked questions
What are the three things a research-methods committee checks in a History problem statement?
Specificity (a bounded period, place, actor group or corpus, not a broad theme), the historiographical gap (what existing scholarship has not addressed or has under-evidenced), and feasibility (whether the sources the statement depends on are actually accessible within the thesis timeline).
What is the most common reason a problem statement fails review?
A topic described accurately but presented as if it were a problem statement, with no specific question left genuinely open, and no engagement with what the closest existing scholarship has already established.
How is a problem-statement review different from reviewing the whole proposal?
It is a narrower, earlier check on a single paragraph, run before the theoretical framework, methodology or literature review are evaluated, so a structural weakness is caught before a student invests months building the rest of the proposal on top of it.
Can a problem statement have a real historiographical gap but still fail?
Yes, if the sources it depends on have not been confirmed accessible. A genuine gap claim built around an archive the student has not verified is reachable within the thesis timeline should be returned for a feasibility check before further review.
What should feedback on a failed problem statement include?
The specific check that failed, named directly — for example, an unsupported gap claim or an unconfirmed archive access — rather than general feedback that the statement needs more work, so the student’s revision targets the actual deficiency.
Can this review process reveal something about the programme as a whole?
Yes. Tracking which of the three checks most often causes a return, across a cohort and over time, can reveal a systemic gap — for instance, if feasibility failures recur, that suggests students need earlier training in confirming archive access, not that individual students are writing poorly.
Is the strong-versus-weak example in this piece from a real thesis?
No. Both examples are illustrative and fictional, built to demonstrate the difference between a topic and a bounded, gapped, feasible problem statement, not to represent any actual student’s work.