Why does Turnitin flag my theoretical framework?
When you read the similarity report and see a block highlighted as “insufficient theoretical grounding,” the software isn’t accusing you of plagiarism in the legal sense. It’s simply telling you that the phrasing you used matches text that already exists in the database. In a doctoral prospectus, the theoretical framework is supposed to be a synthesis of existing ideas that you then extend with your own argument. The module guide for mechanical‑engineering PhDs usually lists three exact terms that examiners look for: gap identification, critique of prior models, and justification for a new approach. If your draft repeats the same stock language that appears in a rejected proposal or a published review, Turnitin will flag it because the wording is common, not because you copied the underlying analysis.
For example, you might have written:
“Current finite‑element models assume linear elasticity, which fails to capture the nonlinear stress‑strain behavior observed in high‑temperature alloys.”
If a seminal paper or a previous prospectus used the phrase “fails to capture the nonlinear behavior,” the algorithm will register a match. The key is that the exact wording is what triggers the alert, not the idea itself. Your supervisor will care more about whether you can demonstrate original reasoning, not whether a few adjectives are identical to someone else’s.
So the first thing to do is to locate the highlighted sentences, compare them with the source Turnitin suggests, and ask yourself: does the source present the same logical chain, or is it merely a shared description of a known limitation? If it’s the latter, you can keep the idea but rephrase it in your own voice and cite the original work.
What specific part of the prospectus triggers the similarity alert?
The prospectus is divided into several required sections: problem statement, literature review, theoretical framework, methodology, and expected contributions. The similarity report usually groups matches by section, and the “theoretical framework” is the most vulnerable because it often contains dense, discipline‑specific terminology. The technical dead end here is twofold.
First, Turnitin’s settings may be configured to flag “short phrases” (four‑word sequences) as matches. In engineering writing, phrases like “finite element analysis of” or “nonlinear dynamic response of” appear in dozens of papers. If the software is set to a low threshold, it will generate a high similarity score even when you have not copied any substantive content.
Second, the prospectus template you are using might have a pre‑filled “example paragraph” that you inadvertently left unchanged. Many departments provide a sample framework that reads:
“The existing models, such as XYZ and ABC, lack the capability to account for temperature‑dependent material degradation, leading to inaccurate predictions under service conditions.”
If you copied that example verbatim, Turnitin will treat it as a match to the department’s own repository. The remedy is to replace the placeholder with your own critique, citing the original models (XYZ, ABC) and then articulating why they fall short for your specific research question.
How can I prove the work is my own and calm the integrity fear?
Turnitin does not replace human judgment; it merely highlights overlap. The integrity fear comes from the possibility that a committee member might interpret the similarity score as academic misconduct. Here are three legitimate ways to lower risk while preserving the scholarly content you need.
- Paraphrase aggressively. Change the sentence structure, swap nouns for verbs, and insert your own connective phrases. For the earlier example, you could write: “Although XYZ and ABC have been widely adopted, they ignore the degradation of material properties at elevated temperatures, which compromises predictive accuracy in real‑world applications.”
- Insert in‑text citations wherever you discuss a known limitation. A simple citation (e.g., Smith 2020) signals that the idea is grounded in existing literature, not invented on the spot.
- Provide a brief “original contribution” sentence immediately after the critique. For instance: “My proposed model incorporates a temperature‑dependent constitutive law, filling the gap identified above.” This makes it clear which part is your novel work.
When you meet with your supervisor, bring the Turnitin report, point out the highlighted passages, and show the revised version side‑by‑side. Demonstrating that you understand why the match occurred and that you have taken concrete steps to differentiate your language will usually satisfy any concerns.
Do not submit the same wording without citation. Even if the idea is common knowledge in mechanical engineering, the exact phrasing belongs to the original author.
What concrete steps should I take tonight and this week?
Time is limited, especially when you have lab work and coursework competing for attention. Below is a practical checklist you can start on immediately, followed by a short weekly plan.
- Open the Turnitin report and copy the exact sentences flagged in the “theoretical framework” section.
- Search each sentence in Google Scholar or your department’s repository to locate the source.
- For each match, write a one‑sentence summary of the source’s main point in your own words.
- Rewrite the original sentence using a different grammatical structure and add a citation to the source you just summarized.
- Run the revised paragraph through a free plagiarism checker (e.g., SmallSEOTools) to verify that the similarity drops below 15%.
- Send the updated draft to your supervisor with a brief note: “I revised the flagged sections based on your feedback; please let me know if further changes are needed.”
Weekly timeline:
- Day 1–2: Complete the checklist items above.
- Day 3: Incorporate any supervisor comments and double‑check the reference list for completeness.
- Day 4–5: Polish the rest of the prospectus (methodology, timeline) so the document feels cohesive.
- Day 6: Submit the final version to the department portal, keeping a copy of the final Turnitin report for your records.
Following this plan ensures you address the similarity issue without sacrificing the intellectual depth of your framework.
Should I rewrite the section or explain the similarity to my supervisor?
The decision hinges on three criteria: the magnitude of the similarity score, the nature of the overlap, and your supervisor’s typical response style. The table below helps you weigh the options.
| Option | Risk of Misinterpretation | Time Required | Supervisor Reaction |
|---|---|---|---|
| Rewrite only | Low if you fully rephrase; moderate if you keep some phrases | 2–3 hours | Usually appreciative of proactive effort |
| Explain only | Higher if similarity > 20 % | 1 hour (email) + meeting | Depends on supervisor’s tolerance for raw similarity |
| Rewrite + Explain | Minimal | 3–4 hours total | Best outcome; shows diligence and transparency |
If the similarity percentage hovers around 15% and the overlap consists of standard technical phrasing, a brief explanation may suffice. However, if the flagged block is longer than a sentence or includes a distinctive argument, it’s safer to rewrite and then inform your supervisor of the changes. This dual approach demonstrates that you respect academic integrity while also valuing their time.
In practice, most mechanical‑engineering PhD committees expect you to own the language of your framework. A concise email that says, “I noticed Turnitin highlighted my critique of XYZ models; I have reworded the passage and added a citation to Smith 2020,” followed by the revised paragraph, usually settles any lingering doubt.
Take a breath. The prospectus is a work‑in‑progress, and similarity alerts are a normal part of the drafting cycle. By clarifying the source of the overlap, rephrasing responsibly, and communicating openly with your supervisor, you turn a moment of anxiety into an opportunity to strengthen your scholarly voice.