A phased approach to solving yard map authoring and distribution across FedEx facilities — delivering an interactive driver portal in Q4 2026, with proximity-aware delivery and PWA install to follow.
Network 2.0 has expanded where linehaul drivers go — but hasn't given them the information they need when they arrive. Authoring is fragmented, distribution is broken, and the moment-of-need experience doesn't exist.
These came directly from the kickoff conversation and the FedEx requirements list
Phase 1 ships the full interactive driver portal — structured pin authoring, smart lookup, and a web experience drivers reach by QR. Phase 2 layers on the proximity-aware delivery: PWA install, geolocation, push on arrival, and deeper CMS capabilities.
| Capability | Phase 1 — Interactive Portal | Phase 2 — Proximity & PWA |
|---|---|---|
| Driver access | QR code → secured web portal | QR code + proximity push notifications |
| Map format | Interactive Google Map with custom pin layer | Same map, surfaced automatically on arrival |
| Find my map | Smart lookup (ZIP, alpha, numeric) + browser geolocation | Push notification on arrival at the facility |
| Authoring | Drag-and-drop pin authoring on Google Maps satellite layer | Bulk operations, expanded role model, change-history |
| Manager access | Single sign-on for TSPs / location managers | Same SSO, expanded role model |
| Map publishing | Real-time — live the moment they save, structured pins | Real-time with change-history & versioning |
| Distribution | Web — Safari / Chrome, no install | Progressive Web App (installable, no app store) |
| Target launch | Q4 2026 | Post-Phase 1, per facility |
Every requirement from the FedEx list is mapped to the phase that delivers it — and how.
| FedEx Requirement | Phase | How It's Delivered |
|---|---|---|
| Map creation by Linehaul / Station Manager | Phase 1 | Drag-and-drop pin authoring directly on a Google Maps satellite layer — no PowerPoint, no PDFs, no export step |
| Required map content: satellite image, entrance/exit, dispatch, fuel island, drop zone, dolly zone, trailers, restrooms, address, location rules (STA), directional flow | Phase 1 | Structured pin library covers every required element; satellite imagery is the native base layer |
| Interactive map with drag-and-drop pins | Phase 1 | Managers place structured pins (entrance/exit, dispatch, fuel island, drop zone, dolly zone, restrooms, trailers) directly on a satellite base layer |
| Driver-facing interactive map view | Phase 1 | Drivers tap any pin for details, directional flow, and location rules — zoom, pan, and follow-my-location supported on mobile |
| Interactive Google Maps integration with custom pin layer | Phase 1 | Google Maps satellite + roads base layer with a FedEx-specific overlay of structured pins |
| QR code distributed to drivers, scanned prior to arrival | Phase 1 | Single QR code resolves to the portal |
| Centralized URL where all maps are stored | Phase 1 | Secured web portal on Nishtech managed infrastructure |
| Single sign-on access for TSPs | Phase 1 | SSO on manager / authoring side |
| Centralized storage with per-location authoring by managers | Phase 1 | CMS scoped to each manager's assigned facility(ies) |
| Smart address lookup by ZIP, alpha code, or numeric code | Phase 1 | Unified search box accepting all three identifier types |
| Capability to store all FedEx locations | Phase 1 | Seeded from FedEx-supplied facility list (<1,000 US / Canada) |
| Driver access via website, QR code | Phase 1 | Web + QR; no native app required. PWA install added in Phase 2 |
| Real-time availability of map updates | Phase 1 | Pin edits go live immediately on save (optional approval step) |
| Auto pre-population based on location / geo-fencing (nice-to-have) | Phase 2 | Push notification when driver arrives at a registered facility |
| Push notifications on arrival to facility | Phase 2 | Geo-fenced trigger surfaces the correct yard map, STA, and gate procedures the moment the driver enters the facility perimeter — no scan required |
| Installable home-screen experience | Phase 2 | Progressive Web App — drivers install from the browser, no App Store or MDM friction |
| CMS enhancements (bulk operations, expanded roles, analytics) | Phase 2 | Bulk pin operations, expanded role model beyond per-facility scope, change-history and adoption analytics for the FedEx team |
| Rolling per-facility rollout of proximity features | Phase 2 | Facilities opt into proximity push and PWA enrichment as their fences are configured — Phase 1 interactive portal keeps working everywhere |
A native interactive map experience for drivers — structured pins, satellite imagery, and a drag-and-drop authoring CMS for managers. Target: Q4 2026.
Phase 2 isn't a replatform. The Phase 1 interactive portal keeps running for everyone — Phase 2 adds the proximity, install, and CMS-depth layer on top, rolled out facility by facility.
The two-phase structure isn't a hedge — it's the right architecture for what FedEx is trying to accomplish.
Dedicated. Multi-disciplinary. Blend of onshore/offshore talent to be cost effective and efficient
USA-led architecture, analysis, and design — paired with senior India-based engineering and QA for delivery velocity.
Phase 1 and Phase 2 are presented as separate line items — each can be approved independently. Figures below are estimates based on Nishtech's project scoping; final SOW pricing is subject to a joint discovery session.
These are the remaining unknowns. Resolving them — especially SSO — is what unlocks the Q4 2026 launch date.