Can I Submit the Same Paper to Two Classes? What Turnitin Actually Does

Submitting the same paper to assignments in different classes means the two submissions can match each other in the Similarity Report. Submitting the same paper to two assignments within the same class is different: Turnitin automatically prevents those papers from matching each other. The score you get in the second class is a mechanical result of how Turnitin's database works — not a verdict about whether reusing your own paper is allowed. Whether you should submit the same paper to two classes is a question for your school's policy and your instructor, and Turnitin's documentation does not answer it.

The scenario is common: you wrote one strong paper for one course, and a second course has an assignment where the same work would fit. Submitting it twice saves time, and it is your own writing — so the worry is not "am I copying someone else," but "will Turnitin flag me against myself."

What usually triggers the panic is the number. A paper that scored 10% in the first class can come back 90%+ in the second, with the source list showing your own previous submission as the match. That looks like a false accusation, but it is the mechanism working as designed. The second class has no memory of your first submission being yours — it only knows that the text already exists in the student paper repository.

Turnitin's own help center describes the same-class case directly:

"If a student submits the same paper to more than one assignment within the same class, Turnitin automatically prevents these papers from matching against each other. This default 'self-match exclusion' is designed to allow students to submit early drafts of their work without their final submissions matching against their own previous drafts."

That sentence is the reason you can submit a draft, revise it, and resubmit without your later version matching your earlier one in the report. The same logic applies to two different assignments inside the same class: the system treats them as the same student's own work and hides the match.

One detail is worth knowing: those hidden matches are not deleted. The help center adds:

"These internal matches are automatically hidden but can be viewed in the Excluded sources section of the Similarity Report, where they can easily be re-added to the report if necessary."

So an instructor can restore a self-match if they want to see it. The exclusion is a default for the report's readability, not a rule that the text is invisible.

Cross-class submission is where the behavior flips. The same help center article says:

"An automatic exclusion does not occur if a student submits the same paper to assignments across different classes, provided at least one of those assignments was configured to save papers to the standard Turnitin repository."

Two conditions matter here:

• Different classes: the first class's submission is a separate entry in the database from the second class's submission, so the second report can match it.
• The repository setting: at least one of the two assignments must be configured to save papers to the standard repository. If the first course used a "no repository" draft setup, the stored first submission may not exist, and there may be nothing to match against. That "provided" clause is the reason the same action can produce different scores across courses — the instructor's assignment settings decide whether submitted papers are kept in the database at all.

When the second class's report shows your first submission as a source, the instructor has a tool that solves the display problem quickly. University FAQ pages that mirror Turnitin's documentation describe it: the instructor can exclude the source from the report, and the similarity score recalculates without that match.

That is an instructor-side action, not something you can do from your account. The distinction matters because it keeps the report legible: your instructor can see that the match is your own previous submission, mark it as excluded, and read the rest of the report for actual external matches.

What the instructor will not see is a label saying "self-plagiarism" or "allowed." The report shows a match and a source; interpreting that match — as reuse of your own work, as a policy violation, or as acceptable — is academic judgment that happens outside the report.

Here is the separation that most answers miss. Turnitin's product documentation explains what the score is but never says whether reusing your own paper is acceptable:

• The Similarity Report is a text-matching tool, not a plagiarism verdict.
• Whether submitting the same paper to two classes counts as self-plagiarism — or violates your school's own-work policy — is decided by your syllabus, your institution's academic integrity policy, and your instructor.

Many schools address re-use of your own work in their academic integrity policies, and expectations vary by course and level. A score of 90% in the second class is not, by itself, a finding of misconduct; but it is also not a sign the system approves of the submission. The mechanism and the policy are two different questions, and Turnitin's documentation only answers the first.

If you are considering submitting the same paper (or a large portion of it) to a second class, the practical checklist is short:

1. Read the second course's syllabus and assignment instructions — many explicitly state whether reusing your own prior work is allowed.
2. Ask your instructor directly before submitting. The question "may I reuse my own paper from another course?" is a normal question, and the answer settles the policy part that the report cannot.
3. Expect the second report to match your first submission if both assignments store papers to the standard repository. A high score in the second class is the mechanism working as documented, not a malfunction.
4. If the score appears and your instructor already knows the paper is your own, asking them to exclude the source is a legitimate readability fix — it does not change whether the reuse was permitted.

Turnitin's answer to "can I submit the same paper to two classes" is mechanical: same-class assignments exclude self-matches automatically; different-class assignments do not, as long as at least one stores papers to the standard repository. The second class's high score is the database recognizing your own earlier text — a match, not a verdict. Whether you should submit the same paper twice is a policy question your syllabus and instructor answer. Check the policy, ask the question, and let the report do what it is designed to do: show matches, not decisions.