Skip to main content

§ masterplan.md

Clean Logistics Platform

A corporate logistics dashboard landing with shipment tracking, rate calculator and partner onboarding form.

All ideas
Clean Corporate

01

App overview and objectives

A shipment tracking and fleet coordination platform: live vehicle positions, delivery status per stop, route optimisation and a customer-facing tracking link.

02

The problem worth solving

Most small logistics operators run on phone calls and spreadsheets. Replacing 'where is my delivery' calls with a live link saves dispatcher hours every single day.

03

Target audience

  • Primary — Dispatchers and operations managers at small and mid-size fleets.
  • Secondary — Drivers on the road and end customers awaiting a delivery.

04

Roles and permissions

  • Visitor — read-only public pages, can sign up.
  • Member — owns their own records, cannot see other users' data.

05

Core features

  • Live map of vehicles with status and estimated arrival
  • Shipment records with stops, proof of delivery and exceptions
  • Route planning and optimisation for a day's stops
  • Driver mobile view: next stop, navigation handoff, capture proof
  • Public tracking link per shipment, no login required
  • Operational reports: on-time rate, distance, exceptions by cause

Deliberately later

  • Cold-chain and temperature monitoring
  • Customer booking portal
  • Carrier marketplace

06

Technical stack

React dashboard with a map library, Postgres with geospatial support, websockets for live positions, a routing engine service.

Why: Geospatial queries and route optimisation are specialised — use a proven routing service and store positions in a database built for geometry.

Alternatives: Telematics vendor dashboards (turnkey, no customisation) or building routing in-house (differentiating, months of work).

07

Conceptual data model

Vehicle — fleet, registration, type, capacity, current position

Driver — name, licence, assigned vehicle, shift

Shipment — customer, origin, destination, items, service level, status

Stop — shipment, sequence, address, window, arrival, proof

RoutePlan — date, vehicle, ordered stops, distance, duration

Exception — stop, type, note, photo, resolved

08

Integrations

  • Map tiles and geocoding
  • Routing and matrix API
  • SMS or push for customer notifications
  • Telematics devices

09

UI design principles

  • Predictable structure, strong trust signals, consistent 8px spacing rhythm.
  • Restrained brand colour on actions only; neutral surfaces everywhere else.
  • Fast, accessible, and boring in the best way — nothing gets in the user's path.

10

Security considerations

  • Driver location is personal data: collect only during shifts, state the policy, and retain for a limited window.
  • Public tracking links expose only status and estimated arrival — never the customer list or driver identity.
  • Role separation between dispatcher, driver and administrator.

11

Development phases

Phase 1 — Prove the core

  • — Live map of vehicles with status and estimated arrival
  • — Shipment records with stops, proof of delivery and exceptions
  • — Route planning and optimisation for a day's stops
  • — Static content and design system in place
  • — Basic analytics

Phase 2 — Make it real

  • — Driver mobile view: next stop, navigation handoff, capture proof
  • — Public tracking link per shipment, no login required
  • — Operational reports: on-time rate, distance, exceptions by cause
  • — Accounts, sign-in and password reset
  • — Empty, loading and error states everywhere

Phase 3 — Polish and launch

  • — Performance, accessibility and SEO pass
  • — Legal pages, contact route and 404 handling
  • — Wire up: Map tiles and geocoding
  • — Wire up: Routing and matrix API

Phase 4 — Grow

  • — Cold-chain and temperature monitoring
  • — Customer booking portal
  • — Carrier marketplace

12

Challenges and solutions

Risk — Poor connectivity on rural routes

Solution — Offline-first driver view that queues proof-of-delivery uploads and syncs when signal returns.

Risk — Route optimisation cost per request

Solution — Optimise once per day per vehicle and re-optimise only when a stop materially changes.

Risk — Driver resistance to tracking

Solution — Shift-bounded tracking, transparent policy, and features that genuinely help drivers such as navigation and paperwork removal.

13

Future expansion

  • Predictive delay alerts
  • Fuel and maintenance management
  • Multi-tenant carrier network

14

Page list (13 pages)

  1. 01 APP (signed in) Dashboard — Today's operations at a glance.
  2. 02 APP (signed in) Tracking — Live map and shipment status.
  3. 03 PUBLIC Fleet — Vehicles, drivers and assignments.
  4. 04 PUBLIC Routes — Planning and optimisation.
  5. 05 PUBLIC Reports — Performance and exceptions.
  6. 06 AUTH Sign up — Create an account with email or a social provider.
  7. 07 AUTH Log in — Return to the account, with error and lockout states.
  8. 08 AUTH Reset password — Request a reset link and set a new password.
  9. 09 APP (signed in) Account settings — Profile, email, password, language and delete account.
  10. 10 PUBLIC Contact — Contact form plus real address, phone and email.
  11. 11 LEGAL & SYSTEM Privacy policy — What data is collected, why, and how to remove it.
  12. 12 LEGAL & SYSTEM Terms of service — Rules of use, liability and account termination.
  13. 13 LEGAL & SYSTEM 404 not found — Friendly dead end with search and links back.

15

Page map

PUBLIC      AUTH               APP (signed in)      LEGAL & SYSTEM
──────────  ─────────────────  ───────────────────  ───────────────────
├─ Fleet    ├─ Sign up         ├─ Dashboard         ├─ Privacy policy
├─ Routes   ├─ Log in          ├─ Tracking          ├─ Terms of service
├─ Reports  └─ Reset password  └─ Account settings  └─ 404 not found
└─ Contact

key flows:
  Dashboard ──▶ Tracking
  Fleet ──▶ Routes
  Routes ──▶ Tracking
  Tracking ──▶ Reports