Teacher Attendance Reporting

Research, UX design, and redesign of
a teacher attendance reporting flow.

Nice to meet you - Mashov system

The MASHOV System is the official pedagogical management system of the Ministry of Education used in schools across Israel. It supports daily educational workflows such as lesson documentation, attendance tracking, and continuous monitoring.

Since the system is used frequently – both during the school day and later at home after long working hours – its usability directly affects the efficiency, focus, and cognitive load of teachers.

schools across Israel
0
daily users (students & parents)
M 1

For teachers with low digital
literacy, reporting in the system is
often the hardest part of the day.

Problem

Lack of Clarity, Complex for Daily Use


The system lacks clarity and requires unnecessary cognitive effort for routine daily actions, making consistent use difficult.

Objectives

Improve the visual design and overall user experience

of the system, which is currently perceived as outdated and uninviting.

Position the system as a strong and central school-wide tool

encouraging more schools to adopt it as part of their daily operations.

Encourage consistent and confident use by teachers and students,

reducing friction, delays, and incomplete workflows.

Focus And Opportunity

When reporting feels
harder than teaching

Rather than attempting to redesign
the entire system,
this project focuses on a single,
high-frequency interaction: student attendance reporting

Attendance reporting is performed daily, under time pressure, and often after long school days.
 It represents a moment where usability issues are felt immediately — especially by teachers with low digital literacy.
By narrowing the scope to this specific flow, the project aims to explore how small UX decisions can significantly reduce cognitive load, increase confidence, and support everyday work in a large-scale educational system

Research

Market
Analysis

Learning from Similar Systems

The study examined reporting and management systems that handle
frequent and mandatory daily operations.

Research

User Research

In order to better understand
the existing issues in the system,
I conducted interviews and observations
with several current users.

“It should be here.”

“Just thinking about reporting
attendance in the system is exhausting.”

“Look how long it took me to
report attendance for
just four lessons.”

These observations highlighted recurring friction points in daily attendance reporting.

User Persona

Quote

“Just thinking about
reporting attendance
in the system feels
exhausting.”

Goals

  • Report attendance quickly
    and clearly
  • Avoid mistakes and
    missing data
  • Complete system tasks
    without struggling with
    technology

Background

Veteran, mission-driven educator

A veteran and dedicated teacher who sees teaching as a mission
Strong personal connection with students is at the core of her work
Began using a personal computer only in recent years
Most system-related tasks are done after long workdays

Behaviors

Minimal, Delayed System Usage

  • Unclear and non-intuitive system structure
  • Too many options without clear hierarchy
  • Long processes for simple, daily actions
  • Feelings of frustration and mental fatigue when using the system

Pain Points

High Cognitive Load

  • Unclear and non-intuitive system structure
  • Too many options without clear hierarchy
  • Long processes for simple, daily actions
  • Feelings of frustration and mental fatigue when using the system

User Journey

Conclusions

01.

Unclear action hierarchy on the home screen

The home screen contains actionable elements, but lacks a clear visual hierarchy that highlights primary actions.
 Attendance reporting is not immediately perceived as the main daily task upon entry.

02.

Fragmented attendance reporting flow

Attendance reporting is spread across multiple screens and menu paths,
 includes non-essential actions, lacks a clear hierarchy,
 and uses terminology that does not align with the language commonly used in the education system.
 As a result, a daily, repetitive task becomes cognitively demanding and error-prone.

03.

A powerful but hard-to-access search tool

The system includes a useful and effective search tool
 that can significantly support daily work.
 However, it is hidden within the interface,
 not easily discoverable, and not integrated into the main reporting flow.
 As a result, users are often unaware of its existence or avoid using it altogether.

User Flow

Weiframe

First, I organized all the information relevant to the system.
 Then, I began by creating initial wireframes for the main dashboard and the attendance reporting screens.

 Figma Make was a significant help in this process, allowing me to generate the screens from scratch and iterate quickly.

Design

First, I organized all the information relevant to the system.
 Then, I began by creating initial wireframes for the main dashboard and the attendance reporting screens.

 Figma Make was a significant help in this process, allowing me to generate the screens from scratch and iterate quickly.

Graphic language

First, I organized all the information relevant to the system.
 Then, I began by creating initial wireframes for the main dashboard and the attendance reporting screens.

 Figma Make was a significant help in this process, allowing me to generate the screens from scratch and iterate quickly.

Screens

01.

Solution – Home Screen Redesign

How the home screen addresses the problem?

By reorganizing the home screen hierarchy, the system now prioritizes actions at a glance, making it clear what status to view and what action to take.
A daily schedule is displayed in the center of the screen. Attendance reporting is displayed as the primary login action, reducing cognitive load and supporting fast, routine use.

Subject Cards

Subject cards group all relevant information and actions per subject. They were positioned as a secondary element to reduce visual overload.

Side Menu

The side menu was simplified to include only key sections.
 Secondary actions are shown contextually on the screen.

The top status area was transformed from static data into actionable information.
Users can respond directly without navigating to additional screens.

Top Status Area

Based on user interviews and observations, I identified that teachers often need to navigate back and forth in time to complete or review reports.
To reduce friction and cognitive load, I designed a flexible time view that allows switching between daily, weekly, and specific date views directly from the main screen.

This dynamic time control gives teachers clear ownership over their schedule and reporting flow, without excessive navigation or repetitive back-and-forth actions — making the system easier to manage, especially for users with lower digital confidence…

Dynamic Time View

Daily View (Default)

The daily view is set as the default, as it best supports the teacher’s everyday routine.
 It allows quick access to today’s schedule and enables immediate attendance reporting directly from the current day.