3 October 2026 · 7 min read
It is one of the most common ways a Nepali student first sees a serious similarity report: the top matched source is not a website or a journal article but a classmate. Sometimes the two of you genuinely copied. Far more often you studied together, shared notes, used the same senior's file as a model, or split a group project and then each submitted the shared parts as your own. The report cannot tell those situations apart, and neither, at first glance, can your teacher.
This post explains how classmates end up matching each other, where collaboration stops being acceptable, and what to do if it has already happened.
A similarity check compares your file against web pages and published material, and also against previously submitted student papers. Depending on how your institution's account is set up, submissions can be stored in a repository and matched against later submissions — from your own class this semester, from other sections, or from batches years ago.
That has two consequences students rarely think about. First, whoever submits second shows the first person as a source, regardless of who actually wrote the text. Second, a senior's report you borrowed as a model may already be sitting in the repository, so a paragraph you thought you had adapted quietly matches a file submitted three years ago.
The report shows the match; it does not show intent. A teacher looking at two submissions that share whole paragraphs will usually ask both students to explain, and the burden is on you to show how your text came to be.
Departments in Nepal generally encourage students to study together. What they object to is collusion: two or more people producing work that is submitted as individual when it was not. The line is about the written output, not the conversation.
The last point catches honest students. If you send your completed assignment to a friend and they copy from it, the report shows both of you, and many institutions treat the student who supplied the work as part of the problem. Helping a friend means explaining, not forwarding the file.
Group work in BBA, BBS, BIT and engineering programmes adds a complication: some of the work is legitimately shared, and some is assessed individually. Read the brief for which is which, because the answer differs between courses.
Typically the group shares the topic, the data, the presentation and sometimes a joint report. Where the brief asks for an individual reflection, an individual chapter or an individual write-up of the group project, that part has to be written separately by each member. Copying the group's methodology paragraph into five individual reports produces five near-identical submissions, and the report will show it.
If you genuinely co-wrote a section, say so. A short note in the report, or a contribution table, saying who drafted which part is normal practice and protects everyone. Where the department expects a single joint document, submit one — not five copies with names changed.
Shared notes are not the problem; shared sentences are. Notes become a similarity issue when two students lift the same phrasing from them into their final answers. A few habits prevent it:
Two students who studied from the same notes but wrote independently will share ideas and terminology. That reads as two people who studied together. Shared sentence-length runs read as one document submitted twice.
Do not panic, and do not start rewriting the submitted file — the version that was submitted is the one under discussion. Instead, gather what shows how your work developed: your drafts and version history, your own handwritten or typed notes, messages showing what you discussed and when, and the sources you used.
Then look at what actually matched. If it is the shared data description, a standard definition, or a methodology both of you correctly cited from the same source, explain that plainly. If it is whole paragraphs of argument, be honest about how that happened; departments respond far better to a clear account than to two students blaming each other.
If the work has not been submitted yet and you are worried a friend's file overlaps with yours, a pre-submission check run without storing the document will show you where the overlap is while there is still time to rewrite your part in your own words.
Rules on collaboration are set course by course, and they are not always written down. One teacher may welcome students comparing answers to practice questions; another treats any shared wording as misconduct. If the brief is unclear about what may be done together, ask the teacher directly before you start, and ideally get the answer in a message or on the class notice board. A student who can show they asked, and followed the answer, is in a very different position from one who guessed.
The same applies to reusing material between courses. Submitting the same essay, or large parts of it, for two different modules is usually treated as self-plagiarism even though you wrote it, and a repository will match the second submission to the first. If you want to build on earlier work, ask permission and cite your own previous assignment.
Related reading:
Not sure whether your draft overlaps with a classmate's or a senior's? Send it to us on WhatsApp before you submit. We will run a plagiarism report and an AI report, tell you exactly which passages match and why, and what needs rewriting in your own words.
Tell us what you need checked and when it is due. Your document is checked without being stored in any student-paper repository, so the check never counts against your real submission. The reports come back with what each match means, not just a percentage.