Workforce Management

Facility and District Portals for Transportation Requests

A secure portal for the organizations that request transportation from your operation. Hospitals, dialysis centers, and care facilities for NEMT. School districts coordinating across multiple schools. Transit agency contractors managing paratransit contracts. One portal, many organization types.

Trip Requests

Facility staff request trips directly — no phone calls, no transcription errors, no inbound call volume for your dispatch team

Trip Status

Real-time trip status visible to the requesting organization without exposing your dispatch console

Multi-tenant architecture

Multi-tenant architecture keeps each organization’s data scoped to their users with role-based permissions

What This Capability Does

Let Facilities and districts request transportation themselves

NEMT Cloud Dispatch provides a secure portal that facility staff and district users access directly. Hospital discharge planners book patient transportation at discharge time. Dialysis center coordinators schedule weekly recurring trips for their patients. School district transportation requesters book specialty trips for students with changing needs. School staff at individual schools submit transportation requests under their district’s account. Each user sees their own organization’s trips, books new trips within their authorization, and tracks status in real time.

Every inbound call to your dispatch center is work for your team. Booking a trip over the phone takes longer than booking it through a portal, introduces transcription errors, and creates demand on dispatch staff that scales linearly with your business. The facility and district portal changes this economics.

The multi-tenant architecture keeps everything properly scoped. A hospital user never sees another hospital's patients. A school user never sees another school's students. A district administrator sees all schools in their district. Role-based permissions control what each user can do — a district administrator may approve trips, while individual school users submit requests that go through approval.

For NEMT operators

Facility portal for hospitals, dialysis centers, and care facilities

NEMT operators typically serve multiple facility partners — hospitals for discharge transportation, dialysis centers for recurring treatments, skilled nursing facilities for outpatient appointments, home health agencies for patient visits. Each facility generates trip requests on its own schedule with its own staff. The facility portal gives each partner their own workflow without requiring your dispatch team to field their calls.

VoIP

Hospital discharge workflows are the highest-value use case. Discharge planners need reliable transportation for patients leaving the hospital — often on short notice, often with specialty requirements (wheelchair, oxygen, stretcher). The portal lets discharge staff book the trip at discharge time with all specialty requirements captured. The trip flows into your dispatch queue immediately. Status updates flow back so the hospital sees pickup, arrival, and drop-off in real time.

HIPAA compliance applies across every piece of this workflow. Each facility user authenticates individually. Patient data is scoped to the patients that facility is authorized to see. Audit logs capture every access. Business Associate Agreements are available for covered-entity partners.
For deeper NEMT facility portal capabilities, see our NEMT facility portal page

For school transportation

District and School Portal for School Transportation

School districts coordinate transportation across multiple schools they oversee. Each school has its own staff who know their own students' needs — a specialty transportation request for a student with a new IEP, a one-time change because of a custody arrangement, a field trip, an early dismissal. These requests come from the school staff, not from central district administration.

NEMT Cloud Dispatch provides a district-to-school portal hierarchy that matches this reality. The district creates user accounts for each school under their jurisdiction. School staff submit transportation requests under their school's account.

FERPA applies here. Each school sees only its own students. The district sees all schools. No cross-school visibility without explicit authorization. This matches FERPA's access model exactly.

For the full school transportation story, including district-to-school coordination, see our school transportation software page.
For Paratransit Operators

Agency portal for paratransit operations

Contracted paratransit operators often serve multiple public transit agencies. Each agency has its own rider population, its own subscription trip inventory, its own reporting cadence, and its own staff who interact with the transportation operation. An agency portal lets each agency interact with the operation through a scoped workflow.

Agency coordinators submit new rider enrollments, update subscription trip inventories, view service delivery in real time, and generate agency-specific reports — without calling the contractor's operations center. The contractor operates more efficiently. The agency has better visibility into its own service.

For in-house paratransit operations (agencies running paratransit directly), the same portal serves as the staff interface for eligibility coordinators, subscription managers, and rider services staff.

For the full paratransit story, see our paratransit software page.
Core Capabilities

Core facility and district portal capabilities

These capabilities apply across hospital, dialysis, care facility, school district, and transit agency portals:

Multi-tenant user architecture

Each facility, district, or agency gets its own user set, its own authentication, and its own data scope. No cross-tenant visibility without explicit authorization.

Role-based permissions

