DES-13 — Day 13 — Delegate app: visit, report, prospects, follow-ups
Visit and check-in, not-done reason, visit report, prospects list/map, follow-ups.
| Field | Details |
|---|---|
| Task code | DES-13 |
| Phase | P0 — Foundations (cadrage, UX/UI, architecture & contract) |
| Product scope | V1 |
| Status | Planned |
| Start | Wed 4 Nov 2026 |
| Due | Wed 4 Nov 2026 |
| Responsible | Akram — UI/UX designer |
| Co-responsible | — |
| Effort | 1 person-day(s) planned · 1.25 from scratch · size S |
| Area · app | Delegate app design · design |
| Depends on | DES-12 |
| Unblocks | MDA-04, MDA-05, MDA-06, DES-14 |
| Milestones | — |
Summary
Visit and check-in, not-done reason, visit report, prospects list/map, follow-ups.
Description
Day 13 designs a full visit that works offline and ends with a structured report that creates the follow-up. The screens are DA-10 visit and check-in, DA-11 visit not done, DA-12 visit report, DA-13 prospects and resellers (list/map) and DA-19 follow-ups. Inputs: the delegate-05-visit-checkin and delegate-09-visit-report references, the Day-5 visit-flow wireframe, cahier §6.4 and §6.8, FLD-08/09/10, CRM-04/08, ACL-03, GEO-03, and the operations delegate.visits.*, delegate.resellers.list, delegate.tasks.* and reference.lists. One correction to the reference: « Terminer la visite » is a normal completion and uses primary, not red. Consumers: Imad's MDA-04 (DA-13), MDA-05 (DA-10, DA-11) and MDA-06 (DA-12, DA-19).
Subtasks
| # | Subtask | Owner |
|---|---|---|
| 1 | DA-10 Détail de la visite, one primary action per VisitStatus: À visiter (arrive), Arrivé (« Commencer la visite », arrival time), En cours (live duration, checklist 0/5, quick note 0/300, photos, call, « Terminer la visite » in primary), Visité (read-only with lock note VISIT_LOCKED), Non réalisée (reason shown), Annulée | Akram |
| 2 | DA-10 rules: required photos per visit type (« Terminer » disabled with « 1 photo de façade requise »), photo states queued / sending / sent / failed, required checklist items, a required report routing to DA-12, offline with everything queued and the sync badge | Akram |
| 3 | DA-11 Visite non réalisée: required reason from VISIT_NOT_DONE_REASON, comment, optional photo, confirmation | Akram |
| 4 | DA-12 Rapport de visite: person met (name, role from PERSON_ROLE), interest Faible / Moyen / Élevé (tone segmented control), products and promotions presented (multi-select chips), issues (VISIT_ISSUE_TAG), comment, attachments | Akram |
| 5 | DA-12 next action: NextAction (Relance téléphonique, Nouvelle visite, Envoyer le catalogue, Message WhatsApp, Aucune) with follow-up date required unless Aucune; draft autosaved; confirmation « Relance planifiée le 29 mai » | Akram |
| 6 | DA-13 Prospects: list/map toggle, search, filters (ResellerStatus, potential, commune, follow-up due), distance sort, clusters, « Nouveau revendeur » → DA-14, delegate scope only, offline cache, empty and filtered-empty | Akram |
| 7 | DA-19 Relances: groups En retard (derived), Aujourd'hui, À venir; TaskType icons; complete; reschedule; open the point-of-sale sheet; empty « Aucune relance » | Akram |
| 8 | Annotate every report field with its reference list and every offline action with its outbox behaviour (client-generated UUIDv7, occurredAt) | Akram |
| 9 | Link the visit prototype DA-08 → DA-10 → DA-12 (and the DA-11 branch) | Akram |
| 10 | Feasibility: offline outbox for visits and reports, photo queue and compression, timer accuracy in background | Imad |
Deliverables
- Claude Design › Delegate App ›
DA · Visit(DA-10…12, DA-19) andDA · Prospects(DA-13) with every VisitStatus state - Linked visit prototype DA-08 → DA-10 → DA-12 with the not-done branch
- Field → reference-list annotation table for DA-11 and DA-12
Acceptance criteria
- Each VisitStatus has exactly one primary action, and finished visits are read-only
- The finish action is primary (not red) and is disabled with an explicit reason when required photos or items are missing
- Every report field names its reference list (PERSON_ROLE, VISIT_ISSUE_TAG, VISIT_NOT_DONE_REASON), and next action + date rules are shown
- Every frame has an offline variant or note, and nothing in the visit flow requires the network
- DA-13 shows only the delegate's scope (ACL-03)
- Imad's review answer is OK or OK with notes
Requirements covered
| Requirement | Title | Release |
|---|---|---|
| FLD-08 | Visit and check-in: time and position at check-in, duration, checklist, note, photos (mandatory by visit type), call; finished visit locked | V1 |
| FLD-09 | A visit not carried out requires a reason | V1 |
| FLD-10 | Structured visit report (person met, interest, products and promotions presented, issues, next action, follow-up date, attachments) that triggers the follow-up | V1 |
| CRM-08 | Follow-ups (relances), tasks and next actions with due dates and notifications | V1 |
Screens
| Screen | Name | App |
|---|---|---|
| DA-10 | Visit & check-in | DA |
| DA-11 | Visit not done — reason | DA |
| DA-12 | Visit report | DA |
| DA-13 | Prospects & resellers (list / map) | DA |
| DA-19 | Follow-ups & tasks | DA |
Test measures
- Visit prototype walkthrough with Imad, then timed: a full visit with report in under 3 minutes of taps
- 200 % text scale on DA-10 (visit must hold at 200 %)
- Check DA-12 against cahier §6.8 field by field
Risks
- The report is too long to fill at the counter — chips and defaults first, free text last; only person met, interest and next action are required.
KPI
- Delivered by Wed 4 Nov 2026 within 1 person-day(s).
- Every acceptance criterion above demonstrated before hand-off; linked requirements' acceptance criteria pass.
- Zero open critical defects, permission gaps or data-integrity regressions at sign-off.
Generated from content/plan/tasks.json by scripts/generate-team-tasks.mjs. Dates are computed by the scheduler (Sunday–Thursday weeks, holidays excluded) — change the plan, not this page.
DES-12 — Day 12 — Delegate app: tour programme, map & POS sheet
Tour programme (tabs, mini-map, ordered list), tours calendar, map and navigation, point-of-sale sheet.
DES-14 — Day 14 — Delegate app: sign-up, invitation, first order, closing
New reseller, edit, invitation, first-order assistance, assisted orders, tour closing, reports, messages, sync centre, system states.