The LMS badge and the PDF you downloaded disagree—how to read coverage before you rewrite
The LMS badge and the PDF you downloaded disagree—how to read coverage before you rewrite
Across English-medium programmes in India and Southeast Asia, a familiar mismatch shows up after submission: the Moodle, Canvas, or Blackboard card shows one AI writing percentage, while the downloaded PDF / full report shows a different highlight map, missing pages, or footnotes the badge never displayed. WhatsApp crops of the portal travel faster than the official export.
This post is about portal-versus-report coverage literacy. It is not about “which file on your laptop got uploaded” (a different problem). It does not promise any score, and it is not a detection-evasion guide.
Two surfaces, two jobs
Surface | What it is good for | What it often hides |
|---|---|---|
LMS / portal badge or inline card | Fast status for staff and students | Full highlight map, unscored regions, footnotes, page-level coverage |
Downloaded PDF / official export | Artefact you can bring to office hours | Nothing—if you actually open every page |
Arguing from the badge alone is like arguing from a movie poster. The PDF is the cut you should discuss.
Why the numbers can look different without anyone “changing the score”
Common, boring causes:
The portal refreshed a summary while the PDF export captured a later (or earlier) processing state.
The card aggregates only qualifying continuous prose; the PDF shows which blocks were excluded (tables, captions, appendices, reference lists).
A screenshot cropped away the tool name, report ID, attempt number, or coverage note.
Similarity and AI writing widgets sit side by side on the portal; a crop merges them into one rumour.
None of these require a conspiracy. All of them require you to open the full export before rewriting.
Five checks that compare portal to PDF
Write down the badge number and the PDF header number (if both exist). Note report ID / time on each.
Flip every PDF page: which sections have highlights, gray bands, or blank unscored zones?
Compare word count / page count of the scored attempt file with what the PDF claims to cover.
Look for a coverage or footnote sentence the portal card never showed.
Only then decide whether the conversation is about wording—or about which artefact is authoritative for your module.
Similarity still is not AI writing
A low similarity score on the portal does not cancel an AI writing indicator in the PDF. An AI writing indicator does not prove plagiarism. Coverage mismatch adds noise to both if classmates only share crops.
If your school already asked for revision
Ask in writing which artefact counts: the live portal card or the official export. Scope edits to flagged continuous prose in the file that will be re-checked. Freeze citations, tables, and verified facts unless they are wrong.
For a document-level workflow—import an AI writing report, change only flagged passages, keep layout—see HumanPen. It still does not promise what the next portal card will show.
Takeaways
Treat the downloaded report as the discussion copy; treat the badge as a headline.
Coverage footnotes and unscored regions often explain “why the numbers feel inconsistent.”
No honest tool should be described as a “guaranteed pass.”
— Charles Li · HumanPen · https://humanpen.net
Join the Conversation
Share Your Thoughts
Related Articles
*% Versus 21%: Do Not Over-Read the First Visible AI Number
The AI writing indicator does not always show a tidy percentage. A display band — not a gavel — explains *% and ~21%.
Authorship Flag vs AI Detection: Two Systems People Mix Up in Reports
Authorship and AI detection answer different questions with different methods. How to read each flag without mixing them up.
The AI Badge Did Not “Miss” Your Rewrite—It May Be Scoring an Older Upload
An AI writing percentage scores a submitted snapshot. Version mismatch — not a stubborn detector — explains most “I fixed it and the score stayed” nights.