Promonexis
Start a project
Concept studies / Education
An exam-management concept connecting candidate access, question delivery and result review in one planned workflow.
Concept study. This describes a design intention, not a completed client engagement.
Online Exam Platform explores how an education team could move from separate forms and student lists to a more coherent assessment workflow. The original brief describes candidate access, a question bank, timed exams and staff-facing results. These are connected responsibilities: a candidate must receive the right paper, an attempt must have a clear beginning and end, and staff must understand how a score was produced. Promonexis presents this case study as a design concept for that journey. The focus is on reducing ambiguity at each handoff, rather than claiming that a particular institution has deployed the platform or achieved a measured improvement.
The intended users are students taking assessments and education staff preparing and reviewing them. In the scenario described by the brief, candidate lists, exam forms and result handling sit in separate places. That separation makes it harder to answer simple questions: who is eligible, which exam is open, and which attempts are ready for review? The organization and historical delivery status have not been established.
The proposed solution joins exam preparation, candidate access, timed participation and result review. Planning would start with the lifecycle of an assessment, including the states that staff and students need to recognize. Interface design would then separate preparation tasks from the focused exam screen. The application boundary would be responsible for checking access and interpreting submissions, rather than relying on a visible countdown alone. Scoring would follow explicit rules for objective questions; other question types would need their own agreed review process. This connects each screen to a practical responsibility and leaves room to test edge cases before anyone depends on it for a live assessment.
The proposed student workspace would show eligible assessments, instructions and the active attempt. Its purpose is to keep participation separate from preparation and result administration. Eligibility and submission rules would need agreement before these permissions are implemented.
The brief assigns question management and result visibility to staff and administrators. Their proposed workspace would support preparation and review. The exact boundary between staff and administrative powers remains a design decision; the concept does not claim an implemented permission matrix.
The design separates permission to use the platform from eligibility for a particular assessment. A student-facing entry point would make the available exam and its instructions clear before an attempt begins. The access rules, enrollment source and handling of late entrants need agreement before implementation.
A question bank and timed attempt are part of the original brief. The design would connect question selection to the paper being delivered and make progress understandable without exposing staff preparation tools. Saving, interruption recovery and the exact submission policy remain decisions to validate, not implemented guarantees.
The brief proposes automatic scoring for objective sections. A useful review screen would distinguish the submitted answer, the scoring rule and the resulting score. That separation would help staff investigate a disputed result without treating all assessments as though they use the same marking approach.
Keeping an exam definition separate from an individual attempt would make it easier to reason about what a student actually saw. No database engine, hosting provider or deployed architecture is asserted.
forms, candidate lists and result handling require staff to reconcile several sources.
an assessment has an explicit preparation, participation and review path.
The comparison describes the design goal; it is not a measured before-and-after result from a client deployment.
Discovery would map how candidates are enrolled and how papers are approved. Design would trace one complete attempt, including expiry and interruption. Validation would compare representative answers against agreed scoring rules before considering a limited pilot. These are proposed development steps, not a reconstruction of a past project timeline.
Timing is a business rule, not just an animation. A future implementation would need an authoritative submission policy and tests for boundary cases. Separating question preparation from attempt handling also limits the number of responsibilities on the candidate screen. These decisions require validation with the people administering the exam.
The expected operational benefit is a more traceable assessment workflow: staff could follow an exam from preparation to result review, while students would have a clearer route through their attempt. This is an intended benefit, not evidence of faster processing or better educational outcomes. A pilot would need to record completion errors, staff corrections and candidate support requests before any improvement could be claimed.
Possible next steps include agreeing an interruption policy, evaluating accessibility with representative candidates, and defining review rules for non-objective answers. None of these extensions should be marketed as complete until implementation and testing evidence is attached.
Tell us how the work runs today and we will help you decide what is worth building.