← QuranFlow — the redesign← The flow map

Open questions for Lejla

Twelve questions that came out of building the flow map from our July 24 discussion. We went through them first: four we believe are already answered — they just need your confirmation — and eight carry a proposed default we'll design to unless you correct it.

How to reply: right in the Slack thread under the flow-map post in #product-quranflow. Because every question has a proposed answer, “defaults fine except #4 and #10” is a complete reply — only write more where we got it wrong.
Answered — confirm Default proposed — correct if wrong

New students & placement

01How is the first assessment conducted?
Default proposed

A live 1:1, booked through the same slot-grid as regular appointments and held on the existing live-session screen. The coach grades against the First Assessment rubric that already exists in the data model. No new screens beyond booking.

Correct us if it's a recorded recitation instead, or held off-app (Zoom).

02How long does placement take after the assessment, and what should the waiting state show?
Default proposed

Placement result within 48 hours of the assessment — the same promise the app already makes for coach feedback. While waiting, the student sees only their assessment date and a short “what happens next” — no lessons, no recording.

03Can a brand-new student be placed directly into Year 2?
Default proposed

No. Year 2 means returning; a new student always places into a Year-1 level.

04After web checkout, what exactly does the student receive?
Default proposed

An email with the app download link and a magic sign-in link (passwordless), with set-a-password as the fallback. This decides what the new Sign-in screen must handle.

Year 2

05Appointment frequency — hard cap, recommendation, or tuition-dependent?
Default proposed

Included in tuition with a soft cap of 3 per week; one per week is the baseline rhythm. The UI shows the next appointment plus “Book another” until the cap. (From our call: “2–3 per week.”)

06Do Year-2 students keep any recording / submission ability?
Default proposed

No — removed entirely in v1. Today — Year 2 has no record button. We'd only revisit if TAs want short pre-appointment recitation clips.

07What happens when a student misses an appointment?
Answered — confirm

The data model already defines this: cancellation is guilt-free up to the last minute (frees the slot, no penalty); a no-show is joining under 75% of the session or not at all; two consecutive no-shows auto-escalate by email to program staff. No in-app progress penalty.

Just confirm this carries unchanged to Year-2 multi-TA bookings.

08Do Year-2 students follow the same weekly lessons as Year 1?
Answered — confirm

From our call: same lessons for everyone — the feedback format is the only difference. The map's shared-lessons band is built on this.

Returning students

09Are ALL returning students auto-placed into Year 2?
Answered — confirm

From our call: returning students are auto-placed into Year 2. For the edge case — repeating Year 1 or requesting re-assessment — our default is that staff handle it off-app in v1; no in-app flow.

10What happens after week 15 — and how does a Year-1 student become Year 2?
Default proposed

Today shows a semester-complete state; re-enrollment happens on the web like all sales; the app flips the account's status once the new semester is purchased.

This is the default we're least sure of — worth a real answer.

Coach / TA

11Do the same TAs handle Year-1 submission reviews and Year-2 appointments?
Default proposed

One pool. The role-gated coach section shows both the review queue and the schedule; a coach who only does one kind simply has an empty other queue. The shared student record (visible to all coaches) already supports rotation.

12Is there an approval step before the appointment summary reaches the student?
Answered — confirm

The designed flow is record → transcribe → auto-summary → the TA edits → send. The TA's edit is the approval — no second approver.