Within each tenant, roles control what each user can do. Requesters submit. Approvers approve. Administrators manage the user set. Permissions match the organization's internal workflow.

Trip request submission

Configurable request forms capture everything your dispatch team needs — rider information, specialty requirements, pickup and drop-off details, dates and times, notes. No phone calls, no transcription errors.

Real-time trip status

Requesters see trip status in real time — scheduled, driver assigned, en route, arrived at pickup, on board, dropped off, completed. Cuts 'where's my ride' calls from facility staff.

Recurring trip templates

Dialysis centers, school routes, and paratransit subscriptions set up recurring trips once. The system generates trip instances automatically.

Approval workflows

Configurable approval workflows — district administrator approves school requests, agency supervisor approves new enrollments, hospital manager approves specialty transportation.

Organization-specific reporting

Each facility or district sees reports scoped to their own trips. Service delivery, on-time performance, ridership, billing — all viewable per tenant.

HIPAA-compliant (NEMT and hospital)

Patient data handling meets HIPAA requirements. Business Associate Agreements available. Role-based access, audit logs, encryption in transit and at rest.

FERPA-aware (school)

Student data scoped per school. District administrators have districtwide view. No cross-school exposure without authorization. Matches FERPA access model.

Branding per tenant

White-labeled portal experiences available so facility staff see their own organization's branding alongside your transportation service.

Why operators choose Us

Why operators choose NEMT Cloud Dispatch for facility and district portals

Serves every kind of organization your operation works with

Hospitals, dialysis centers, SNFs, home health agencies, school districts, individual schools, transit agencies, contracted paratransit operators. One platform, one architecture.

Reduces dispatch call volume dramatically

Facilities and districts book, track, and coordinate transportation themselves. Inbound ‘where’s my ride’ and ‘what’s the ETA’ calls drop sharply after portal rollout.

Multi-tenant from day one

The data model was built for multi-tenant operation. You add new facility or district partners as contracts grow without reconfiguring the platform.

Compliant across regulatory frameworks

HIPAA for medical facilities. FERPA for schools. NTD-friendly for paratransit agencies. Compliance is baked in, not retrofitted.

Included in pricing

Facility and district portals are included at every tier. Add facility partners without increasing software cost — pricing scales by vehicle count, not by facility count.

Frequently Asked Questions

A transportation facility portal is a secure online workspace that lets hospitals, dialysis centers, care facilities, school districts, or transit agencies request transportation, track trip status, and manage their trips without calling the transportation operator’s dispatch center. NEMT Cloud Dispatch provides multi-tenant portals for every kind of organization that requests transportation.
Hospital discharge planners or transport coordinators log in with their individual credentials, fill out a configurable trip request form with patient info and specialty requirements, and submit. The trip enters the transportation operator’s dispatch queue immediately. Real-time status updates appear in the portal as the driver progresses.
Yes. That’s the intended architecture. The district creates user accounts for each school under its jurisdiction. School staff submit transportation requests under their school’s account. District administrators see all schools in one view. Each school sees only its own students and trips.
Yes. Patient data in the NEMT facility portal is handled according to HIPAA requirements. Role-based access, audit logs, encryption in transit and at rest. Business Associate Agreements are available for covered-entity partners.
Yes. Student data access is scoped per school. District administrators see districtwide; individual school users see only their building’s students. No cross-school visibility without explicit authorization. Matches FERPA’s access requirements.
Unlimited. Add as many partners as your business grows to serve. Each gets its own tenant with scoped data and users. Pricing is based on your vehicle count, not your partner count, so adding facility or district partners doesn’t increase software cost.
Yes. White-labeled experiences are available so facility staff see their own organization’s branding alongside your transportation service. Configuration is per-tenant so each facility partner can have its own branding.
Operators regularly report significant reductions in inbound ‘where’s my ride’ and ‘when is the patient being picked up’ calls after portal rollout. The exact reduction depends on how call-heavy the operation was before. Facility staff trade phone calls for self-service, and your dispatch team redeploys that time to exception handling.

See facility and district portals in action

The best way to evaluate portal workflows is to walk through them with your actual facility and district partners in mind. We'll set up demo tenants representing your hospital partners, dialysis centers, school districts, and agency contracts — and show you what their self-service experience would look like.

Prefer to talk first? Call (623) 226-8966 or [email protected]