Education
Running quizzes for a 91-student course, from entry to semester rollover
Posting questions was only part of running the class. I connected section entry, timing, saved answers, submission and semester archives into a workflow I could check.
The problem
A 91-student course needed repeatable section, timing, answer and submission handling.
My approach
I connected the course rules to entry, server-side saving, deadline submission and semester archives.
What changed
I created an inspectable operating flow and a practice route separate from student grading records.
BUILD DETAILS
Build details & ideas to reuse
01Start with the work that repeats every week
My architecture-law course at Inha Technical College had 91 enrolled students. Beyond writing questions, I needed to manage which section could enter and when work was due. I set the teaching requirements and used an agent to turn the recurring steps into software and operating notes.
02From entering the quiz to submitting it
The system checks section and timing conditions, manages each attempt’s window, saves answers on the server and handles submission at the deadline. Instructor practice is separate from student grading records so I can check the flow before class.
03Handle reloads and the next semester
I checked that reloads preserve attempt state and that saving and submission follow the course rules. I archived earlier materials before switching semesters. Browser assessment controls support the process, but cannot prevent every action outside the browser.
04Keep public resources separate from class records
I publish my own planning, source-checking and self-review checklists alongside this account. Student identities, marks and current answers remain within course operations. Next I would like to aggregate support requests, missed submissions and recovery time without exposing personal records.