Milestones

1. Platform foundation and delivery setup

Establish the shared project foundation: application architecture, core data model, environment/config handling, CI/CD, base API and web app structure, shared layout/navigation, and baseline error handling and browser support.

Scope:

• Overview
• Language
• Technical limitations
• Brand specifics
• About this document

Estimate: 8-12 man-days

2. Authentication, authorization, and user management

Integrate external authentication, implement sign in/out and password flows, protect routes and APIs, define role-based access, and build user CRUD with role assignment for the user-manager role.

Scope:

• Authentication/authorization
• User management
• User roles

Estimate: 8-12 man-days

3. Vehicle inventory

Deliver vehicle CRUD, search/filter/pagination, archive and delete rules, vehicle statuses, vehicle detail/edit screens, and booking history visibility needed by both Events and Fleet.

Scope:

• Vehicle Inventory List
• Add new vehicle
• Edit vehicle
• Vehicle detail

Estimate: 10-15 man-days

4. Fleet reservations and availability calendar

Build the fleet calendar, grouped vehicle availability view, reservation CRUD, conflict detection, prefilled booking flows from the calendar, and reservation validations tied to vehicle availability.

Scope:

• Calendar
• Managing reservations
• Vehicle Inventory List

Estimate: 10-15 man-days

5. Fleet pickup and return protocols

Implement the two-step pickup and return forms, draft persistence, signatures, attachments, PDF generation, protocol list/downloads, email sending, and protocol status transitions from draft to pickup to return.

Scope:

• Pickup form
• Return form
• List of pickup/return forms

Estimate: 15-20 man-days

6. Events core management

Deliver event list, create/edit/archive event flows, event detail, vehicle assignment to events, event metadata and questionnaires, and per-event invitee management including the main list/detail management surfaces.

Scope:

• Event management
• Events list
• Adding new event
• Event detail
• Invitee management
• Adding new invitee
• List of invitees on event
• Vehicle management

Estimate: 15-20 man-days

7. Events operational workflows

Implement QR-based invitee lookup, document signing, signed PDF availability with role restrictions, single- and dual-timestamp activity tracking, activity logs, and vehicle reassignment logic during overlapping test-drive activity flows.

Scope:

• Invitee detail
• QR Codes
• Document management
• Documents
• Document signing
• Activity management
• Activities tracking (single-timestamp activities)
• Activities tracking (dual-timestamp activities)

Estimate: 15-20 man-days

8. Cross-domain integrations, offline support, and hardening

Finish automatic event mailings, general invitee/document/activity lists where included in release scope, offline support for the documented event flows, sync/reconnect behavior, permissions hardening, QA, and production-readiness work.

Scope:

• Mailings
• Invitee list general
• General list of activities
• General list of documents
• Offline functionality
• Technical limitations

Estimate: 15-20 man-days