Hook: The Everyday Headache Everyone on r/teaching Talks About
Scrolling through r/teaching this week, I kept seeing the same thread title: “My students keep turning in the wrong file type and I can’t keep track of who did what.” A handful of replies echoed the same frustration—students miss the exact wording of the submission instructions, upload PDFs when a TXT was required, or simply forget to include the private access code the teacher posted in a separate announcement. On X, educators were posting screenshots of inboxes flooded with “I submitted the wrong version” messages, each one adding another layer of manual sorting for the teacher.
What makes the problem stick is that the instructions are often scattered across a syllabus, a Google Classroom post, and a quick reminder tweet. The result is a constant back‑and‑forth, wasted class time, and a grading load that feels like it’s growing faster than the teacher’s coffee consumption. The community consensus is clear: we need a single, reliable place where the submission rules are locked in before the student even clicks ‘Submit.’
The Problem Deep Dive: Why Mixed Instructions Break the Workflow
When instructions live in multiple places, students interpret them differently. One Reddit user described how half the class uploaded a Word doc while the other half submitted a plain‑text file, forcing the teacher to open each file, rename it, and manually verify that the correct version was attached. The same post noted that partial‑credit policies become impossible to enforce because the teacher can’t tell which version a student intended to submit.
Beyond the file‑type confusion, the lack of a unified identifier—like a student ID or private code—means teachers spend precious minutes cross‑checking rosters. A thread on X highlighted a teacher who spent an entire afternoon reconciling a spreadsheet of IDs with the filenames students chose. The result is not just extra admin work; it also creates anxiety for students who fear that a simple typo will erase their effort, and for teachers who worry about fairness when they can’t verify who actually turned in what.
How Quesly Solves It: A Streamlined, Locked‑Down Submission Process
Quesly starts by letting teachers upload source material—plain‑text files, text‑based PDFs, or pasted notes. The platform extracts the readable text, then generates a set of questions based on that content. Teachers review the generated questions, the MCQ answer key, and the marking criteria before publishing. Because the source must contain text, an empty upload is blocked, ensuring the assignment is always grounded in real material.
When the assignment goes live, teachers issue a unique student ID and a private access code that each learner must enter before they can begin. The system locks the work once a student hits ‘Submit,’ so no further edits are possible. MCQs are graded automatically against the fixed answer key, while written answers are evaluated after submission by Quesly’s Jev engine, which suggests marks and provides reasons for each suggestion. Teachers then review those suggestions, adjust any marks as they see fit, and finally release the results. Students only see the final grades, not the AI’s intermediate suggestions, preserving the teacher’s judgment.
Real Example (Synthetic): From Reddit‑Style Post to Quesly Workflow
Imagine a Reddit post titled “Help! My class keeps submitting the wrong file type for the unit test.” The comment thread shows a teacher posting the original instructions: “Upload a .txt file named ‘UnitTest_YourID.txt’ and include the code ABC123 at the top.” In the Quesly workflow, the teacher would first upload the unit‑test notes (a PDF of lecture slides). Quesly generates ten short‑answer and five MCQ items, and the teacher confirms the MCQ key (e.g., A, C, B, D, A). The teacher then creates a batch of IDs (U001‑U030) and shares the code ABC123 in a single announcement.
Students log in, type their ID, enter the code, and answer the questions directly in the Quesly interface. Once they click ‘Submit,’ the file is locked, and the system records the exact ID‑code pair. Jev runs on the short‑answer responses, suggests marks with brief rationales (e.g., “Answer captures main concept but misses supporting detail”), and the teacher reviews each suggestion, makes any necessary adjustments, and releases the final grades. The entire process eliminates the scattered‑instruction chaos that sparked the original Reddit thread.
Teacher Judgment Required and Practical Takeaway
Even with Quesly handling file type enforcement and initial marking suggestions, the teacher’s expertise remains essential. Teachers must still verify that the generated questions align with learning objectives, confirm that the MCQ answer key matches the intended correct responses, and adjust any Jev‑suggested marks that don’t reflect nuanced rubric criteria. The final step—releasing results—requires the teacher to ensure that the released grades accurately reflect the reviewed marks.
For teachers looking to implement this solution today, start by consolidating all submission instructions into a single Quesly assignment page. Use the built‑in ID and private code fields to replace scattered emails and announcements. After publishing, allocate a short block of time to review the AI‑generated questions and answer keys before students begin. Finally, treat Jev’s suggestions as a draft, not a final verdict; a quick scan of the rationales will usually reveal any mis‑interpretations before you hit ‘Release.’ By centralizing instructions and locking submissions, you cut down on the back‑and‑forth that dominates many teacher inboxes, giving you more time for the teaching that really matters.
