Your International Business department almost certainly has no single governed thesis-topic bank — a shared list of pre-vetted, live-tracked research topics students can draw from — and is instead running on whatever mix of a supervisor’s personal notes, an old orientation slide deck, and word-of-mouth from last year’s cohort happens to circulate. The predictable result: two students in the same cohort independently proposing near-identical studies of the same market-entry strategy or the same named multinational’s expansion case, discovered only after both have already invested weeks in a literature review, sometimes only when both proposals land on the same review committee’s desk in the same week. If this sounds like a small administrative inconvenience rather than a real institutional cost, it is worth tracing what actually happens next: a hurried reframing conversation under deadline pressure, a supervisor who now has to approve a second, rushed direction for one of the two students, and, in the worst case, two visibly similar theses that both make it to submission before anyone notices the overlap.
Why International Business is especially exposed to this problem
International Business theses cluster around a comparatively small set of high-visibility research angles — a handful of frequently studied market-entry modes (joint venture, wholly owned subsidiary, franchising, licensing), a rotating cast of well-known multinational case subjects whose expansion moves get covered in the business press, and a limited set of commonly used cross-country institutional-distance frameworks. That concentration is exactly what makes duplicate proposals more likely here than in a field with a wider natural spread of topics: without a governed bank tracking what has already been claimed, two students working independently, reading the same business-press coverage of the same high-profile multinational, will gravitate toward the same angle far more often than random chance would suggest.
What this actually costs your department right now
A discovered duplication late in a term costs more than an awkward conversation: one of the two students has to substantially reframe a project they have already invested real time in, under time pressure, while the department absorbs the reputational cost of two students in the same cohort submitting visibly similar work if the duplication is not caught before submission at all. Every hour a coordinator spends manually cross-checking a new proposal against recent past titles by memory, rather than against a governed, searchable bank, is time not spent on the substantive supervision questions that actually improve a thesis’s quality, and memory-based cross-checking degrades further the longer a coordinator has held the role, precisely as their institutional knowledge of past titles should in theory be improving. This is the same underlying pattern this site has documented for building and governing a thesis-topic bank in a Special Education program, arriving here in a different field with its own specific concentration risk around market-entry topics and named multinational case subjects.
Three ways the ad-hoc approach fails, specifically
First, the informal list nobody owns: a shared drive folder or a supervisor’s personal document that nobody is responsible for updating, so it drifts out of date within a term or two of being created. Second, no visibility across supervisors: a student working with one supervisor has no way to know what a different supervisor’s advisee proposed last term, so duplication risk is invisible until both proposals happen to reach the same review committee. Third, no signal on saturation: a genuinely interesting angle — a specific market-entry mode into a specific regional bloc, say — gets proposed independently by several students across consecutive cohorts because nothing tells a new student the angle has already been worked several times, even if each individual instance was not a literal duplicate of another.
What a governed bank actually prevents, concretely
A governed topic bank with a named owner, a live claimed/open status field, and a mandatory duplication check against the full historical archive before a topic goes live turns each of the three failure modes above into a solved, mechanical problem rather than a recurring fire drill. A student proposing “market entry mode choice for a European retailer entering Southeast Asia” gets checked against the archive before investing time in a literature review, not after a committee happens to notice the similarity to a project from three terms ago. A supervisor considering a named multinational as a case subject can see immediately whether that company has already been the subject of two theses in the past two years — not a hard block, but a flag that should prompt the student toward either a different subject or a genuinely different research question about the same company. The duplication check itself belongs at the same gate as the rest of proposal approval, which is why it fits naturally into the committee sequence this site describes for structuring a business school’s proposal-review workflow.
What this specifically requires for International Business’s topic concentration risk
Beyond the general governance discipline this site has already documented for other fields, an International Business bank needs one extra field most other disciplines’ banks do not: a running count of how many prior and current theses have used each named multinational as a case subject, and each market-entry mode as the central mechanism, updated as new topics are claimed. This turns the concentration risk described above from an invisible pattern into a visible one a coordinator can act on — capping how many active theses can simultaneously use the same named company as a primary case subject, for instance, or actively steering a new proposal toward a less-studied market-entry mode or a less-covered regional bloc when the popular ones are approaching saturation for that cohort. This is the same discipline this site’s piece on national data sources for a Sports Science thesis cohort applies to a different resource-tracking problem: name what is being tracked, record it centrally, and use the record to make a deliberate allocation decision rather than leaving the pattern to accumulate invisibly.
How this differs from a generic literature-review overlap
A department leadership team might assume this is just a normal literature-review overlap that any competent supervisor would catch, but the failure mode described here is specifically an institutional visibility problem, not an individual competence one. Two supervisors, each doing their own job well, each unaware of what the other’s advisee is proposing, is not a supervision failure — it is a structural gap in the department’s own information flow. A governed bank fixes the structural gap directly, by giving every supervisor visibility into what the whole cohort is proposing, rather than asking each supervisor individually to somehow know what colleagues across the department are separately approving. It also sits naturally beside the supervisor-matching decisions covered in allocating dissertation supervision in a business school, since knowing which topics are claimed is half of knowing which supervisors are genuinely available.
What a first version of this bank actually takes to build
A department does not need a sophisticated database to start. A single shared spreadsheet with five columns — topic, proposing student, supervisor, status (open, claimed, completed), and named case company or market-entry mode — covers the essential mechanics, provided one person is named as the owner responsible for keeping it current and running the duplication check on every new proposal before it is formally approved. The specific technology matters far less than the discipline of having one authoritative, actively maintained record that every supervisor checks before signing off on a new topic, rather than each supervisor relying on their own memory of what they have personally seen proposed.
Where Tesify fits
None of the ownership, duplication-checking or saturation-monitoring decisions above are ones a writing platform makes — they stay with the department coordinator and faculty. Tesify comes in only after a student has claimed a topic from the bank: it 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 student. For a department worried about visibly similar theses, that authorship position is the relevant point — two students on neighbouring topics still produce their own, separately written work.
What to expect in the first term after standing up the bank
The first term a department runs a governed bank tends to surface more apparent duplication risk than it prevents, not less — simply because the department can now see clustering it was previously blind to. A coordinator reviewing the newly compiled historical archive for the first time often discovers that a popular multinational case subject or market-entry mode has already been used more times in recent years than anyone individually remembered, since no single supervisor had visibility across every other supervisor’s advisees. This is not evidence the bank is causing a new problem; it is evidence the problem already existed and was simply invisible. The genuine payoff arrives from the second term onward, once every new proposal is checked against a truly current record before it is approved, rather than against whichever fraction of the department’s collective memory happens to surface in a hallway conversation.
Who should own this, practically
The most workable ownership model assigns the bank to whoever already coordinates thesis administration for the department — a programme coordinator or an assistant department chair — rather than creating a new role solely for this purpose. The owner’s actual job is narrow: run the duplication check on each new proposal before it is approved, update the status field the moment a topic is claimed or completed, and flag emerging concentration around a specific company or market-entry mode at a standing termly review. None of this requires specialist technical skill; it requires only that the responsibility is named explicitly and consistently exercised, rather than left as an informal task nobody is specifically accountable for. A department that has never assigned this ownership explicitly should expect the first assignment conversation to take longer than the actual ongoing task, since most of the work is deciding who owns it and confirming the rest of the faculty will actually route new proposals through the check, not the mechanics of running the check itself once that agreement is in place.
Frequently asked questions
Why is International Business especially prone to duplicate thesis proposals?
The field concentrates around a comparatively small set of market-entry modes and a rotating cast of well-covered multinational case subjects, so students working independently and reading the same business-press coverage gravitate toward the same angles far more often than in a field with a wider natural topic spread.
What is the minimum viable version of a topic bank?
A single shared spreadsheet with five columns — topic, proposing student, supervisor, status, and named case company or market-entry mode — plus one named owner who runs the duplication check on every new proposal before approval.
Should the bank block a popular multinational as a case subject?
Not outright. A running count per company and per market-entry mode should flag saturation, prompting the student toward a different subject or a genuinely different question about the same company, with a cap on simultaneous active theses if the department chooses one.
Who should own the topic bank?
Whoever already coordinates thesis administration for the department, such as a programme coordinator or assistant department chair, with the responsibility named explicitly rather than left informal.
Why does the first term with a bank seem to show more duplication, not less?
Because the department can now see clustering that was previously invisible. The payoff arrives from the second term, once every new proposal is checked against a current record before approval.
Does using Tesify raise an academic integrity concern?
No differently than for any other department. Every chapter written in Tesify is 100% written by the student; the platform does not select topics, check for duplication, or supervise the student’s research reasoning, all of which remain the department’s and supervisor’s responsibility.
Does the platform build or maintain the topic bank itself?
No. Building, owning and maintaining the governed topic bank — including the duplication checks and saturation monitoring described above — is a departmental governance decision.