Hook: The Real‑World Frustration
Scrolling through r/teaching on a Tuesday night, you’ll see the same thread pop up over and over: “My AI grading tool keeps giving me scores that make no sense, and I end up re‑grading everything by hand.” A teacher on X echoed the sentiment, posting a screenshot of a spreadsheet full of red‑flagged AI marks and a caption that read, “When the AI says 9/10 for a half‑finished answer, I feel like I’m back to the stone age.” The pain is palpable—educators want the time‑saving promise of AI, but they can’t trust suggestions they don’t understand or can’t tweak quickly.
The chatter isn’t just venting; it’s a call for a system that respects the teacher’s expertise. In many posts, teachers describe spending extra minutes—sometimes hours—cross‑checking AI output, writing notes on why a suggestion is wrong, and then manually entering the corrected score. The result is a workflow that feels more like a penalty than a help, and the AI suggestions end up ignored altogether.
The Problem Deep Dive
At the heart of the issue is a mismatch between AI output and the nuanced judgment teachers apply to written responses. On Reddit, a user posted a sample of an AI‑generated mark that awarded full credit for a paragraph that only partially addressed the prompt. The teacher’s comment highlighted the missing partial‑credit rubric that had been built over years of classroom practice. Without a clear way to adjust the AI’s reasoning, the suggestion becomes a distraction rather than a shortcut.
Another common thread on X mentions the “black‑box” feeling: the AI tells you a student earned 7 out of 10, but it offers no transparent justification that aligns with the teacher’s rubric. When the AI’s reasoning conflicts with the teacher’s expectations, educators feel forced to either accept a flawed mark or spend time rewriting the feedback. The underlying frustration is not with AI itself, but with the lack of a structured hand‑off point where teachers can review, edit, and approve the AI’s recommendations before they affect student grades.
How Quesly Solves It
Quesly’s workflow is built around teacher control from the moment an assignment is created. Teachers start by uploading notes in TXT, a text‑based PDF, or by pasting directly into the platform. The system extracts the text, then generates a set of questions and a fixed answer key for any multiple‑choice items. Importantly, the generated content is displayed for the teacher to verify before it is released, ensuring that the source material matches the intended assessment.
When students submit written answers, Quesly locks the work and runs Jev, an AI module that suggests marks and provides a short rationale after submission. Those suggestions appear alongside the original student response, but they remain suggestions only. Teachers must actively review each AI recommendation, compare it to their rubric, and then enter the final mark. The platform records the teacher’s final decision, and only after the teacher saves and releases the results do students see their grades. This two‑step review guarantees that AI assistance never bypasses educator judgment.
Real Example (Synthetic)
Imagine a Reddit post titled “How I finally got AI to respect my partial‑credit rubric.” The user shares a screenshot of Quesly’s assignment page: a teacher has uploaded a PDF of lecture notes on photosynthesis, generated five short‑answer questions, and set up a private access code for the class. After students submit, the AI suggests a mark of 8/10 for a response that mentions chlorophyll but omits the light‑dependent reactions. The suggestion includes a brief note: “Key point on light‑dependent reactions missing.” The teacher clicks into the review pane, checks the original rubric (which awards 5 points for chlorophyll, 5 for light‑dependent reactions), and adjusts the mark to 5/10, adding a custom comment. Once all responses are reviewed, the teacher hits “Release Results,” and the class sees their updated scores on the student portal.
The post continues with a comment thread where another educator asks, “Can I see the AI’s reasoning before I change anything?” The original poster replies, “Yes—Jev’s suggestion appears right next to the answer, so you can compare it line‑by‑line with your rubric before you type in the final mark.” This synthetic exchange mirrors the real‑world desire for transparent AI assistance that never overrides teacher authority.
Teacher Judgment Required & Practical Takeaway
Even with Quesly’s safeguards, teachers still need to perform three key checks: verify that the generated questions accurately reflect the uploaded notes, confirm that the fixed MCQ answer key matches the intended correct options, and review each Jev suggestion against their own marking rubric before entering the final score. Those steps keep the assessment fair and aligned with classroom expectations.
For a practical rollout, start by piloting Quesly with a single unit. Upload your notes, run the question generator, and spend a brief session reviewing the output with a colleague. Then, after a student submission, use the Jev suggestions as a first pass, but allocate a set amount of time—say ten minutes per batch—to adjust marks and add personalized feedback. Finally, release the results and gather student reactions. By treating the AI as a draft rather than a final verdict, teachers can reclaim the time they hoped to save while maintaining full control over grading decisions.
