Prototype
Assumptions & open decisions
Every traveller, agency, guide and document in this build is fictional. The prototype is intended to make the product decisions visible and discussable before further phases.
Scope
What Phase 1 shows
- The traveller experience end to end: Today, Journey, Assistance, Documents and More.
- One central trip record shared by travellers, advisors and the Fayed Travel team.
- Role-based demonstrations during private development only — removed from every public build.
- Real sign-in accounts and real database permission rules behind the traveller experience.
Deliberately deferred
Not in this prototype
- Live flight tracking, payments and invoicing.
- Guide and driver applications — placeholders only in the data model.
- Photo attachments on assistance requests and offline document downloads (MVP).
- Advisor multi-factor authentication and staff single sign-on (later phase).
Privacy
How information is separated
- Travellers see only their own trip and only items released to them.
- Advisors see their own agency's trips — never internal operations notes.
- Medical notes are held by Fayed Travel and never shown to agencies.
- Location is shared only when a traveller chooses to share it, and expires.
Open questions
Decisions for Fayed Travel
- Which itinerary changes should notify the advisor automatically?
- How long should documents stay available after a journey ends?
- Should travellers see guide and driver names before the day of service?
- What rating threshold should escalate to a service recovery case?