Skip to content
PlagiatScanner.de
Examination procedures · problem · PRV-02

Plagiarism allegation: prepare to review the case file

In brief: Read the notice, response deadline and file-review instructions in full. Bring the exact submitted work and list the records, passages, comparison sources, similarity reports, procedural steps and responsibilities you need to understand. During review, separate what the file states from what you observe and what remains a question. Make copies or notes only where permitted, and do not accept an untested factual premise merely to obtain access.

Document-and-question checklistReviewed 11 September 2026

Establish the route and scope before the appointment

“Reviewing the file” is not a universal process. It may mean supervised access, a digital bundle, copies of selected documents or another arrangement under the institution’s rules. Read the specific notice rather than relying on a generic online description. Identify the location, booking route, deadline, contact, permitted note-taking and any process for requesting copies or accessible formats.

Assemble your submitted file, assignment brief, declaration, applicable academic regulations and earlier correspondence. They provide comparison material but may not themselves form part of the official case file. Keep originals unchanged. If you are considering a representative or support person, check the controlling provision early rather than assuming that attendance is either allowed or prohibited.

Authority asset: document-and-question checklist

Worksheet for a structured case-file review
AreaLook forQuestion to answerRecord
Opening noticeDate, sender, allegation, deadlineWhich conduct and passage are identified?Exact wording and page
Submitted workFile, appendices, receiptIs this the precise version under review?Filename and identifier
Contested passagesPage, paragraph, table or footnoteCan every concern be located?Assign a passage ID
Comparison materialSources and juxtaposed extractsWhich edition and surrounding context were used?Source and scope
Technical reportSystem, date, settings, marksWhat is machine output and what is evaluation?Keep terms separate
Procedural recordNotes, referrals, decisionsWhich steps are documented?Add to chronology
Service and deadlinesDate, channel, appeal informationWhat response is expected, and when?Preserve original text

Capture each disputed passage as a separate unit

Assign identifiers such as P-01. Record its page and paragraph in the submitted version, the wording under scrutiny, the comparison material and the stated reasoning. Include the immediate context on both sides. Otherwise a similarity mark may be detached from quotation marks, a footnote, the bibliography or necessary disciplinary language.

Do not draft your whole defence in the observation field. Use three layers: “The file records …”; “The submitted work shows …”; and only then “My provisional interpretation is …”. Link the third layer to evidence still required. This discipline prevents a later note from making your assumption look like something that appeared in the official file.

If only a source extract is available, record that limitation. Ask which edition, archived page or database record was used. Do not declare a comparison source wrong before examining it. Translation, code, tables and figures need their own attribution conventions and surrounding academic context.

Separate a similarity report from the decision made about it

A report may display percentages, colours and source candidates. Those elements begin as system outputs. Look for the documented human assessment: Which matches were accepted, excluded or reclassified? Were bibliography entries, properly marked quotations or unavoidable standard wording considered? Which version of the report is in the file?

Record configuration only when it is actually shown. Do not invent an exclusion threshold or database scope. A document-wide percentage does not explain which text is alleged to be improper. Equally, a low percentage cannot disprove a well-defined passage-level concern. At this stage, the goal is to identify the actual basis of the allegation before answering it.

Create notes whose provenance remains obvious

Use file page numbers or unambiguous document names. Mark verbatim transcription as quotation and distinguish your summaries. If photographs or copies are restricted, comply and note what was available for inspection. Avoid transferring third-party personal data or confidential documents into an unapproved cloud notebook.

End each document review with three prompts: What is established by the file? Which evidence is missing for an assessment? Which procedural question requires an answer from the institution? Review legibility promptly after the appointment, but do not silently polish the original wording. Date and label any later addition.

Turn the review into a controlled working file

Build a chronology and passage register. Connect each preliminary answer to genuine records from your workflow. Mark unresolved points as open instead of filling them with a favourable assumption. Recheck the deadline against the original notice and preserve evidence of when and how any response is submitted.

  • The exact submitted version is identified.
  • Every disputed passage can be located.
  • The comparison material and edition are traceable.
  • Automated output and human assessment remain distinct.
  • Procedural steps, responsibility and deadlines are recorded.
  • File content, observation and interpretation are visibly separate.
  • Protected material stays within an authorised transfer route.

The examination procedures hub gives broader process orientation. Next, the guide to preparing for a plagiarism hearing turns the file into a passage-level response. This page contains one foundation link, to academic writing and evidence; it does not replace the governing rules.

Official foundations

  1. German Federal Ministry of Justice: section 29, Administrative Procedure Act – a German federal reference on access by participants, without assuming that it applies to a specific case.
  2. German Research Foundation: Guidelines for Safeguarding Good Research Practice – fair processes and traceable documentation.
  3. ALLEA: The European Code of Conduct for Research Integrity – integrity, reliability and fair investigative practice.

Sources reviewed 4 September 2026. Local law and institutional assessment rules may differ.