Will my own earlier draft match my resubmission?

Resubmitting to the same assignment overwrites your previous submission, and Turnitin states that overwritten submissions do not match against each other. Submitting the same work to a second assignment is the different case: Turnitin's own scoring examples describe a student whose final draft came back at 100% after they had submitted drafts of the same paper, and the same page's description of what a submission is compared against explains why.

Same assignment: safe by design. Second assignment: this is the one that produces the horror-story screenshot.

Turnitin's student guidance on resubmitting and managing submissions puts it in one sentence:

"As your resubmission overwrites any previous submissions, they will not match against each other in your Similarity Report."

The same page sets the limits. If your instructor has enabled resubmissions and the due date has not passed, you may resubmit up to three times in 24 hours, with the 24 hours counted from your first submission of that day. Resubmitting overwrites the previous file, so any grading attached to it is lost, which is why that page tells you to check whether the work has been graded before you upload again.

There is a second reason to care about the count. A separate page on generating a new Similarity Report after resubmission says the three immediate-report attempts are shared between you and your instructor, and that one of your attempts is used if they resubmit on your behalf. So an instructor who uploads a corrected file for you has spent one of yours.

If you have ever resubmitted and watched the similarity icon sit there greyed out, that is not the system being slow. Turnitin's page on accessing the Similarity Report says:

"Overwritten or resubmitted files may not generate a new Similarity Report for a full 24 hours. This delay is automatic and allows resubmissions to correctly generate without matching to the previous draft."

Read that second sentence twice. The delay is the mechanism that stops your own draft from matching you. If you are on a deadline and a report has not appeared, the useful thing to know is that waiting is doing something, and that the fourth submission of the day is the one that lands in the queue rather than coming back immediately.

Now the version people actually get burned by.

Turnitin's guidance for instructors on understanding the similarity score lists scoring scenarios, and the second one is this:

"A student may have used Turnitin to submit drafts of the same paper, meaning their final draft has resulted in a score of 100%."

A hundred per cent. Against themselves.

The same page gives the remedy, and it is worth knowing precisely who holds it: "As the instructor is likely aware that their student has submitted multiple times, they can rectify this issue by excluding the student's previous submissions from the Similarity Report." That is an instructor-side control. You cannot apply it, which is why the fix for this is a conversation and not a rewrite.

Whether a submission goes into the repository is decided above you, in two layers.

Turnitin's account settings guide describes what an administrator can allow. With standard repository options enabled, instructors "will be able to set the assignment option to either store student papers within the standard paper repository or not store the papers in any repository". With expanded options, the choice becomes the standard repository or the institutional one. And an administrator can instead select "Submit all papers to the standard repository", in which case every paper submitted to the account is stored.

So three different assignments in the same degree can behave three different ways, and none of the settings are visible to you from the submission screen.

That has a practical consequence for anyone using a draft-checking assignment: it is worth asking whether that assignment stores papers before you use it as a rehearsal for the real one.

One more thing from the student guidance: once you have made a submission you cannot delete it yourself. Resubmitting can overwrite a wrong file, but removing a submission goes through your instructor and your institution's policy.

Everything above is about the Similarity Report. It has no bearing on your AI percentage, and the distinction matters more here than almost anywhere else, because the two failures look identical in a screenshot.

Turnitin states that the similarity score and the AI writing detection percentage are completely independent and do not influence each other, and that AI writing highlights are not visible in the Similarity Report at all. Its FAQ adds that there is no separate repository for AI writing detection, and that customers keep the choice of whether student papers go into the repository or not. What is retained, it says, is the result: the AI percentage and the segments identified as likely AI-written are kept as part of the similarity report.

Two things follow. Your earlier draft cannot raise your AI percentage by sitting in a repository, because that is not what the repository feeds. And a 100% self-match is a similarity event that says nothing whatsoever about AI. AI Writing Report vs Similarity Report covers why all four combinations of high and low are possible.

1. Find out whether you are resubmitting to the same assignment or a new one. Everything else follows from this. The same assignment overwrites; a new one is a fresh submission that can match the old one.
2. Check whether the work has been graded before overwriting it, since the grade goes with the file.
3. Count the attempts, and remember your instructor shares them. Three immediate reports in 24 hours, then the queue.
4. If the report has not appeared, wait rather than resubmit again. The delay is what stops your own draft from matching you.
5. If you already have a self-match, take it to the instructor, because excluding previous submissions is a control on their side of the report, not yours.
6. Do not read a similarity self-match as an AI problem. They are separate reports measuring different things.

The reason this question comes up at all is that people are usually about to change the file, not just resubmit it.

If the AI percentage is what you are fixing, then the size of the change decides how much of the resubmission you have to reread before you spend one of your three attempts. HumanPen is built around keeping that number down: the report you import defines what gets rewritten, the paragraphs it did not flag come back as you wrote them, and the charge follows the words that changed rather than the file you uploaded. Eligible results can continue lowering AI for free.

That is a statement about scope and cost, not about what your next report will say. Here it buys one specific thing: a shorter list of paragraphs to check, on a submission you only get to make three times in a day.

Will my first draft show up as plagiarism when I submit the final version? Not if both go to the same assignment. Turnitin says a resubmission overwrites the previous submission and that they will not match against each other. If the drafts went to a different assignment that stored them, Turnitin's own scoring examples describe drafts of the same paper producing a 100% score.

How many times can I resubmit? Where your instructor has enabled resubmissions and the due date has not passed, up to three times in 24 hours with an immediate report, counted from your first submission that day. After that a new report waits for the 24 hours to pass. The attempts are shared with your instructor.

My similarity report is stuck after resubmitting. Is something broken? Probably not. Turnitin says overwritten or resubmitted files may not generate a new report for a full 24 hours, and that the delay exists so a resubmission does not match the previous draft.

Can I delete a submission myself? No. Turnitin's student guidance says once a submission is made you cannot delete it from the assignment; resubmitting can overwrite the wrong file, and removal goes through your instructor and institutional policy.