System Requirements Document (SRD)

Project Name: mint-dashboard

1. Introduction

The mint-dashboard is a full-stack delivery management system designed to streamline logistics operations for businesses. It includes an Admin Dashboard (web application) and a Driver Portal (mobile-optimized app) to manage orders, optimize routes, track deliveries in real-time, and provide electronic proof of delivery (ePOD).

This document outlines the functional and non-functional requirements, user personas, visual design concepts, and technical specifications for the mint-dashboard project. The system is tailored for Christopher West's business needs in the UK, with locale-specific defaults such as GBP (£) currency, UK time zones, and address formatting.

2. System Overview

The mint-dashboard system consists of two main components:

1. Admin Dashboard: A web-based application for managing orders, creating optimized delivery routes, tracking driver progress, and monitoring delivery statuses.
2. Driver Portal: A mobile-optimized application for drivers to view assigned routes, navigate stops, capture ePOD, and update delivery statuses in real-time.

The system supports:

• Order entry and management
• Route creation and optimization using APIs (e.g., Google Maps, Mapbox, OpenRouteService)
• Real-time GPS tracking of drivers
• Electronic Proof of Delivery (ePOD) with photo, signature, and timestamp capture
• Customer notifications via SMS and email
• Live status updates for admins and customers
• Advanced features such as route re-optimization, failed delivery logging, live customer tracking, delivery time window management, and analytics dashboards.

3. Functional Requirements

Admin Dashboard

• As Admin, I should be able to input and manage orders with details such as order number, business name, delivery address, contact information, line items, and delivery status.
• As Admin, I should be able to search, edit, and filter orders in a table view.
• As Admin, I should be able to create optimized delivery routes by selecting pending orders and assigning them to drivers.
• As Admin, I should be able to view live driver locations on a map, including current, completed, and remaining stops.
• As Admin, I should be able to click on a stop to view delivery details and ePOD information.
• As Admin, I should be able to receive real-time updates when a driver changes stop status or uploads ePOD.
• As Admin, I should be able to re-optimize routes mid-route if needed.
• As Admin, I should be able to log failed delivery reasons for each stop.
• As Admin, I should be able to generate and view analytics dashboards for delivery performance, on-time rates, and other key metrics.

Driver Portal

• As Driver, I should be able to log in and view my assigned route, including total stops, distance, estimated duration, and a map view.
• As Driver, I should be able to start my route, enabling GPS tracking and location updates every 10–20 seconds.
• As Driver, I should be able to view stop-by-stop navigation details, including business name, address, contact details, delivery items, and special notes.
• As Driver, I should be able to capture ePOD by taking a photo, collecting a signature, and confirming delivered quantities.
• As Driver, I should be able to mark a stop as complete, triggering an automatic update to the admin dashboard and customer notifications.
• As Driver, I should be able to log failed delivery reasons (e.g., customer unavailable, incorrect address).

Real-Time Features

• As Admin, I should see real-time updates on the dashboard when drivers update stop statuses or upload ePOD.
• As Customer, I should receive instant SMS/email notifications with delivery confirmation, timestamp, and ePOD details.
• As Customer, I should be able to track my delivery live via a tracking link.

System Settings

• As Admin, I should be able to configure depot address, manage drivers, set notification preferences, upload company branding, and define delivery time windows for orders.

4. User Personas

1. Admin:

   • Role: Logistics manager responsible for overseeing delivery operations.
   • Goals: Efficiently manage orders, optimize routes, monitor delivery progress, and analyze performance metrics.
   • Needs: A clean, intuitive dashboard with real-time updates, robust search/filter capabilities, and advanced analytics.

2. Driver:

   • Role: Delivery personnel executing assigned routes.
   • Goals: Complete deliveries efficiently and accurately while providing ePOD.
   • Needs: A simple, mobile-friendly app with clear navigation, offline functionality, and the ability to log delivery issues.

3. Customer:

   • Role: Recipient of deliveries.
   • Goals: Receive accurate delivery updates and confirmations.
   • Needs: Timely notifications with proof of delivery and live tracking of their delivery.

5. Visuals Colors and Theme

The mint-dashboard will feature a professional and modern logistics-style UI with the following color scheme:

• Primary Color: Mint Green (#3EB489) – Represents freshness and efficiency.
• Secondary Color: Navy Blue (#1A237E) – Conveys trust and reliability.
• Accent Color: Light Grey (#F5F5F5) – For clean and minimal backgrounds.
• Text Color: Dark Charcoal (#333333) – For readability.

The design will prioritize clarity and usability, with a focus on map-based interfaces and table views for the admin dashboard and large, touch-friendly buttons for the driver portal.

6. Signature Design Concept

Interactive Route Map with Dynamic Animations and Live Customer Tracking
The homepage of the admin dashboard will feature a live, interactive map as its centerpiece. This map will display all active routes, driver locations, and delivery statuses in real-time.

• Dynamic Animations:

  • Routes will animate as they are created, with a glowing path tracing the optimized delivery route.
  • Driver icons will move smoothly along the route, updating every 10 seconds to reflect real-time GPS data.
  • Completed stops will fade out with a subtle checkmark animation, while pending stops will pulse gently to indicate action is needed.

• Micro-Interactions:

  • Hovering over a stop will display a pop-up card with delivery details and ePOD status.
  • Clicking on a driver icon will zoom into their route and display a progress bar.

• Customer Live Tracking:

  • Customers will receive a live tracking link that opens a simplified version of the map, showing the driver’s current location and estimated arrival time.

• Color Shifts:

  • The map background will subtly shift from light to dark based on the time of day, creating a visually engaging experience.

This bold, interactive design will make the admin dashboard not only functional but also visually captivating, leaving a lasting impression on users.

7. Non-Functional Requirements

• Performance: The system must handle up to 1,000 concurrent users with minimal latency.
• Scalability: The architecture should support future expansion, including additional features and increased user load.
• Security: Implement role-based authentication and secure data storage for sensitive information.
• Availability: Ensure 99.9% uptime with robust error handling and recovery mechanisms.
• Localization: Support UK-specific settings, including GBP currency, time zones, and address formatting.

8. Tech Stack

Frontend

• Admin Dashboard: React with Next.js
• Driver Portal: React Native or Flutter

Backend

• Python with FastAPI OR Node.js with Express OR Supabase backend

Database

• Primary: PostgreSQL
• Migrations: Alembic

Integrations

• Google Maps API, Mapbox, or OpenRouteService (Routing + Geocoding)
• Twilio (SMS)
• SendGrid (Email)
• Cloud storage for ePOD images

Real-Time Features

• Firebase, Supabase, or WebSockets for real-time sync

Deployment

• Docker and Kubernetes for containerization and orchestration
• Hosted on AWS, Vercel, or Supabase

9. Assumptions and Constraints

• The system will primarily serve businesses in the UK.
• Drivers will have access to smartphones with GPS capabilities.
• Internet connectivity may be intermittent; the driver app must support offline mode.
• Route optimization will rely on third-party APIs, which may have usage limits.

10. Glossary

• ePOD: Electronic Proof of Delivery, including photo, signature, and timestamp.
• Route Optimization API: A service that calculates the most efficient delivery route.
• Depot: The starting and ending location for delivery routes.
• Real-Time Sync: Instant updates between the driver app and admin dashboard.
• Live Tracking Link: A URL provided to customers to track their delivery in real-time.

This document provides a comprehensive foundation for the development of the mint-dashboard. Let’s bring this vision to life, Christopher! 🚀