1. The phased shape — Phases 1 and 2 are built and paid for now. Phases 3 and 4 need a separate approval. Confirm this is acceptable.
2. What the internal register actually holds — if the secretariat has mobiles, emails and GST numbers in an Excel or a ledger, Phase 1 shortens from months to weeks. We need to see it.
3. The re-registration mandate — will the committee instruct units to complete re-registration by a stated date? Without that push, the cleanup stalls and nothing above it works.
4. The official unit list — the current units, their boundaries, and their 2025-2027 office-bearers, so verification rights can be assigned correctly.
5. Fee heads and receipt series — which fees KETA collects today, who collects them, and what receipt numbering the auditor expects.
6. Payment collection — UPI-first collection into an account in KETA's name, and who reconciles it monthly.
7. Contact visibility policy — should any verified member see any other member's mobile number, or only after a requirement match? This is a member-sentiment call, not a technical one.
8. The existing website — does KETA Connect replace ketaonline.com or run alongside it? The present site is with another vendor, so the data handover route needs to be agreed by the committee, not by us.
9. Malayalam upkeep and sign-off — Malayalam script, a full Malayalam interface and transliterated typing are all in scope, not options. What needs deciding is who at KETA approves the Malayalam wording, and who reviews new strings as the platform grows. Translation is a standing job, not a one-time task.
10. Voice and search records — spoken Malayalam is converted to text by a third-party service, so search text leaves KETA's own servers. We propose no member name is ever attached to a search. The committee should approve that wording before launch.
11. Brand policy — which manufacturers KETA is willing to carry in the Brand Corner, at what rate, and who owns that relationship.
12. Day-to-day ownership — who in the secretariat runs the platform once it is live. A platform with no owner goes stale in one quarter.

Workflow approval signature

By signing below, the undersigned confirm that the workflow described in this walkthrough is a true representation of the process to be supported, and that the proposed roles, permissions, dashboards and reports are acceptable. Signing commits the workflow and the scope of Phases 1 and 2. Phases 3 and 4 remain subject to a separate approval. Dates will be added once the open items on slide 22 are settled.