Exam-centre operations depend on many people completing different tasks at the right time. Centre heads need oversight, invigilators need clear operational guidance, and students need an exam experience that feels calm and understandable.
Desisle designed a tablet application for exam-centre management, creating role-specific experiences for centre heads, invigilators, and students. The work brought these multiple perspectives into one product with a shared design language, clear instructions, accessible navigation, and exam-focused interface patterns.
Project Overview
- Industry: Education and assessment
- Product: Tablet application for exam-centre management
- Platform: Tablet application
- Primary users: Centre heads, invigilators, and students
- Services: UI/UX and product design
- Role: UI/UX Designer
- Team: One UI/UX Designer, one stakeholder, and two mobile developers
- Project period: 2023-2024
What Did Desisle Do?
Desisle designed an end-to-end tablet experience for exam-centre operations. Starting from client-provided basic wireframes, the work developed role-specific application flows for centre heads, invigilators, and students while maintaining a consistent design system across the product.
The engagement included initial interface concepts, tablet UX research, design guidance, and collaboration with mobile developers to help ensure the approved product direction was accurately implemented.
The Challenge
The product needed to support distinct groups with different goals and responsibilities:
- Centre heads: Need visibility and control over exam-centre activity.
- Invigilators: Need operational clarity while coordinating exams.
- Students: Need direct instructions, easy navigation, and a focused environment during an assessment.
Designing one application for these groups required more than creating separate screens. Each role needed a tailored experience, but the product still had to feel familiar, consistent, and easy to use for people across a broad age range.
The project also began as a new concept, with only basic client wireframes available. The design process therefore had to turn early ideas into a clearer tablet product experience.
Designing for Multiple User Roles
The application was designed around a shared exam lifecycle, while giving each persona access to the information and actions relevant to their responsibilities.
Centre Head Experience
The centre-head experience was intended to support oversight of exam-centre operations. The interface needed to surface relevant information clearly, helping users understand the state of examination activities without navigating through unnecessary complexity.
Invigilator Experience
The invigilator experience needed to support action during an active exam environment. Clear steps, instructions, and navigation were essential because invigilators may need to complete operational tasks quickly and confidently.
Student Experience
The student experience focused on clarity and reduced cognitive load. Exam instructions, timers, and navigation needed to be easy to understand so students could remain focused on the assessment rather than the device interface.
Recommended visual: A role map showing Centre Head → Invigilator → Student, with their position in the exam lifecycle.
Why it matters: It demonstrates why one tablet product needed different experiences rather than a single generic dashboard.
AI-Assisted Design Approach
AI-assisted design should only be presented as part of this project if AI was genuinely used during the design process. The following are potential applications, not confirmed project deliverables.
- Exploring role-based user-flow variations from early wireframes.
- Generating alternative information hierarchies for tablet screens.
- Reviewing terminology and instruction clarity for different user types.
- Identifying repeated UI patterns across centre-head, invigilator, and student flows.
- Supporting preliminary accessibility checks for readable labels, timing states, and navigation cues.
- Documenting design decisions for developer handoff.
AI should not be presented as having independently designed the application, performed validated usability research, tested real users, or generated the final product without designer review unless those activities are supported by project evidence.
Key UX Decisions
1. Create Distinct Experiences Within One Application
Problem: Centre heads, invigilators, and students have different needs and levels of responsibility.
Decision: Design separate role-based experiences while using a unified visual language.
Why: Each user group needs only the controls and information relevant to its role, while familiarity across the application supports easier adoption.
Trade-off: Role separation must not create visual inconsistency or make users feel they are using unrelated products.
2. Design for the Tablet Context
Problem: Tablet applications have different interaction and layout needs from desktop or phone products.
Decision: Research tablet-design patterns and create layouts suited to a larger touch interface.
Why: Tablet use supports more visible information and larger interaction areas, but it also requires clear spacing, readable hierarchy, and reliable touch targets.
Trade-off: The interface must balance information visibility with simplicity so users are not overwhelmed during an exam-related task.
3. Prioritise Clarity During Time-Sensitive Tasks
Problem: Exams involve time pressure, instructions, and users who may have varying comfort with technology.
Decision: Use a minimal visual approach, clear instructions, exam timers, and simple navigation.
Why: Users need to understand what to do next without spending attention on the product interface.
Trade-off: The design needs enough guidance to prevent confusion without adding excessive instructional content to every screen.
4. Maintain Consistency Across Roles
Problem: Role-specific functionality can lead to fragmented interface patterns.
Decision: Create a shared design language across the application.
Why: Repeated navigation, colours, controls, feedback states, and content patterns make the product easier to learn and maintain.
Trade-off: Shared components need enough flexibility to work across operational and student-facing contexts.
The Designed Experience
The tablet-app design brought together the core interface elements required to support exam-centre operations:
- Role-based interfaces for centre heads, invigilators, and students.
- Tablet-focused layouts and touch interactions.
- Exam timers and time-aware interface states.
- Clear instructions and operational guidance.
- Easy navigation between relevant tasks.
- A clean, minimal visual style.
- A consistent design language across distinct user roles.
- Initial design concepts and implementation guidance for mobile development.
The design aimed to make exam-related tasks easier to understand for operational staff and students, while respecting the different responsibilities of each role.
Recommended visuals:
- Centre-head dashboard or operational overview.
- Invigilator task flow or live exam-management screen.
- Student exam screen with timer and clear instructions.
- Shared component library demonstrating consistency across roles.
Outcome
The project delivered a unified tablet-application design with role-specific functionality for centre heads, invigilators, and students. The supplied project context reports positive feedback on the product’s intuitive interface, usability, visual consistency, and clear exam-related features.
No verified performance or live-product data was provided. This case study does not claim lower invigilation errors, faster exam setup, increased student completion, improved academic outcomes, or operational savings.
What We Learned
Multi-role products work best when roles share a common system but do not share every screen. Each group needs an interface shaped around its responsibilities, yet common patterns should make the overall product feel coherent.
The project also reinforced that exam-related products must reduce unnecessary uncertainty. Clear instructions, visible timing, and predictable navigation can help users focus on the assessment process instead of figuring out how the application works.
Building a Similar Assessment Product?
Assessment and EdTech teams need interfaces that account for operational staff, supervisors, and learners at the same time. A strong product experience starts by defining which decisions each role must make, what information each role needs, and what the application should remove from their attention during time-sensitive moments.
Desisle can support EdTech and assessment-platform teams with tablet-app UX, role-based workflow design, design-system development, and developer-ready product interfaces.