Hook: The Real‑World Pain Everyone Is Talking About
Scrolling through r/teaching this week, I kept seeing the same sigh‑filled comment: “I get AI‑generated feedback, but I never know how to tweak it, so I just ignore it and grade everything by hand.” On X, a thread titled #TeacherGradingStruggles had dozens of replies about AI tools that spit out suggested scores, only to be tossed aside because teachers feel they lack a clear way to adjust those numbers without breaking the workflow. The frustration is palpable—educators want the time‑saving promise of AI, but the lack of a transparent edit path makes the suggestions feel like junk mail.
That sentiment echoes across campuses: teachers spend hours crafting rubrics, then stare at a spreadsheet of AI‑suggested marks that they can’t easily reconcile with their own judgment. The result is a double‑work loop—first ignoring the AI, then re‑entering grades manually. It’s a classic case of a tool that promises efficiency but ends up adding mental load.
The Problem Deep Dive
What makes the AI suggestions feel unusable? First, the suggestions appear after students submit written answers, but the interface offers no place to annotate why a teacher disagrees. In many Reddit posts, teachers describe “partial credit confusion” where the AI awards a full point for a keyword match, while the teacher sees a nuanced misunderstanding that deserves half credit. Without a way to record that reasoning, the AI’s output is effectively invisible.
Second, the workflow often forces teachers to accept the AI’s mark or discard it entirely. A common X complaint is that the AI’s recommendation is presented as a final number, leaving no room for a teacher to say, “I’ll give 0.75 instead of 1 because the argument was incomplete.” When the system doesn’t let educators insert their own rationale, the AI suggestion becomes a distraction rather than a starting point.
How Quesly Solves It
Quesly’s design flips that script. After you upload class notes—whether as a TXT file, a text‑based PDF, or simply paste the content—Quesly generates a set of questions and a corresponding MCQ answer key. For written responses, the platform’s Jev engine waits until a student submits their answer, then produces a suggested mark together with a brief reason (e.g., “Key term present, but argument lacks evidence”). This suggestion lands in a teacher‑only view where you can compare it side‑by‑side with the original student work.
Crucially, the teacher retains full authority to edit the mark before releasing results. You can increase, decrease, or leave the suggestion unchanged, and you can add your own comment explaining the decision. Once you’re satisfied, you save the final mark and release the results to the student. The workflow respects the teacher’s judgment while still giving a concrete AI starting point, eliminating the “ignore‑and‑re‑grade” loop that dominates many community discussions.
Example (synthetic)
Imagine a Reddit post in r/teaching titled “AI gave full credit for my history essay, but I think it’s half‑credit.” The synthetic screenshot shows the teacher’s screen: a student ID, the submitted essay, and Jev’s suggestion—“Score: 1.0, Reason: Key event mentioned.” Below, the teacher clicks “Edit Mark,” changes the score to 0.5, and adds a note: “Argument missing supporting evidence.” After saving, the teacher hits “Release Results,” and the student sees the final score with the teacher’s comment.
- Step 1: Teacher uploads notes → Quesly creates questions.
- Step 2: Students answer, work is locked on submission.
- Step 3: Jev suggests a mark with a brief reason.
- Step 4: Teacher reviews, adjusts score, adds comment.
- Step 5: Final mark saved and released to student.
Teacher Judgment Required
Even with Quesly’s suggestions, the teacher must still verify three things: (1) that the generated question aligns with the intended learning outcome, (2) that the AI’s reasoning for a suggested mark matches the rubric you set, and (3) that any adjustments you make are documented for student transparency. The platform does not auto‑grade MCQs beyond the fixed answer key, so you must confirm that the key reflects the correct option before releasing results.
Because Quesly locks the submission once a student hits “Submit,” you won’t see later edits from the student, which mirrors the concern many teachers voiced about post‑submission changes. This lock ensures the integrity of the work you are reviewing, but it also means your initial review must be thorough.
Practical Takeaway
Start by using Quesly to generate your next quiz from a set of lecture notes. Before you share the quiz, skim the auto‑created questions and answer key—tweak any wording that could cause ambiguity. When the class submits, treat Jev’s suggested marks as a draft: compare each suggestion to your rubric, adjust the score if needed, and add a brief comment that explains the change. Finally, release the results and let students see both the score and your feedback.
By positioning the AI suggestion as a draft rather than a final verdict, you keep the efficiency boost while preserving the professional judgment that teachers value. This approach directly addresses the Reddit and X frustrations about “AI suggestions ignored,” turning a noisy recommendation into a useful, editable tool.
