MoveHub — Neetu Sajan
UX/UI Design · Non-Profit CRM · Shelter Movers

MoveHub — CRM for
Shelter Movers

Designed a customer relationship management application to assist in facilitating, coordinating, planning, and executing moves within Shelter Movers — a national, volunteer-powered charitable organization providing moving services to women and children fleeing abuse.

Lead UX Designer UX/UI Design Prototyping Information Architecture
Impact
11+Cities across Canada
2500+Volunteers
150+Clients / month
11+
Cities deployed
2,500+
Volunteers using app
150+
Clients per month
6
User roles supported
01 — Project brief

The challenge

Design a digital application that will enable volunteer teams to coordinate, plan, and conduct moves from start to finish. Each client is served by a team of volunteers — intake coordinators, move coordinators, drivers, and movers — requiring significant coordination, planning, and communication.

"The need for a digital solution that would enable teams to coordinate, plan, and conduct moves — in one place, seamlessly."

Who uses MoveHub

Intake

Intake Coordinator

Opens new cases and manages the initial intake process for each client

Intake

Intake Coordinator Supervisor

Reviews and approves intake cases before they move forward

Move

Move Coordinator

Plans and coordinates each move — volunteers, logistics, timelines

Move

Move Coordinator Supervisor

Oversees move coordinators and approves moves at key milestones

Admin

System Administrator

Manages templates, permissions, and operational health of the platform

Field

Drivers & Movers

Execute the move on the ground — need clear instructions and confirmed itineraries

02 — Research & discovery

Re-examining the existing system

I re-examined the information architecture and existing functionality of the application — analyzing user feedback, mapping the IA of the existing app, and flagging any flaws within the user flow.

Staff journey map
Key insight from user feedback
Two critical pain points

There was an overload of information in the app, and it was difficult for users to navigate from start to finish. The existing design dispersed information across multiple sub-pages, with no clear linear structure matching how a move actually progresses.

03 — Design decisions

What I changed and why

📋
Simplified template management

Removed the archive section — primary users had no need for it. Proposed a simple solution where users can edit and save templates within the browser. Fewer clicks, same goal achieved.

🔢
Chronological tab structure

Re-structured the primary move page so tabs appear in the order a coordinator works through them — visually relaying the user flow in chronological order, laying all necessary information on one page.

📊
Status bar for move stages

Added a status bar at the top that clearly shows which stage the move is in. A critical missing feature — without it, there was no way for users to know the current status or which reviews were pending.

04 — Final screens

The redesigned application

The redesign was driven by two clear findings from user research: information overload, and no clear path through the app from start to finish. Every design decision traces back to one of those two problems.

Move Coordinator

Restructuring the move flow around how coordinators actually work

The primary moves page was the most complex surface in the application — and the one with the most friction. The original design scattered move steps across multiple sub-pages with no clear sequence, making it easy to miss critical steps or lose track of where a move stood.

The key insight was simple: coordinators move through a move chronologically. The redesign reflects that. Tabs were restructured to mirror the actual order of operations — so a coordinator can follow the flow from left to right and know exactly where they are at every stage.

The second major addition was a status bar. Without it, there was no way to know what stage a move was currently in — a critical gap given that each stage requires specific reviews and approvals before progressing. I also had to account for conditional logic: depending on the move stage, certain actions need to be enabled or disabled. Mapping this out during the research phase made those decisions traceable and defensible in the final designs.

Chronological tab order — tabs now follow the sequence a coordinator works through, reducing cognitive load and the chance of missed steps.
All information on one page — consolidated from multiple sub-pages into a single surface, eliminating unnecessary navigation.
Status bar added — clearly shows the current move stage and surfaces which reviews are pending or approved.
Conditional button states — actions are enabled or disabled based on move stage, preventing errors without needing to explain the rules to the user.
Moves - Volunteers
Click to expand ↗
Moves - Move Info
Click to expand ↗
Moves - Confirmation
Click to expand ↗
Moves - Client Confirmation
Click to expand ↗
Moves - Thank You Note
Click to expand ↗
Move Coordinator - Moves
Click to expand ↗
System Administrator

Simplifying template management for administrators

The templates section existed to allow administrators to create and manage reusable templates for each move type. But the original design included an archive section that primary users had no practical need for — adding visual clutter and extra navigation without adding value.

The redesign stripped this back to what the user actually needs to do: edit a template and save it. Rather than requiring multiple steps across different pages, the updated flow lets administrators edit and save templates directly in the browser. The goal is identical — the path to get there is significantly shorter.

Archive section removed — eliminated a feature primary users never needed, reducing cognitive load and page complexity.
Inline edit and save — templates can now be edited and saved in the browser in a single flow, reducing clicks without reducing functionality.
System Admin - Itinerary
Click to expand ↗
System Admin - Itinerary 2
Click to expand ↗
System Admin - Itinerary 3
Click to expand ↗
System Admin - Lead Mover Notes
Click to expand ↗
System Admin - Templates
Click to expand ↗
System Admin - Templates 2
Click to expand ↗
05 — Reflection

Key takeaways

🔄

Systems thinking & design thinking

Systems thinking is a holistic approach that considers multiple factors simultaneously. This project facilitated a shift away from linear thinking to circular thinking — understanding how each design decision affects every other part of the system.

🌍

Design with direct impact

The application is used by 2,500+ volunteers across 11+ cities in Canada, serving 150+ clients every month. Design decisions here directly increase the capacity for how many moves are completed — and ultimately help more people in need.

The biggest takeaway

"This project put into perspective the importance of design — and was very inspiring for me as a designer."

Building for a charitable organization serving vulnerable people made every UX decision feel meaningful. The clarity, efficiency, and reliability of this app directly affects the organization's ability to help people at some of the most difficult moments of their lives.