Bridgr — the spec

A two-sided marketplace where newcomers who lack a bilingual support network can find, book, and pay a vetted in-person interpreter for a specific appointment — medical, legal, housing, immigration, or otherwise — within hours or days of that appointment. Interpreters list their languages, credentials, and availability; users filter and confirm a booking without any manual coordination.

---

Decisions locked

---

The core loop

1. A newcomer creates an account, enters their appointment details (date, time, location, appointment type), and uploads any relevant context documents.
2. They filter available interpreters by language pair and availability window; the system returns only interpreters whose calendar matches.
3. The user selects an interpreter, reviews their credentials and rate, and pays securely at the point of booking.
4. Both parties receive a confirmation via email or SMS with appointment details.
5. If plans change, the user cancels or rebooks under the stated policy — no penalty within the allowed window — and payment is handled automatically.
6. The interpreter attends the appointment; the user receives an invoice receipt post-booking.

---

v1 scope

Language and Availability Filtering
A search interface on the Browse screen that filters the interpreter pool by target language and a specific date/time window, returning only interpreters with confirmed availability. No results shown for slots already booked.

Secure Payment and Invoice Generation
Stripe-powered checkout on the Booking Confirmation screen. On completion, an itemised invoice is emailed to the user automatically — no manual step required.

Interpreter Credential Verification
A verification workflow in the Interpreter Onboarding flow: background check consent, credential document upload, and an admin approval gate before the interpreter profile goes live. A visible badge appears on each approved profile.

Cancellation and Penalty-Free Rebooking
A policy engine attached to every booking that allows cancellation or rebooking within a defined window at no charge. Edge cases outside that window trigger a clearly stated partial-refund rule. Managed from the user's Booking Dashboard.

Appointment Context and Document Upload
A pre-appointment panel on the Booking Detail screen where the user can upload documents (referral letters, forms, case numbers) and add freetext context notes. The assigned interpreter sees this panel before the appointment.

---

Deliberately later

• Real-time location tracking and ETA updates — requires interpreter mobile app infrastructure; builds correctly once core bookings are stable and volume justifies the build cost.
• In-app call/messaging during appointment wait — communications compliance (especially for medical and legal contexts) needs legal review before it ships.
• Post-appointment summary and note-taking — valuable, but depends on understanding how users actually debrief after appointments; better designed from real usage data.

---

Data model sketch

• users — id, name, email, phone, preferred\_language, created\_at
• interpreters — id, user\_id, languages, hourly\_rate, credential\_docs, verification\_status, background\_check\_status
• availability_slots — id, interpreter\_id, start\_at, end\_at, is\_booked
• bookings — id, user\_id, interpreter\_id, slot\_id, appointment\_type, location, status, cancellation\_window\_end
• documents — id, booking\_id, uploader\_id, file\_url, context\_notes, uploaded\_at
• payments — id, booking\_id, amount, currency, stripe\_payment\_intent\_id, status, invoice\_url
• cancellations — id, booking\_id, requested\_at, reason, refund\_amount, penalty\_applied

---

Screens

• Home / Search — entry point; language and date/time filters surface available interpreters instantly.
• Interpreter Profile — credential badge, languages, rate, reviews, and available slots.
• Booking Confirmation — appointment detail summary, document upload, and Stripe checkout.
• Booking Dashboard (user) — all upcoming and past bookings; cancellation and rebooking controls.
• Interpreter Dashboard — upcoming confirmed appointments, document/context panel per booking, earnings summary.
• Onboarding Flow (interpreter) — credential upload, background check consent, rate setting, availability calendar setup.
• Admin Verification Queue — internal screen to approve or reject interpreter applications before profiles go live.

---

How to use this document

• Bring it into Mind Palace, where the guided platform and its AI coach pick up from exactly this document and build the product with you step by step.
• Hand it to a developer as the complete v1 brief — scope, data model, and screen list are ready to act on without further discovery.
• Keep it as the single source of truth to resolve scope debates: if a feature is not in v1 scope, it is in "Deliberately later" for a documented reason.