The paper was finished until the AI score arrived.
I had done the work and could explain every section. The citations were checked. The weak parts had already been revised. Then the number turned a finished paper into work I was expected to do again.
The new task had nothing to do with finding a better source or fixing a bad argument. It was a loop built around the report. Locate a highlighted passage. Change words that already say what I mean. Make sure the edit did not disturb a quotation or citation. Hand the revision back for another check.
There is no credit for this task. There is no marking rubric either. I am trying to satisfy a classifier without being told what finish line would count.
That extra work is a detector time tax. It is paid in the part of the deadline that could have gone toward reading, checking evidence, asking for feedback, or getting some sleep. The paper does not become more thoughtful because its sentences have been moved around for a number.
The score also collapses questions that should stay separate. Authorship is about who did the intellectual work. Course policy decides which kinds of assistance were allowed. The detector supplies a signal about the text. One answer cannot stand in for the other two.
A student can write the paper and still violate a rule about editing tools. A student can also follow the tool policy and receive an AI flag. Treating the score as a verdict skips both of those facts.
Turnitin's own report guidance says its model may misidentify human-written, AI-generated, and AI-paraphrased text. It says adverse action needs further scrutiny, institutional policy, and human judgment. The company's FAQ says instructors should not use the percentage as a definitive grading measure.
That is the vendor drawing a boundary around its own output. The report can start a closer look. It cannot reconstruct who chose the argument, found the sources, or made the decisions inside the paper.
Still, telling a student to ignore the number is easy advice from the side that does not carry the grade. If an instructor or submission process wants the score lowered, a refusal can be principled and expensive at the same time. Students comply because the risk belongs to them.
An authorship concern should lead to a human conversation. Ask me to explain the thesis. Ask why I used a source or how a section changed between drafts. Apply the course policy to evidence from the writing process.
If the paper has already been submitted and an investigation has begun, preserve the original file. Rewriting an existing submission would change the evidence when the dispute is about how that evidence was produced.
Before final submission, or during a revision the student has been explicitly allowed to make, the situation is different. The work still has to be mine. The course or assignment rules must expressly permit this kind of AI-assisted or third-party rewriting at that stage. Any disclosure, approval, and submission requirements still apply.
To save my valuable time, I used HumanPen for this part.
For an English DOCX, PPTX, or TXT file, the tool can use a Turnitin or iThenticate report to locate the flagged passages inside the document. That removes the manual search and the trip through a paste box for every passage. Eligible results can continue lowering AI for free.
It cannot decide whether the use was allowed. It cannot prove authorship, cancel a disclosure duty, or promise a score. Every changed paragraph still needs to be read. The meaning and citations still need to be checked. I keep the original and remain responsible for the file I submit.
That division of labor makes sense to me. I do the thinking. A tool can take some of the mechanical work out of a loop I did not ask for. The final review remains mine.
The score should be a reason for a person to examine the evidence, not a hidden style guide that students must reverse-engineer. The first approach asks whether the work is honest. The second teaches students that pleasing a classifier matters more than writing well.
I wrote the paper. I should not also have to write a second version for the machine.
Top comments (0)