BENEFICIARY TRANSPORT OPERATIONS

Community Service

Community Service is an end-to-end platform that coordinates beneficiary transportation between charitable associations, the General Syndicate of Cars, and transportation companies. Associations manage beneficiary records and submit trip requests, the syndicate reviews and assigns approved requests, and transport companies allocate vehicles and drivers while tracking execution. The platform brings the full operational journey into one role-based system.

My roleProduct Designer & Full-Stack Developer

Workflow DesignRole-Based UXReact & TypeScriptNode.js & ExpressPostgreSQLREST APIPermissionsDeployment

StatusCompleted

Year2025

View Live Project View Technical Showcase

Problem

Coordinating transportation across multiple organizations without a unified workflow.

Beneficiary transportation requires information and decisions to move between a charitable association, the syndicate, and a transportation company. The association must prepare beneficiary details, assistance needs, locations, timing, and supporting documents. The syndicate then needs to review the request, record a decision, and assign a suitable company, while the company must allocate operational resources and report progress. Without a shared request record, responsibilities, status updates, and operational information can become difficult to coordinate.

Solution

A single operational workflow connecting submission, approval, and execution.

The platform keeps every transport request in one shared lifecycle while presenting each organization with only the tools, decisions, and operational data relevant to its role.

Product scope

How the solution is organized.

Association Workspace

Associations manage beneficiaries and prepare transport requests with schedules, locations, supervisors, assistance needs, selected beneficiaries, and supporting documents.

Syndicate Review

A centralized request view supports review, permitted corrections, documented rejection, approval, and assignment to an eligible transport company.

Transport Operations

The company accepts assignments, selects a branch, vehicle, and qualified driver, then advances the trip through ready, started, and completed states.

Shared Visibility

Messages, notifications, calendars, reports, and status history keep responsibilities and the next required action visible across organizations.

Design decisions

Product decisions shaped around each organization’s operational responsibilities.

Role-specific workspaces give associations, the syndicate, and transport companies distinct navigation, tools, and protected permissions. Arabic and English support, RTL layouts, responsive behavior, and light and dark modes keep these workspaces usable across different environments.

A single beneficiary-centered request record moves through draft, review, approval, assignment, execution, and completion. Request creation includes assistance needs and supporting documents, while a review step and centralized detail view keep decisions, edits, attachments, and status history connected.

Resource assignment is restricted by operational readiness: vehicles are filtered by branch, status, and required capacity, while drivers are filtered by availability and licence validity. Dashboards, status tabs, search, calendars, messages, and notifications provide the visibility needed to act without creating conflicting reservations.

Technical architecture

The implementation behind the interface.

React + TypeScriptRole-specific operational workspaces

Express REST APIWorkflow rules and protected actions

PostgreSQLRequests, beneficiaries, resources, and status history

Connected services & concerns

Role-Based Access ControlProduction Demo InitializationRender Deployment

Evidence

What is implemented, constrained, and verified.

Engineering evidence

Association, syndicate, and transport-company actions are separated through role-based workspaces and permissions.
One request record preserves decisions, attachments, assignments, execution states, and history throughout the lifecycle.
Vehicle and driver options are filtered by branch, capacity, readiness, availability, and licence validity.
Production demo-account initialization was hardened so reviewers can access stable seeded roles.

Constraints & trade-offs

The workflow spans three organizations with different responsibilities and permission boundaries.
Resource assignments must avoid capacity, availability, and scheduling conflicts.
The public demo uses non-sensitive demonstration data rather than real beneficiary records.

Validation

The deployed demo exercises the association, syndicate, and transport-company journeys with separate accounts.
Request-state transitions and resource eligibility are validated through the connected frontend and API workflow.
Responsive Arabic and English interfaces were reviewed across the role-specific workspaces.

Gallery

Platform Interfaces and Operational Workflow

The gallery highlights the syndicate’s charity directory, beneficiary record management, and the transport company’s fleet workspace, showing how the platform adapts its interface to each organization’s responsibilities.

Outcome

A complete product that turns cross-organization coordination into a trackable process.

The application can manage the complete transportation request lifecycle, from beneficiary registration and request creation through review, assignment, execution, and completion. Each organization works through a focused workspace while the request, its status, communication, and history remain connected. The project demonstrates the ability to design and build a multi-role product that combines user experience, operational rules, data management, and full-stack development.

Product & UX DesignReact & TypeScriptNode.js & ExpressPostgreSQLREST APIRole-Based Access ControlTesting & Deployment

Next project

Pulse

Pulse is a mobile discovery app for exploring places across Makkah and Jeddah through structured place signals rather than static listings. It connects search, filters, map exploration, detailed place context, saved collections, comparisons, and editable multi-stop outing plans in one flow.