I have written a story of a user accomplishing the primary objective of marking assessment attempts of their students. There are sub-objectives that they will have to accomplish to achieve this primary objective. These are teacher creating a submission bucket, teachers (on behalf of students) or students submitting their assessment attempt, and teacher marking the attempt. I need you to enhance my story by improving the overall flow of the story, improving the order of the events, expanding on scenarios that lacks depth, proper grouping such as the story is about the primary objective, and the chapters of the story could be the sub-objectives, and asking me questions about some gaps/holes that I will need to fill and address.

---

Here’s my current writing about the user journey and experience:

”The mark assessment attempts is started when a teacher wants to mark attempts made by students for an assessment that they are examining their students on. We will have a library of assessments for teachers to choose from. Once they have selected an assessment, there will be a button that lets them create a bucket for students to submit their attempts - we will call this bucket, submission. The user can also choose to make a submission for a specific question of that assessment. Once a submission is created, the user is taken to the site of the bucket/submission document. In there, the teacher will have an option to either submit on behalf of students which will take them to a dedicated submission page. Or copy the URL with an invite code which they can give to students so students can make the submission. Regardless this will take them to our submission page. With the URL pathway, we will require an email as input so teachers can later differentiate. With the teacher submitting on behalf of students, once the submission is created, the teacher will have the option to assign the email for that submission (email of their student who made the attempt).

Let’s talk about the experience of submission. They are taken to a page where they can upload PDFs or images. PDFs are first converted into images. Images are then displayed on a staging container. And there will be empty containers for specific gradable questions (question numbers). The user then assign the pages (images) to specific buckets where the image or answer corresponds to which question number. Once the user has successfully assigned the content, they can submit. There will be instances that there will be only one question. And in that case, there will be no staging bucket. There’s only one container, and all images will go for that single question. Before making the submission, the user has to inform us if the images/pages have the question statement in them or if they are not there (only the answer). Once they are done, they can submit their attempt.

Once submissions are made. Our AI, Eh-Llie, will do preliminary marking of their attempts. Examining the question and answer sets against a marking criteria. It will come up with a detailed feedback and a grade. This preliminary because teachers will have to verify that the output of the AI is right. Each submission will be displayed as a card. And it will show various states such as whether it has been marked or verified or neither. The cards can be clicked which will take teachers to the marking page where they will be able to see feedback for questions, the preliminary marks from Eh-Llie, make edits on the preliminary feedback, or write their own feedback, and this is also where they will verify the mark, informing teachers and students that it has been finalised.