Online Assignment Submission Portal with Plagiarism Check and Deadline Tracking

An online assignment submission portal with plagiarism check and deadline tracking is a web application where faculty publish assignments with fixed deadlines, students upload their work before the cut-off, and every submission is automatically compared against other submissions, web sources and past work for copied text. In most colleges this workflow still runs on email and messaging apps, so faculty chase late files in scattered inboxes, deadlines are announced but never enforced by the system, and copied work is spotted only when a teacher happens to recognise it. This portal replaces that scatter with one timestamped record per submission: upload closes at the deadline, a similarity report is generated on upload, reminders go out before the cut-off, and late work is accepted only inside a published penalty window. In the demo build, the similarity scan flags 7 of the 48 seeded submissions above the 25% threshold, showing how the check surfaces copied work instead of leaving it to chance.

A faculty member creates an assignment with a title, instructions, allowed file formats and a deadline, and the portal publishes it to the class dashboard with a countdown. Students upload their file before the cut-off; the portal stores it with a server timestamp, extracts the text, and runs the similarity check against the three comparison sources, saving a report alongside the submission. As the deadline approaches, the reminder job notifies students who have not submitted, and after the deadline the portal either locks uploads or accepts them with the configured penalty. Faculty then open each submission, read the similarity report, enter marks and feedback, and publish the grades, after which students see their result and the annotated report in their own dashboard. Every step leaves a timestamped record, so a dispute about a late or missing submission is settled from the portal log rather than from memory.

1. Faculty create an assignment with instructions, file-format rules and a deadline; it appears on the student dashboard with a live countdown.
2. Students upload PDF, DOCX or ZIP files; the portal records the server timestamp and stores the file against the assignment and the student.
3. The uploaded file is converted to plain text and compared against class submissions, web sources and the department archive using TF-IDF and cosine similarity.
4. A similarity report is generated with an overall percentage, matched passages and the source of each match; submissions above the 25% threshold (configurable) are flagged for review.
5. The reminder job sends notifications 48 hours and 24 hours before each deadline to students who have not yet submitted.
6. After the deadline, the portal applies the configured late penalty automatically and locks uploads once the final cut-off passes.
7. Faculty grade each submission in the portal, add written feedback, and publish the results; students see their marks and the similarity report in their dashboard.

Assignment portal vs email submission

Tech stack:

• HTML5 · CSS3 · JavaScript
• Node.js · Express
• MySQL
• PDF text extraction (pdf-parse)
• Similarity matching (TF-IDF · cosine)
• JWT authentication
• Nodemailer reminders
• Git

The portal is built around four capabilities that carry the whole assignment cycle: an automatic similarity check that runs on every upload, a deadline tracker that counts down to each cut-off and sends reminders before it, a role-based workflow that keeps student, faculty and admin views separate, and online grading with written feedback. Around those four, the portal adds late-submission penalties that the faculty member configures per assignment, a full submission history so no file is ever lost or disputed, and a plagiarism report that shows the matched passages and their sources instead of a single unexplained percentage. Together these make the portal a complete replacement for email-based submission rather than a file-upload form with a calendar attached. The demo class behind the screenshots shows all of this working together: six assignments, forty-eight submissions and seven flagged reports, so a reviewer can see the workflow end to end rather than reading about it.

• [Automatic similarity check on upload] Every uploaded file is converted to text and compared against class submissions, web sources and the department archive, producing a similarity percentage and a report with the matched passages highlighted.
• [Deadline tracker with reminders] Each assignment shows a live countdown, and the portal sends reminders 48 hours and 24 hours before the deadline, so students cannot claim they did not know the cut-off.
• [Role-based dashboards] Students see their own assignments, deadlines and grades; faculty see the whole class, submission progress and flagged reports; an admin manages users, courses and the similarity threshold.
• [Late-submission penalty rules] Faculty set the penalty per assignment — 10% of marks per day for up to 3 days in the default configuration — and the portal applies it automatically and locks uploads after the final cut-off.
• [Online grading and feedback] Faculty grade inside the portal, attach marks per submission and write feedback that the student sees immediately, replacing mark sheets passed around on paper.
• [Plagiarism report with sources] Flagged submissions open a report showing the overall similarity score, each matched passage, the source it matches and the share of matched text from that source.
• [Submission history and audit trail] Every upload, resubmission, reminder and grade is timestamped and stored, so a dispute about whether work was submitted on time is settled from the record, not from memory.

• Complete portal source code (frontend, backend and database schema)
• Automatic similarity checker with matched-passage reports
• Deadline tracker with countdowns, reminders and late-penalty rules
• Role-based dashboards for student, faculty and admin
• Seeded demo class with 6 assignments and 48 submissions for the viva demonstration
• Project report PDF (background, design, database schema, similarity method, testing)
• PPT presentation for final review
• Viva Q&A preparation document (authentication, similarity matching, deadline enforcement, database design)
• Setup guidance for installation and first-run configuration
• Typical build timeline: approximately 3–4 weeks from requirements confirmation to delivery (expected)
• To get this project, message Projectech on WhatsApp with the project name, your branch and your deadline — you receive a written quotation stating the exact scope, the price and the delivery date before any payment.