Objective

Design a user friendly, scalable workflow that enables admins in the logistics industry to apply for gate passes for multiple employees across different ports within a single, streamlined request process. The goal was to reduce manual effort, improve accuracy and support real-world technical constraints such as API limitations and government system dependencies.

 Problem Overview

Admins at maintenance and logistics companies are required to apply for gate passes to allow employee entry into ports like Jebel Ali and Port Rashid. The existing system is:

• Manual and repetitive when handling high volumes of employees.

• Prone to human error due to document mismatches or incorrect data entry.

• Time consuming, especially when grouping employees by port or visit date.

• Lacking real-time visibility into application status and tracking.

• Not always equipped with integrations to government platforms, creating delays or dependency on outdated workflows.

User Needs

• A centralized platform to upload, review and manage gate pass applications.

• Ability to apply for multiple employees at once across ports in a single request.

• Flexibility to manage document uploads, assign ports and edit details before submission.

• Real-time visibility into the status of each gate pass.

• Easy error detection and correction before final submission.

Business Needs

• A streamlined workflow that reduces admin processing time and submission errors.

• Compatibility with Dubai Trade and port authority systems, including backup flows if APIs are not available.

• Scalable solution for high-volume application windows.

• Clear audit trail and tracking for compliance and operational oversight.
  
  

My Role

This was an independent assignment brief. I was a solo designer and I owned the end-to-end process: research, problem definition, workflow architecture, wireframing, and final UI. The project was completed in 2 days and presented to the internal team.

Design Process

Research & Discovery

This project was grounded in firsthand research across multiple touch points not just interviews, but personal experience inside the system itself. Understanding the gate pass process from both sides of the workflow was essential to designing something that would actually work in practice.

Who I spoke to
I conducted in-person interviews and conversations with people at every stage of the gate pass journey:

Speaking to both sides of the system revealed that the friction wasn't just an admin problem every delay or error on the admin's end directly affected how long employees waited to get access approved. The two experiences were tightly coupled.


Personal Experience as a Research Input

I also drew on direct personal experience. When obtaining my UAE driving licence, I had to go through the gate pass process myself to access the relevant facility. I went through the full application flow including researching and gathering the required documents: Emirates ID copy, passport copy and the specific supporting documents mandated by the port authority for visitor access.

Going through this process firsthand gave me a ground level understanding of how opaque and time consuming even a single application feels from the applicant's side no clear guidance on what's needed upfront, no feedback on status once submitted, and no way to know if something had gone wrong until it was too late.

While this experience was from a few years prior, the structural friction it revealed was consistent with what current JAFZA employees described in interviews suggesting these pain points are systemic, not incidental.


What the Research Revealed

Across all conversations and my own experience, a clear pattern emerged. The pain wasn't caused by any single broken step it was the accumulation of small inefficiencies across the entire workflow that made the process feel unmanageable, especially at scale.

Admins described spending the first two hours of their shift manually re-entering employee details they had submitted before. Engineers mentioned submitting their information to their company admin days in advance, only to find out at the last minute that a document was rejected or missing. Security staff flagged that errors were almost always discovered after submission at the point where fixing them required starting over.

These weren't edge cases. They were the everyday reality of a workflow that was built for individual submissions but was being used to process dozens of employees at a time, under deadline pressure, with no room for error.

Key Insight
The core problem was not that the process was complicated it was that the system gave admins no tools to manage complexity efficiently. Every error was discovered late. Every submission was treated as if it were the first. Every employee had to be processed as if the admin had never seen their documents before. The design opportunity was clear: build a system that remembers, validates early, handles volume, and gives both admins and employees visibility into what's happening at every stage.


Existing Workflow

HMW Questions

These insights directly shaped the 'How Might We' questions that framed the design challenge.

• HMW reduce the submission time for gate pass applications, especially during high-volume periods?

• HMW enable bulk submission of gate pass applications and group employees by port?

• HMW help the admin minimize and quickly resolve errors while filling out gate pass applications?

• HMW provide real time visibility and status tracking for all gate pass applications?

• HMW reuse previously verified employee data and documents to save time in future applications?

• HMW design an intuitive workflow that is easy for admins to use, even during urgent or high-volume situations?

These questions became the design briefs that guided both the wireframing phase and the final solution architecture.

Key Insights

Workflow Approaches

Wireframe & Exploration

Solution Strategy: Flexible Employee Gate Pass Workflows

To address the diverse operational needs of logistics admins, I designed three distinct but complementary solutions each optimized for different scenarios and levels of tech feasibility. The goal was to balance speed, accuracy, and adaptability while keeping user control and clarity at the center of the experience.

1. Manual Entry Workflow

Best for low-volume or on the go submissions.

This flow allows the admin to add employees one at a time through a structured form. It’s intuitive, mobile-friendly and ideal for small teams or when data is collected ad-hoc.

2. Bulk Import via API Integration

Best for high volume submissions with available data in Excel or internal systems.

In collaboration with IT teams, an API enabled workflow that allows admins to bulk upload employee data using structured templates. This significantly reduces manual input and errors.

3. Smart Table Workflow

Best for teams who need speed and flexibility but without full API automation.

I designed a smart table UI similar to a spreadsheet where admins can quickly add and edit multiple employees within a single dynamic interface. This is ideal when submissions vary slightly and need quick tweaking before finalizing.

Key Learnings