Repair Management System

Repair Management System

Repair Management System

A comprehensive platform that simplifies issue reporting and accelerates repairs across educational institutions.

A comprehensive platform that simplifies issue reporting and accelerates repairs across educational institutions.

A comprehensive platform that simplifies issue reporting and accelerates repairs across educational institutions.

Role

Product Designer

Year

2025

Client

Tzohar Halev
(Freelance)

Timeline

4 Weeks

Teammates

Developer
Project Manager

Introduction

Overview

Managing Repairs Shouldn't Be a Guessing Game

Managing Repairs Shouldn't Be a Guessing Game

Keeping track of repairs across dozens of schools is no small task. This responsive, multi-role platform brings clarity to the process, making it easy for staff to report issues, for maintenance teams to manage tasks efficiently, and for senior managers to get real-time oversight, all in one place.

The Challenge

The Cost of an Informal Process

The Cost of an Informal Process

Withour this system, most incident reporting was done via phone, emails, or even handwritten notes.
This caused:

Delays in problem resolution

Lack of transparency about progress

Difficulty prioritizing incidents

Miscommunication between parties

Difficulty prioritizing incidents

Miscommunication between parties

Delays in problem resolution

Lack of transparency about progress

Difficulty prioritizing incidents

Miscommunication between parties

Research

User Interviews

Three User Types, One Broken Process

To understand pain points and needs, I conducted interviews with users from all three groups:

🧑‍💼 Manager

  • No status tracking.

  • Relied on Excel, which was manually updated-if at all.

  • Only learned of stuck issues after repeated complaints.

  • Lacked visibility into team performance and open issues.

🧑‍🏫 Reporting Employee

  • No formal way to report an issue- relied on tools like email or WhatsApp.

  • No confirmation the issue was received, tracked, or solved.

  • Unsure if reporting was even worth the effort.

🔧 Technician

  • Vague issue descriptions made diagnosis hard or impossible.

  • Issues with poor details often went unresolved.

  • Categorizing issues could streamline workflows.

  • Images help a lot.

Design Strategy

Information Architecture

Every Pixel Helps Users Feel in Control

I used NotebookLM to structure the entire journey- from issue reporting to resolution confirmation.
This clarified role-based handoffs, status changes, and edge cases.

AI-Powered Prototyping

Fail Fast, Learn Smarter

Tools like Lovable, Base44, V0, and Bolt helped me explore different interaction models.
These AI tools sped up ideation, tested assumptions, and inspired variations I wouldn’t have considered alone.

This helped me:

  • Validate assumptions quickly

  • Spot edge cases

  • Get fast feedback from stakeholders

Base44

During this process, I identified two major bottlenecks:

  1. Too many required fields for reporters

  2. Limited visibility for managers

The Design

The Solution

Formalize the Informal, For Fast and Trackable Fixes

The Design

The Solution

For fast and Trackable Fixes

Design Decisions

Key Features Screens

Key Features Screens

Issue Reporting

Initially, I explored a single-page form that presented all the reporting fields at once. While comprehensive, this approach quickly felt overwhelming—especially for non-technical users facing a stressful issue they just encountered.

Before: One long form.
After: Streamlined into three clear steps.

(2) Issue details

(3) Repair preferences

To address this, I applied the principle of gradual disclosure and restructured the form into three simple, guided steps:

  1. Reporter details

  2. Issue details

  3. Repair preferences

This change reduced cognitive load, improved completion rates, and gave users a clearer sense of progress through the reporting process.

Visual Overview

A dashboard that gives managers a quick glance

Status Columns

The kanban-style view groups issues by status. This allows drag-and-drop updates and encourages real-time tracking.

Calendar View

Maintenance staff and managers can both view and assign tasks by day.
This keeps everyone aligned and increases accountability.

Issue Display

Shows all report info in one place, with options to edit or delete for better accuracy and control.

Mobile

Mobile responsiveness was essential, as most reporting and repair actions happen on phones. The design had to stay clear, fast, and easy to use on small screens.

Reflection

My key learnings from this project

My key learnings from this project

  • Designing a complex system like this was deeply rewarding.
    It challenged me to think not only about beautiful UIs, but also about system-level clarity, accessibility, and emotional ease.

  • Using AI tools along the way helped me work faster and more strategically.
    Most importantly, I stayed focused on the human experience—crafting a solution that made each user feel seen, supported, and in control.

Research

User Interviews

Three user types, One broken process

Three user types, One broken process

To understand pain points and needs, I conducted interviews with users from all three groups:

  • No status tracking.

  • Relied on Excel, which was manually updated-if at all.

  • Only learned of stuck issues after repeated complaints.

  • Lacked visibility into team performance and open issues.

🧑‍💼 Manager

  • No formal way to report an issue- relied on tools like email or WhatsApp.

  • No confirmation the issue was received, tracked, or solved.

  • Unsure if reporting was even worth the effort.

🧑‍🏫 Reporting Employee

  • Vague issue descriptions made diagnosis hard or impossible.

  • Issues with poor details often went unresolved.

  • Categorizing issues could streamline workflows.

  • Images help a lot.

🔧 Technician

To understand pain points and needs, I conducted interviews with users from all three groups:

🧑‍💼 Manager

  • No status tracking.

  • Relied on Excel, which was manually updated-if at all.

  • Only learned of stuck issues after repeated complaints.

  • Lacked visibility into team performance and open issues.

🧑‍🏫 Reporting Employee

  • No formal way to report an issue- relied on tools like email or WhatsApp.

  • No confirmation the issue was received, tracked, or solved.

  • Unsure if reporting was even worth the effort.

🔧 Technician

  • Vague issue descriptions made diagnosis hard or impossible.

  • Issues with poor details often went unresolved.

  • Categorizing issues could streamline workflows.

  • Images help a lot.

Design Strategy

Information Architecture

Every pixel helps users feel in control

Every pixel helps users feel in control

I used NotebookLM to structure the entire journey- from issue reporting to resolution confirmation.
This clarified role-based handoffs, status changes, and edge cases.

AI-Powered Prototyping

Fail Fast, Learn Smarter

Fail Fast, Learn Smarter

Tools like Lovable, Base44, V0, and Bolt helped me explore different interaction models.
These AI tools sped up ideation, tested assumptions, and inspired variations I wouldn’t have considered alone.

During this process, I identified two major bottlenecks:

  1. Too many required fields for reporters

  2. Limited visibility for managers

Timeline

4 Weeks

Teammates

Developer
Project Manager

Role

Product
Designer

Year

2025

Client

Tzohar Halev
(Freelance)

Back to top

Thanks for Diving In! Explore More

Thanks for Diving In!
Explore More

Thanks for Diving In!

Explore More