The problem
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.
The idea
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.
Associations manage beneficiaries and prepare transport requests with schedules, locations, supervisors, assistance needs, selected beneficiaries, and supporting documents.
A centralized request view supports review, permitted corrections, documented rejection, approval, and assignment to an eligible transport company.
The company accepts assignments, selects a branch, vehicle, and qualified driver, then advances the trip through ready, started, and completed states.
Messages, notifications, calendars, reports, and status history keep responsibilities and the next required action visible across organizations.
Design decisions
Why?Each organization gets its own navigation, tools and permissions.
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.
Why?One request record, from draft to completion, keeps decisions, edits and documents together.
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.
Why?Only ready vehicles and qualified drivers can be assigned, so bookings never conflict.
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.
How it's built
IntegrationsRole-Based Access ControlProduction Demo InitializationRender Deployment
Outcome
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.
