New: Original View reports — findings directly on the original document See what's new
AI writing detection

AI detection honest enough to act on

iOriginally shows sentence-level probabilities instead of one opaque number, keeps the AI signal strictly separate from similarity, and prints your institution's policy note on every AI screen and PDF. A signal for human judgment — never proof of misconduct.

Sentence-level probabilitiesKept separate from similarityLimits printed on every report
Segment-level analysis

Sentence-level probabilities, not one opaque number

A single document-wide percentage invites over-reaction and hides the evidence. iOriginally breaks the analysis down to sentences and segments, so a reviewer can see exactly which passages drive the signal — and which contribute nothing at all.

  • Per-segment probabilities. Every passage carries its own estimate, so one machine-flavoured paragraph never paints the whole document.
  • The same detail on screen and PDF. The report your committee files shows the identical segment breakdown the reviewer saw in the browser.
  • Nothing hidden behind the headline. The document-level estimate always opens into the segments that produced it — you can interrogate every step.
How AI-writing detection works
AI writing analysis · segment viewDocument estimate 24%

The proliferation of digital technologies has fundamentally transformed the contemporary educational landscape, necessitating a comprehensive re-evaluation of pedagogical frameworks.

91%

Honestly, the survey results surprised us — half the cohort had never opened the module handbook, which changed how we read everything that followed.

7%

These findings are consistent with earlier work on assessment design, although the sample size limits how far the comparison can be pushed.

43%
Institution policy note: AI indicators support human judgment — they are not proof of misconduct.
Senior professor reviewing work on a laptop in a university lecture theatre
Separate by design

The AI number never touches the similarity score

Similarity is a matching result against identifiable sources. The AI signal is a statistical estimate. Blending them would dress a probability up as a fact — so in iOriginally they are kept strictly apart, from the first screen to the filed PDF.

  • Separate score, separate report, separate PDF. An AI estimate can never inflate a similarity result, and a committee always knows which signal it is reading.
  • Your policy note on every AI screen and PDF. Reviewers see your institution's rules of use at the exact moment of judgment — not in a handbook they read once.
  • Policy bands your institution configures. What counts as "worth a closer look" is your call, set per institution — not a vendor default.
See how similarity detection works
Built for review

What a responsible review looks like

The report is designed around how a fair process actually works — in three deliberate steps, with a human making every call.

1

Read the segments, not the headline

Open the segment view before reacting to the document-level estimate. High-probability passages clustered in one section tell a very different story from a uniform haze across the whole text.

2

Add the context no detector has

Drafts, notes, version history, in-class writing, and the student's known voice are evidence a model cannot see. The report is one input to that picture — never a substitute for it.

3

Open a conversation, not a case

The policy note printed on the report points everyone to your institution's process. An elevated signal earns a supportive conversation about the writing — it never earns a verdict by itself.

Limits, stated plainly

What this signal cannot tell you

Every AI detector on the market shares these limits. We would rather print them on the product than bury them in fine print — a signal your staff over-trusts is worse than no signal at all.

It is a probabilistic signal

The score is a statistical estimate that text resembles machine generation. It does not witness how the work was produced, and it cannot tell intent from assistance.

False positives exist

Formulaic, heavily templated, or carefully polished human writing can score high with no AI involved. Expect false positives and design your review process to absorb them.

Extra caution for non-native writers

Published research has shown AI detectors flag writing by non-native English speakers at higher rates. Elevated scores from these writers deserve particular care and a second reviewer.

Never sole evidence

An AI probability alone should never decide a misconduct case. It can start a conversation and prompt a closer look — the finding must rest on process, context, and human judgment.

Short passages carry less signal

A few sentences give unstable estimates in either direction. The segment view exists precisely so short, noisy fragments are read as fragments — not as findings.

Models keep moving

New writing models change what machine text looks like. We recalibrate continuously, but no vendor can honestly promise a final answer to a moving target — including us.

Printed on every AI screenPrinted on every AI PDFCovered in reviewer training
FAQ

Questions about AI detection

Can iOriginally prove a student used AI?
No — and no detector honestly can. The analysis produces a probability that text resembles machine generation, not a record of how it was written. That is why the signal is framed as an aid to human judgment on every screen, and why your institution's policy note travels with every report.
Why show sentence-level probabilities instead of a single score?
A single document-wide percentage invites over-reaction and hides the evidence. Segment-level detail shows which passages drive the signal and which contribute nothing, so a reviewer can weigh the pattern against everything else they know about the student's work.
Is the AI estimate ever mixed into the similarity score?
Never. Similarity is a matching result against identifiable sources; the AI signal is a statistical estimate. Blending them would dress a probability up as a fact, so they live in separate reports with separate PDFs, and one can never inflate the other.
How should our policy handle flagged work from non-native English writers?
With documented extra caution: research has shown detectors flag non-native English writing at higher rates, so an elevated score from these writers warrants a second reviewer and weight on writing-process evidence such as drafts and version history. We print this caution in the product, and our policy guide for the AI era walks through the wording institutions use.

See an honest AI report on your own documents

Book a demo, or start a free 14-day evaluation with 50 checks — and judge the segment view on writing you already know.