A research gap is a defensible claim about missing knowledge or capability for a specific question and context. In a thesis, support the gap with sources and explain how your work addresses it.
Different fields use different labels for gaps, and no single taxonomy applies everywhere. Use Table Table 1 as a checklist while reading. Identify the point at which each paper’s claims stop being justified.
| Gap pattern | What it means (in practice) | Example (logistics / OR) | How you address it in a thesis |
|---|---|---|---|
| Context / Setting | Evidence exists, but not under your constraints or decision environment | A method is tested in a toy setting, but your case has real-time constraints and noisy data | Explain why the context matters; adapt the approach; evaluate under your constraints |
| Model / Assumptions | Common assumptions likely drive the results, and they do not hold in your case | Papers assume deterministic demand, but your setting has stochastic arrivals and cancellations | Make assumptions explicit; relax/replace key ones; run sensitivity analysis |
| Method / Algorithm | The problem is known, but the available solution methods do not scale or do not apply | An exact formulation exists, but solvers time out on realistic instance sizes | Implement a solid baseline; justify design choices; report trade-offs (quality, time, robustness) |
| Evaluation / Benchmark | Claims exist, but comparisons are incomplete or weak | A new heuristic is reported without strong baselines, ablations, or a clear evaluation setup | Define baselines and metrics; compare fairly; document data, instances, and experimental protocol |
| Concept / Definition | Key terms are used inconsistently, so results are hard to compare | “Service level” is defined differently across studies | Define terms precisely; connect measures to your research question; justify operational definitions |
| Integration / Workflow | Pieces exist separately, but no end-to-end workflow is evaluated in a realistic setting | Forecasting and routing are studied separately, but not as one pipeline | Build an end-to-end pipeline; show where errors propagate; discuss deployment constraints |
Connecting a gap to the thesis contribution
A useful gap leads to a concrete contribution and evaluation plan. Most theses extend existing work from assumptions A, B, and C to a setting that requires D, E, and F. Claims that nobody has studied a broad topic are rarely defensible.
This mirrors a common move in academic introductions: summarize what is known, then show what is missing, then state what your work adds (Swales, 2004). Use Table Table 1 as a checklist while you read.
Swales’ CARS model (Create A Research Space) describes introductions as a sequence of rhetorical moves (Swales, 2004):
- Move 1: Establish a territory: show the topic matters; summarize what the field already knows.
- Move 2: Establish a niche: show what is missing, limited, or unresolved (this is where your gap statement lives).
- Move 3: Occupy the niche: state what you will do and what you will contribute (including how you will evaluate it).
Practical template
Use this structure to turn reading into a defensible thesis pitch:
- What exists: “Prior work on X focuses on …”
- What is missing: “However, Y is underexplored/unclear, especially in …”
- Why it matters: “This matters because …”
- What you do: “This thesis addresses Y by …”
- How you show it: “We evaluate by … (datasets, baselines, metrics).”
Revising broad gap claims
- Broad: “There is no research on X.” Specific: “Research on X is limited in settings with …”
- Broad: “No one considers Y.” Specific: “Only a subset of studies considers Y, and the results are mixed or limited because …”
- Broad: “This has never been done.” Specific: “To our knowledge, there is limited evidence on … in …”
If you are doing a thesis with a strong literature component, keep your review traceable (search log, inclusion criteria). That makes your gap claims easier to defend (Page et al., 2021; Webster & Watson, 2002).