Decisions

Developers manage form config via Frappe Doctype. No client-facing survey builder.

Why: Faster turnaround; prevents client-side errors. Excel form-design template stays SoT.

Owner: Dev team Actions: A20, A19

Hidden member-ID question carried forward to child forms; app-layer prefill of member geography (not data layer). Different scoping rules per program.

Why: P1 + P2 root cause. App-layer keeps form definitions clean.

Owner: Dev team Actions: A11

Replace mForm self-linking with Frappe-native audit log on the original record.

Why: P4. History preserved without new response rows.

Owner: Dev team Actions: A4, A23

New scalable home screen — member search + 'today/this week/overdue' follow-up buckets + colour coding + push notifications.

Why: P3 + P6.

Owner: Abhijit + Fahimuddin Actions: A7

Drop Superset. Build custom dashboard (Frappe Insights / custom Next.js with AI-assisted chart spec).

Why: Bespoke per project; cheaper iteration cadence.

Owner: Dev team Actions: A8, A13

Replace 'load more / append' with paginated view (1/2/3...100 per page, configurable).

Why: Existing append model breaks at 5L+ records.

Owner: Dev team

Use the Reliance route / SDK approach already proven for V3.

Why: Faster bring-up; rel-mis already paid for the rough edges.

Owner: Sunandan / dev team

Support English, Kannada, Telugu (confirm count with Swasti). Plan multi-language properly — Frappe view-vs-data split is different from mForm.

Why: P7. Confirmed via PM sheet only English present today.

Owner: Abhijit Actions: A5, A6

Stay with the simple NCD-style screening for current scope. Pitch TDH model + gamification for future.

Why: Tight deadline; ambition deferrable.

Owner: Abhijit (pitch)

Dedicated QA PC + AI-driven regression on every APK. Sachin focuses on new-feature first-run tests. Frappe web tests via Playwright.

Why: P8 unblocker.

Owner: Sachin + dev team Actions: A10

Use existing HRMS-linked internal ticketing tool for project / dev work tracking.

Why: Already live; no new system to onboard.

Owner: Already live

Publish Frappe Desk KB for Swasti — bulk upload, user/form management, mobile user guide. Same pattern as Adani.

Why: Reduces support load.

Owner: Abhijit Actions: A12

Geography, user allocation, basic admin = available out of box. Form modification & bulk upload — handled per project, custom-built only for big clients with strong need. We do NOT rebuild mForm-the-product inside Swasti.

Why: Avoids feature-creep into building a new mForm.

Owner: Dev team

Maintain a single source-of-truth doc per project: context + flows + forms + logic + decisions. Excel form-design template + Reliance reference example shared with PM.

Why: Avoids context loss across handoffs.

Owner: Abhijit Actions: A1, A9