Back to workClient mandate2026

Medical transport platform

MediTransport

Medi Transport needed to organize a sensitive service: non-emergency medical transport. The platform gives each role the right tools without exposing more data than necessary.

Launching January 2027
One thread, five roles
6 portalsRole-based accessDesigned for older adults
Year
2026
Type
Client mandate
Stack
Next.js 16 · React 19 · Supabase
Status
Launching January 2027

On every screen

One codebase. Every screen.

These aren't screenshots. It's Medi Transport's homepage, rebuilt in code and rendered twice: at 1440 px in the laptop, at 390 px in the phone. The layout really reflows.

The lab

Drag the edge. Watch it reflow.

Drag the handle, or use the ruler with your keyboard.

1440 pxDesktop
localhost:3000
mMediTransportMenu

Accompanied medical transport · Montréal

We go with them,from the door to their care.

A caring driver picks up your loved one at the door, stays with them to their appointment and brings them home. You're kept informed at every step.

Book a ride +1 (438) 924-7988
390768102412801440

01Mandate

Replace scattered calls with a reliable system.

A trip often involves a patient, family, driver, dispatch team, and partner organization. The mandate required a clear interface for each viewpoint, with shared data and strict permissions.

02Experience

Each user sees only what they need.

Dispatch manages trips, drivers see their route and assignments, families follow useful trip information, and organizations keep a clear view of their requests.

Medical transport / Operations

A trip should not depend on a fragile chain of calls.

The platform turns a sensitive operation into a readable flow: request, validation, driver assignment, tracking, and communication.

  1. 01Create a transport request.
  2. 02Assign a driver.
  3. 03Track status by role.

03Product architecture

Six connected spaces around the same trip.

Administration, dispatch, driver, family, patient, and organization all read and write into the same system, with tailored flows for request, validation, assignment, tracking, notification, and history.

6

role portals

Admin, dispatch, driver, family, patient, and organization.

RBAC

role security

Each space exposes only the data and actions it needs.

Maps

field tracking

Geolocation, addresses, trips, and driver context.

Email

operations

Transactional notifications for requests, statuses, and coordination.

04Outcome

An operational platform ready for final launch steps.

The product brings together the foundations of a modern medical transport service: role-based portals, trip logic, security, operational tracking, maps, email, and dashboards.

01

Dispatch portal

Operational view for receiving, assigning, and tracking transport requests.

02

Driver workspace

Assignments, trip details, navigation, status, and mobile-friendly context.

03

Family/patient portal

Simple, reassuring tracking of essential medical-trip information.

04

Organization portal

Centralized requests for hospitals, clinics, or partners coordinating multiple patients.

05

Administration

Management for users, roles, requests, drivers, services, and settings.

06

"Le Fil" identity

A public site designed for older adults: glare-free warm paper, soft ink, large type, generous targets and reading settings, around a single continuous line drawing.

Next.js 16React 19SupabaseLeafletResendTailwind CSS

Measured

Measured, not promised.

Numbers you can check: the site's quality today, the history of its code, and what was done for people who read differently.

AQuality, today

—
Performance
—
Accessibility
—
Best practices
—
SEO

Not live yet: the scores will be measured here from launch day.

BThe build

wajditransportNext.js · Supabase · Leaflet
commits
0
working days
0
lines of code
0

Jun 7, 2026 → Oct 18, 2026

Commits per week

Six role portals and 68 pages, in 16 commits.

Read from git on Oct 21, 2026. Application code only: no tests, config or build output.

CAccessibility

  1. 01Reading preferencesLarger text and higher contrast, applied site-wide, remembered on the device and set before the first paint.
  2. 02No glareWarm bone paper and soft ink instead of white and black, for ageing or cataract-affected eyes.
  3. 03Secondary text near AAAAbout 7:1 on the paper: grey text stays readable without squinting.
  4. 0448-pixel targetsNavigation buttons and settings are 48 pixels: easy to hit with an unsteady hand.
  5. 05Colour never speaks aloneThe five services are told apart by name and icon first; colour comes second.

The budget

What the market charges for this scope.

$15,000 – $50,000

Closest tier
Client portal or web application
Accounts, roles, bookings and custom workflows: the market's “client portal or web application” tier.

A range published by third parties, not a Maison GR quote.

Estimate my project

→Maison GR

Building an operational service?

We structure multi-role platforms so operations stay readable, secure, and scalable.