You've got a stack of student writing, a detector your course or institution now runs on submissions, and a result sitting in front of you that you have to do something with. That's a real position to be in — you're responsible for academic integrity in your course, and you're also responsible for not turning a statistical signal into an accusation a student can't push back on. The honest answer to "how do I use this fairly?" isn't a single rule. It's a process: read the evidence, not just the score, and treat a result as the start of a conversation, not the end of one.
The pressure on your side is real. Class sizes are large, AI-assisted writing is genuinely common, and an institution that hands you a detector without also handing you a process leaves you to work out what's fair on your own. None of that is a reason to skip a careful process — it's the reason one matters.
A bare percentage next to a student's name can feel like a verdict before anyone has said a word to them. That's the actual problem worth naming: not that detection is unreliable, but that a number with no evidence attached can't carry the weight of an accusation. Treating it as proof is unfair to the student on the receiving end, and it's a weak position for you too — a decision built on a score alone is hard to defend if a student, a department, or a committee asks you to explain it.
Be confident about what detection can do, because it does something real. AI writing leaves measurable statistical patterns — sentence rhythm that stays unusually uniform across a passage, word choices that lean toward the statistically predictable option, paragraph structure that repeats the same shape section after section. A detector built to surface those patterns, sentence by sentence, with reason keywords naming which one triggered a flag, is showing you something concrete about the text in front of you.
Be just as clear about what it doesn't do. A score is a probability estimate, not proof — evidence for you to weigh, not a finding that settles the question on its own. That's not a hedge specific to this article; it's the same standard ScribeLens holds its own results to, and it's why a report is built around sentence-level evidence instead of a bare number in the first place.
It's also worth knowing where pattern-based detection tends to strain: formal, disciplined academic writing — consistent structure, measured transitions, even sentence rhythm — shares real surface features with AI-generated text, because that structure is exactly the kind of regularity detectors are trained to notice. That's a reason to read the sentence-level evidence on a flagged paper rather than trust the register alone, not a reason to distrust detection generally.
None of this requires a formal policy overhaul. It's a short sequence you can apply consistently, every time a result crosses your desk:
The difference between a fair process and an unfair one usually isn't the tool — it's how the result gets used once you have it.
This is exactly the gap ScribeLens is built to close: not a bare score, but a report you can actually use in a fair process. Every sentence in a document is classified individually — human-like, mixed, or AI-like — against a graded overall verdict, so you can see immediately whether a signal is concentrated in a few sentences or spread across the whole piece. Sentences that get flagged carry reason keywords naming the specific pattern behind them, so a conversation with a student can start from “these three sentences show this pattern — walk me through how you wrote them” instead of a number with nothing underneath it.
Reference lists, citations, and other back-matter are excluded from scoring automatically, which matters for research-heavy assignments where a bibliography would otherwise inflate a result for reasons that have nothing to do with how the student actually wrote the paper.
If a case needs to go further — a committee, a department chair, a written record — a report exports as a searchable PDF or DOCX with a built-in guide to reading it, so someone reviewing the case can understand the evidence without needing an account or your explanation alongside it. Free accounts include a limited number of these exports each month; unlimited PDF and DOCX exports come with a Pro account.
If your department or institution wants this applied consistently across a whole course load rather than one instructor at a time, that's a separate conversation from an individual account — institutional access is arranged directly, with a contracted usage allowance rather than a self-serve plan. The institutions page covers what's available today.
If you take one thing from this:
No. A detector score is probabilistic evidence, not proof, and treating it as a standalone finding is not a fair or defensible process. Read the sentence-level evidence, weigh the student's drafts and version history, and talk with the student directly before any decision — the score is one input, not the decision itself.
No. It's evidence of statistical patterns commonly associated with AI-generated writing, not confirmation of how a specific piece was actually written. Treat it as a reason to look closer at the sentence-level evidence and talk with the student, not as a finding that settles the question.
Go back to the sentence-level evidence together rather than defending the score. Ask the student to walk you through the flagged sentences specifically, and weigh whatever drafts, notes, or version history they can offer. A fair review treats the student's account as part of the evidence, not as something the score overrides.
Formal, disciplined prose can share surface features with AI-generated text — consistent structure, measured transitions, even sentence rhythm — which is a known strain point for pattern-based detection generally. ScribeLens weighs sentence-level evidence rather than convicting a paper on register alone, but it's still worth reading the evidence on any formal submission carefully rather than trusting the headline score by itself.
That's exactly the kind of context a bare score can't capture and a conversation can. Ask about it directly, and weigh drafts or notes from earlier in the process if the student can provide them. A style shift is something to discuss, not something a detector result can confirm or rule out on its own.
No. A free account covers scans up to 40,000 words from a 35,000-word monthly pool, with a limited number of PDF or DOCX exports included each month — enough to review individual submissions with full sentence-level evidence. If you're reviewing a full course load regularly and need more scanning volume or unlimited exports, that's what a paid account is for; a department-wide or institutional setup is a separate, contracted arrangement.
See sentence-level evidence and reason keywords behind every result, so a flagged draft starts a fair conversation instead of an accusation.