Pilot build plan

Build the Masjid Ayesha pilot as a service we can safely run, not just a booking app.

SalahGo needs rider booking, mosque team coordination, safeguarding, scheduling, volunteer eligibility, sponsorship and impact reporting to work together. The pilot should prove one mosque and one route before adding more hubs.

Qur'an 2:148 - compete with one another in good works.

Pilot specification

Masjid Ayesha Loop

One mosque, one vehicle, one scheduled route, one Friday pilot timetable. The area is Tottenham / Seven Sisters / Tottenham Hale / Manor House / West Green Road.

  • Jumu'ah transport
  • Daily prayer windows where demand is proven
  • Madrasa booking option
  • Sisters' circles and community events
  • Elderly and accessible journeys
  • New Muslim welcome journeys
1

Seven Sisters Station

Rail and Underground interchange

Simple pickup point for people arriving by public transport.

2

Tottenham Hale Station

Victoria line, rail and bus hub

Useful for wider Tottenham and commuters heading to mosque activities.

3

Manor House

North route anchor

Connects people who find direct mosque parking or walking difficult.

4

West Green Road

Community corridor

Supports families, elderly members and local high-street access.

5

Masjid Ayesha

Pilot hub

Arrival, prayer, activity attendance and return loop.

What needs building

What we build next

Rider App

Member profile, mosque selection, prayers, madrasa, classes, events, collection preference, accessibility needs and booking confirmation.

MVP: Make madrasa journeys a normal booking choice, with extra guardian and handover details.

Mosque Team View

Masjid coordinator view for members, stops, route windows, sponsor seats, Friday runs and safeguarding notes.

MVP: Build one Masjid Ayesha team view before adding more mosques.

Route And Timetable

Fixed loops, collection windows, return trips, capacity rules and no last-minute taxi-like dispatch.

MVP: Start with the Masjid Ayesha Loop: Seven Sisters, Tottenham Hale, Manor House, West Green Road and the mosque.

Safety And Safeguarding

Named handover contacts, DBS status, consent, audit logs, driver eligibility, escort rules and minibus-permit assumptions.

MVP: Record every sensitive decision before carrying real passengers; licence assumptions must be checked against GOV.UK and insurer rules.

Payments And Sponsorship

Membership passes, Friday sponsorship, gifted seats, payment history and restricted community funds.

MVP: Use Stripe later; keep a clear sponsored-seat record now.

Driver And Escort View

Volunteer/driver shift view, route manifest, rider notes, handover confirmation, accessibility needs and incident reporting.

MVP: Keep driver tools narrow and safe: today's route, eligibility check, rider notes and completion logs.

Community Impact

Attendance enabled, sponsored seats used, missed-journey reasons, accessibility demand and pilot evidence.

MVP: Measure participation and access, not just miles driven.

Governance

CIC asset lock, mosque partner agreements, role permissions, spending approvals and data-retention controls.

MVP: Separate public promises, service records and founder/private business assumptions.

App scope

Features to show in the launch app

Pilot

Masjid Ayesha Hub

Home screen shows prayer times, madrasa, sisters' circles, elderly programmes, seminars and transport availability.

Pilot

Prayer and Event Booking

Users choose mosque, prayer, class, event or family/community activity before selecting a pickup point.

Enabled option

Madrasa Journey

Madrasa journeys are selectable in the app with guardian, handover and safeguarding fields.

Pilot

Accessibility Needs

Wheelchair space, step-free boarding, elderly support, companion seat and anxiety/support notes are captured before route assignment.

Operational check

Volunteer Driver Eligibility

Driver view records age, licence, medical, vehicle and permit assumptions before assigning a run.

Pilot

Sponsor A Seat

Community members can sponsor journeys, memberships and accessibility transport without seeing rider data.

Volunteer-friendly vehicle route

Some volunteer minibus routes may be possible without every driver holding D1, but only when the vehicle, payment, insurance and permit rules fit official guidance. We will check this with the insurer and qualified transport advice before carrying passengers.

Progress checklist

Where we are now

Prototype Hub

Done

The uploaded SalahGo site, rider app and Masjid Ayesha pitch deck are served from the Next app.

  • Keep the overview, public site, rider app and build plan pages demo-ready.
  • Use `scripts/start-salahgo-dev.cmd` for local review on port 3001.
  • Treat the HTML prototypes as reference material while replacing them with native React flows.

Rider Booking Flow

Next

Convert the phone prototype into real screens with a typed booking model before adding persistence.

  • Define rider profile, mosque, prayer window, pickup preference, accessibility need and handover contact types.
  • Build native React screens for mosque selection, trip request, confirmation and journey status.
  • Add empty, loading and validation states so the app can be tested before auth is wired.

Masjid Ayesha Hub

Next

Create the first mosque coordinator console around members, trips and Friday route preparation.

  • Add a mosque team route for members, upcoming prayer windows, route capacity and sponsor-seat usage.
  • Model manual stop assignment first; route automation can come after real pilot patterns are known.
  • Keep Masjid Ayesha as the single pilot hub until the process is stable.
  • Show madrasa transport as an active selectable service option with extra safeguarding fields.

Safeguarding Gate

Blocked

Real passenger operations need qualified review before sensitive data or live journeys are handled.

  • Confirm permit route, insurance, DBS requirements, safeguarding policy and member consent wording.
  • Check the GOV.UK car-licence/minibus and minibus-permit route against the intended vehicle, fares, volunteers and insurer position.
  • Decide what records are mandatory for handover, incident and driver eligibility events.
  • Lock public copy away from unconfirmed legal, pricing and operating assumptions.

Pilot Backend

Next

After the React flow is real, add storage for members, bookings, route windows and safety records.

  • Add database tables for mosques, members, prayer windows, bookings, stops, route runs and safety records.
  • Wire auth roles for rider, mosque coordinator, driver/escort and admin.
  • Delay Stripe until membership and sponsorship wording has been legally checked.

Service boundaries

Non-negotiables before launch

1

Membership-first, scheduled transport. It must not behave like an instant taxi service.

2

One mosque, one route, one vehicle and one timetable before wider London expansion.

3

The mosque is the hub. SalahGo supplies the app, route planning and support.

4

Accessibility is central: elderly, disabled, sisters, vulnerable riders and children are first-class users.

5

Madrasa journeys are a normal service option, with guardian and handover checks.

6

Safety and safeguarding are part of every journey, not an afterthought.

7

Keep public wording simple. Keep legal, pricing and operating assumptions in private documents until confirmed.

Delivery plan

Practical sequence

Stage 1

Prototype Hub

Serve the uploaded public site, rider app and pitch deck through Next routes for demos.

Stage 2

Real React Flows

Replace iframe prototypes with reusable React screens for prayers, events, madrasa journeys, accessibility and sponsorship.

Stage 3

Pilot Backend

Add auth, member profiles, mosque hubs, bookings, stops, handover contacts and audit logs.

Stage 4

Payments And Sponsorship

Wire memberships, sponsored seats and Friday sponsorship once legal and policy wording is final.

Stage 5

Live Pilot

Run Masjid Ayesha as the first hub with one route, one vehicle, mosque team view, route list and impact reporting.