UX redesign: Field force, sales CRM & claims

Part of the UX gap analysis. Places, patterns and treatments follow the IA & principles. Spryple facts come from the crawled Help Center; click counts are estimates (see evidence).

5. Field Force, Sales CRM & Claims

Scope: CRM / Field force (web and mobile) and Claims (web and mobile). Spryple facts come from the Help Center extracts in 05-screens-by-module.md, 04-workflows.md (I1–I11, G1–G4, J8) and spryple-analysis.md §21.6, §21.7, §21.11. Anything not in those sources is marked "not documented". Click counts are documented-actions estimates (Spryple) against redesign estimates (ours), per the method in 00-ia-and-principles.md §5. Related requirements: FR-FFM-001…017 (PRD §7.14), FR-CLM-001…014 (PRD §7.11).

5.1 UX issues found

ID	Issue (pattern)	Evidence	Pros	Cons	How we handle it (place · pattern · principle)
UX-FFM-01	Two parallel status systems. Demo Status (Leads, Call for Demo, Demo Pending, Demo Completed, Future Leads) and Client Status (Interested, Follow-up, Won, Lost, Not Interested) each have a master and a board, switched by a dropdown.	I3 steps 2–3; I1 (Demo Status and Status Master are separate masters); a client whose status is not Call for Demo, Demo Pending or Demo Completed jumps to "Future Leads" (I3).	Demo progress and deal outcome are both captured. Two masters allow different vocabularies per team.	Users must remember which board answers which question. "Future Leads" is a side effect of a status choice, not a decision. Two masters to keep in sync.	P-FIELD › Pipeline board and P-SET › Masters › Pipeline stages · PAT-6 (board) · UXP-8, UXP-2. One stage master; Won/Lost are outcomes with a reason; Demo is an activity type, not a second board (FR-FFM-008).
UX-FFM-02	Punch, client, activity and payment are separate tabs, not one visit flow. Punch has its own camera screen, Add Client another photo, Activity Dashboard, Add Activity, Client Details, Client Associates and Client Payments are all separate screens.	I8: 16 documented actions for punch, client and activity; I3: 17 actions web; I5, I6 add 3 each.	Each screen is simple and has one job. Image-only activity is possible (I8 step 4).	Four photo or capture moments per visit; the user re-finds the client each time; the field user ends the day with notes in the wrong place.	P-FIELD › Visit flow: check-in (photo + geo) → outcome → next step → collect payment, on one sheet · PAT-6 with a single sheet · UXP-1, UXP-4.
UX-FFM-03	Hidden dependency: the Payments tab appears only after a Final Price is entered in Add Activity (and on web, Final Price only shows when Status = Won).	I6 manager condition; I3 step 4; §21.7 shows Final Price and Pending Amount read-only.	Prevents collecting money against a deal with no price.	The user cannot see why the tab is missing; the price rule is discovered by trial.	Collect payment is a step shown in the visit when the stage is Won, with the line "Final price needed to collect" and an inline price field · P-FIELD › Visit · UXP-5 (explain the rule).
UX-FFM-04	Travel approvals sit outside claims. Travel has its own tabs Pending, Verified, Approved, Travel Summary, Rejected, All plus a Claimed state, but the step that moves a record to Claimed and the Finance Manager's travel screen are not documented.	I7 steps 1–5 and "Not documented"; G1 has no travel bill type documented.	Travel is built from visits, so the employee does not type distance. KM Revised lets the manager correct kms (§21.7).	Two approval chains for money (travel and claims); the employee cannot see travel payout in Claims; payout not documented.	P-INBOX › type Travel feeding P-PAY › Claims; day record auto-built, manager verifies with revised km, system creates the mileage claim · PAT-2, PAT-11 · UXP-2, UXP-6 (FR-FFM-013, FR-CLM-011).
UX-FFM-05	Leave and shift screens are duplicated inside CRM. Leave Request, Leave Balance, Leave History, Leave Approvals, Leave Policies, Configure Shift, Week off Configuration, Attendance Summary, Detailed, Missed Punch and Monthly Attendance are all CRM screens.	01-evidence.md: 18 attendance, leave and shift screens repeated inside CRM; §21.7 notes the Sales Manager menu "duplicates ATT/LVE screens". I12 lists Configure Shift (C9), Week off (C10), Leave Approvals (D6).	A field-only customer gets leave without buying HR.	Two copies of balances and approvals: a field user can have two leave histories. Admin maintains CRM Leave Policies separately (I2).	DEDUPE: P-REQ › Leave, P-TIME, P-INBOX, P-TEAM › Roster planner, P-INSIGHT; the field add-on simply shows them in the same app · UXP-2, UXP-10.
UX-FFM-06	GPS, activity and tracking reports repeat 3 times (Super Admin, Admin, Manager) and the same tracking columns appear on four screens: Tracking Log, Employee Tracking Log Report, Employee Tracking Details, Employee Summary Details.	01-evidence.md: GPS, activity and tracking reports repeated 3 times; screens list identical text "Started At, Start Location, Details, Stay Duration, Travel Duration, KMS Traveled, Reached At, End Location" three times; I10, I11.	Each role gets a tailored menu. Admin sees branch-wise and manager-wise cuts.	Report sprawl; fixes must be made in several places; users cannot tell which is the real one.	P-INSIGHT › Field topic with scope Me / Team / Location / Org; per-person route and timeline in the P-FIELD day drawer · PAT-8, PAT-4 · UXP-2, UXP-3.
UX-FFM-07	Device-change approval is a separate screen. A new mobile device needs manager approval at next login; the page text only says approvals "are displayed"; approve and reject buttons, notification and status are not documented.	I9 (all "Not documented" except the trigger); screens: Device Approvals (Super Admin, Managers).	Prevents a punch from an unknown phone.	The employee is stuck at login without feedback; the manager must go to a special screen to find it.	P-INBOX › type Device change, with swipe, and a waiting screen on the new phone with "Remind manager"; auto-approve option by policy · PAT-2, PAT-11 · UXP-1, UXP-6 (FR-IAM-015).
UX-FFM-08	The CRM mobile page has 34 screens; navigation is split (More tab for leave, Reports tab for travel approvals, Employee Location for managers, Pending Approvals somewhere else).	01-evidence.md: Sales CRM Mobile Application = 34 screens; mobile screens "More" (Leave Management) and "a Travel Approvals: click on Reports tab".	Features are discoverable in a long list.	Leave behind "More", travel behind "Reports", approvals behind another entry: the same user does three unrelated hunts.	Four tabs: Home, Field, Inbox, Me; "+ Request" for leave and claims · PAT-1, PAT-2, PAT-3 · UXP-1, UXP-7.
UX-FFM-09	Role-heading screens and role copies. "Sales Admin", "Super Admin", "Manager Level Features", "Employee Level Features", "Employee Login" are rows with no behaviour; the manager mobile app repeats every employee feature (5.3, 5.4, 5.5…) plus Employee Location.	Screens table rows 17, 18, 27, 30, 36 and 37 are heading-only or role-landing rows; gap-analysis FFM-G02 notes the role pages; I8 variants: Manager has the same features plus Employee Location.	A manager can do all the executive's tasks in the same app.	Documentation and navigation structured by role; users never learn one consistent product.	Scope changes data, not screens (Me / Team / Location / Org) · P-HOME, P-FIELD · UXP-3.
UX-FFM-10	Inconsistent lead-age and follow-up signals. Board colours are green 0–7, amber 8–14, red 15+, but the Client List "by Status" legend uses 0–5, 6–10, 11–15, 16–20, 21+. Follow-up icons are Scheduled, Exceeded, UnScheduled.	§21.7, §21.11; FFM-G11 in gap-analysis.	Colour bands give a quick scan of ageing leads.	Two scales for one concept; no documented configuration.	One configurable scale (default 0–7/8–14/15+) used on the board, list and Today's plan; follow-up chips Scheduled / Exceeded / Unscheduled · P-FIELD · UXP-8 (FR-FFM-010).
UX-FFM-11	Visit location check is only an indicator. Icons show client location matched / not matched / not available; if the client has no location the first visit's location is used. No enforcement is documented.	§21.7 "verification exists as an indicator, not as an enforcement rule"; I8 variants.	A free signal is already there; first visit auto-fills the location.	A wrong first visit permanently becomes the client location; managers see mismatch only after the fact.	Check-in compares to the account geo; policy block / flag / allow; "Wrong place?" lets the user flag instead of silently mismatching · P-FIELD › Visit · UXP-5, UXP-6 (FR-FFM-007).
UX-FFM-12	Five masters with the same pattern; deactivation blocked until employees are moved. Demo Status, Status Master, Associate Type, Qualifications, Specializations each need create → set Active/Inactive; inactivating needs "transfer all employees in that item to another one first".	I1 steps and rule; screens table rows 19–24.	Same pattern everywhere is predictable; duplicates are not allowed.	Five screens for list editing; blocked inactivation is a dead end unless the admin knows to transfer first.	One Masters editor with tabs; "Move N items to…" appears inline when deactivating · P-SET › Masters · UXP-2, UXP-5 (FR-ORG-009).
UX-FFM-13	Follow-ups require choosing date and employee and pressing Search. The mobile Today's Follow-up screen has the filters; the web dashboard shows follow-ups but the mobile arrow opens another screen.	I8 step 5; screens "Today's Followup's" and "Employee Dashboard".	The manager can pick any employee and date.	The 80% case (my follow-ups, today) takes the same filter steps as the rare one.	Today's plan opens on today / me; manager toggles Team; overdue shown first · P-FIELD · UXP-4, UXP-9.
UX-FFM-14	Tracking depends on invisible conditions. Tracking needs login, location permission and internet; the first-login instruction is "Allow all securities"; interval and gap handling are not documented; two GPS modes exist (Point-to-Point, GPS Monitoring) but where a user sees which is active is not documented.	I10, I12; §21.7.	An in-app disclosure ("Allow Spryple CRM to track your activity") precedes the OS prompt. Two modes allow privacy-friendlier routes.	Employee cannot tell whether tracking is working; manager sees silent gaps.	Home shows a tracking chip (On, Paused, No GPS), gaps explained on the map, offline queue (FR-FFM-001, FR-FFM-003, FR-FFM-014) · P-HOME, P-FIELD · UXP-5.
UX-CLM-01	Claim statuses differ across four screens. Employee web tabs: Submitted, In Progress, Paid, Rejected. Manager and Finance web: Pending, Verified, Approved, Paid, Rejected. Mobile: Submitted, Verified, Paid, Rejected (no Approved). Travel: Pending, Verified, Approved, Rejected, Claimed.	G1 statuses; G2 statuses; G3 statuses; I7 statuses.	Each role sees wording suited to its job.	The same claim is "In Progress" for the employee and "Pending" for the manager; mobile cannot show Approved.	One model Draft → Submitted → Verified → Approved → Paid, plus Rejected (reason) and Withdrawn, used by every role and by travel · PAT-10 timeline · UXP-8 (FR-CLM-006).
UX-CLM-02	Claim flow splits across devices. Employee requests and manager verifies on mobile, but approval and payment happen only on the web by the Finance Manager.	G3 steps 2–3.	Finance has the bigger screen for bulk work.	Approval waits for a desk; managers cannot see after verification who holds it.	Mobile inbox supports approve and mark-paid with bulk; web stays for payout files and payroll (FR-CLM-008, FR-CLM-009) · P-INBOX, P-PAYROLL · UXP-7.
UX-CLM-03	Claims is installed as "Spryple CRM" and buried in More. A claim is reached via More → Claim Management → Claims History → Claim Request.	G3 trigger; §21.6: claims is a module inside the HCM/CRM app shell; I12 installation: search "Spryple CRM".	One app install for employees who already use CRM.	An office employee must install a "CRM" app for a claim; 4 hops to start; the manager claims from Claim History.	Claim is a type in the "+ Request" sheet on the one app; shortcut on Home after a visit or trip · P-REQ · PAT-3 · UXP-1, UXP-4.
UX-CLM-04	Claim entry is a popup per bill, then a description at the end. Each bill needs Reimbursement Type, Bill Number, Bill Date, Bill Amount, file; the receipt image is required with a 2 MB limit; limits, drafts and edit-after-submit are not documented.	G1 steps 1–3 (11 actions); G3 step 1; §21.6.	Multiple bills can be added to one claim; image required, so claims always have evidence.	Typing five fields per bill; no policy check until verification; no draft or withdraw documented.	Snap receipt first, type and amount suggested, add more bills in the same sheet, live policy line "Within limit" or "Over by ₹X"; save draft (FR-CLM-002…005) · P-REQ › Claim · PAT-3 · UXP-4, UXP-5.
UX-CLM-05	Web approve and pay steps are described as tabs, not actions. Finance sees tabs Verified, Approved, Paid, Rejected; the steps that mark Approved and Paid, a rejection reason and partial approval on web are not documented.	G2 "Not documented"; mobile shows a Rejected Reason (§21.6).	Tab counts give a quick queue view.	The user cannot tell what button moves the claim; no documented audit trail.	Inbox card with Approve and Pay buttons, mandatory reason on reject, inline timeline · P-INBOX · PAT-2, PAT-10 · UXP-8.
UX-CLM-06	Separate module landing and dashboards per role. Finance, Manager and Employee each have a "Claim Management" module entry and a dashboard (Claims Count by Status, Settlement Ratio, Alerts, Scorecard, Reimbursement Type by Paid Amount); the manager alerts show on the dashboard rather than where the work is.	G2, G4; screens: Claim Management for Finance Manager, Claims Module for Manager, Claims Module for Employee.	One dashboard summarises claims at a glance.	Counts and the queue are on different screens; three module entries to maintain.	Counts as a strip on the inbox (Claim filter) and P-PAY; full dashboard in the report centre for finance (FR-CLM-010) · P-INBOX, P-INSIGHT · UXP-2, UXP-3.
UX-CLM-07	Manager and finance claim approval are two copies of one page. "Claim Approval" and "Claims Approval" with the same description; mobile "Claim Pending Approvals" is a third. Search is by name or claim ID only.	Screens Claim Approval, Claims Approval, Claim Pending Approvals; G2 steps 1–2.	Roles see only their own stage.	Filters differ per role; the same claim ID is searched three ways.	Stage is a column; one claim inbox with filters City-Branch, Manager, Employee, dates; search in P-SEARCH · P-INBOX · PAT-2 · UXP-2.
UX-CLM-08	Claim ID and tracking are plain. Claim IDs follow CL_GEN_<company>_<n>; the Claim Report lists IDs, receipt number and statuses; withdrawal and edit are not documented; payment confirmation to the employee is not documented.	§21.6; G2 reports; G1 "Not documented".	A traceable ID and receipt number exist.	The employee cannot find "where is my money?" without opening history.	Status timeline on each claim and a push when it moves; Home action card "Claim paid ₹X" (FR-CLM-006, FR-NTF-001) · P-PAY, P-HOME · PAT-10, PAT-1 · UXP-1.

Issues: 14 FFM + 8 CLM = 22.

5.2 Where every feature goes (all screens addressed)

Treatments: KEEP+, MERGE, EMBED, REPLACE, DEDUPE (see 00-ia-and-principles.md §4). Place names are the IDs from the rulebook; the text after "›" names the section.

#	Spryple screen	Audiences	New place › section	Treatment	Why / how it works now
1	Sales Manager	Super Admin, Admin	P-FIELD › Team (Manager scope)	REPLACE	A manager "role page" listing punch, GPS, clients, leave and reports becomes the same Home and Field screens with Team scope (UXP-3).
2	GPS Monitoring	Super Admin, Admin, Managers	P-FIELD › Live map (Team / Location / Org scope)	KEEP+	One live map; scope picker replaces the Super Admin, Admin and Manager copies. Last position, battery, punched-in count, past-date replay (FR-FFM-004).
3	Clients	Super Admin, Managers	P-FIELD › Pipeline board (Team scope)	KEEP+	Manager sees the same board as the executive, filtered to the team; tap a card to open the account, reassign inline (FR-FFM-012).
4	Attendance Summary Report	Super Admin, Managers	P-INSIGHT › Attendance topic	DEDUPE	The HR attendance report with scope Team; first in/last out, productive hours stay as columns. No CRM copy.
5	Clients Report	Super Admin, Managers	P-INSIGHT › Field topic › Accounts	MERGE	Accounts report in the one report centre; the admin branch/manager-wise variants are scope filters.
6	Employee Activity Report	Super Admin, Admin, Managers	P-INSIGHT › Field topic › Field activity	MERGE	One report: punch in/out, visits, kms per person; row drill opens the day drawer.
7	Summary	Super Admin, Managers	P-INSIGHT › Field topic › Field activity	MERGE	Same columns plus travel type as the Employee Activity Report; one report with a "type" column.
8	Tracking Log	Super Admin, Managers	P-FIELD › Live map › Day drawer	EMBED	Started at, start/end location, stay and travel durations, kms appear as a timeline under the route (FR-FFM-004).
9	Device Approvals	Super Admin, Managers	P-INBOX › type Device change	MERGE	Approve or reject by swipe; the employee sees "Waiting for manager" on the login screen and can nudge (FR-IAM-015).
10	Employee Tracking Log Report	Super Admin, Admin, Managers	P-FIELD › Live map › Day drawer	DEDUPE	Third copy of the tracking log columns; export from the drawer or the report centre.
11	Employee Summary Details	Super Admin, Managers	P-FIELD › Team today › Person card	EMBED	First login, last logout, worked hours, new visits/clients, kms, activities shown as one card per person per day.
12	Activities	Super Admin, Managers, Mobile App	P-FIELD › Account timeline and Day drawer	EMBED	"Show" click is gone; activities are always visible on the account and the day.
13	Employee Tracking Details	Super Admin, Managers	P-FIELD › Live map › Day drawer	DEDUPE	Same columns as Tracking Log; one view.
14	Team Travel Approvals	Super Admin, Managers	P-INBOX › type Travel (feeds claims)	MERGE	Select-records summary with editable KM Revised stays in the approval card; verified travel becomes a mileage claim (FR-FFM-013, FR-CLM-011).
15	Assignments Report	Super Admin, Managers	P-FIELD › Today's plan (Team) and P-INSIGHT › Field topic	MERGE	Planned vs actual by status for a date range; plan is a view, the report is an export (FR-FFM-012).
16	Leave History	Super Admin, Managers, Employee	P-TIME › My requests	DEDUPE	HR leave history with filter; no CRM copy.
17	Admin Level Features	Admin	P-SET › Roles & access	REPLACE	A role-heading page; the admin sees Settings and the report centre instead.
18	Sales Admin	Admin	P-SET › Masters	DEDUPE	Heading only; not documented as a screen. Masters live in Settings.
19	Demo Status	Admin	P-SET › Masters › Pipeline stages	MERGE	Demo status and client status become one stage master (name, order, won/lost flag, Active/Inactive; FR-FFM-008).
20	Status Master	Admin	P-SET › Masters › Pipeline stages	MERGE	Same master as Demo Status; the second master is removed.
21	Client Associate Type	Admin	P-SET › Masters › Account contacts	EMBED	Heading only; becomes the group title for associate masters.
22	a Associate Type	Admin	P-SET › Masters › Account contacts	KEEP+	Add, rename, Active/Inactive; inactivating offers "move N items to..." inline.
23	b Qualifications	Admin	P-SET › Masters › Account contacts	KEEP+	Same list editor as Associate Type.
24	c Specializations	Admin	P-SET › Masters › Account contacts	KEEP+	Same list editor.
25	Leave Policies	Admin	P-SET › Policies › Leave types	DEDUPE	One leave policy for HR and CRM staff; the CRM copy is removed (FR-ORG-009).
26	Clients Reports	Admin	P-INSIGHT › Field topic › Accounts	MERGE	Admin branch-wise and manager-wise are Location and Team scope on the same report.
27	Super Admin	Admin	P-INSIGHT	DEDUPE	Heading only; not documented as a screen.
28	Client Associate Reports	Admin	P-INSIGHT › Field topic › Contacts	KEEP+	By type, qualification, specialization, owner; closes gap FFM-G29.
29	Monthly Attendance Reports	Admin	P-INSIGHT › Attendance topic	DEDUPE	Monthly attendance with Location and Team scope; no CRM copy.
30	Manager Level Features	Managers, Mobile App	P-FIELD and P-TEAM	REPLACE	Role-heading page; managers get the Team scope on every place.
31	Attendance Detailed Report	Managers	P-INSIGHT › Attendance topic	DEDUPE	Month view of present/absent/late; same report.
32	Missed Punch Report	Managers	P-HOME › Fix action and P-INSIGHT › Attendance	DEDUPE	The employee gets a Fix button on Home; the manager sees a count card (UXP-1).
33	Leave Approvals	Managers	P-INBOX › type Leave	DEDUPE	One inbox for every approval; swipe approve.
34	Configure Shift	Managers	P-TEAM › Roster planner	DEDUPE	Drag-and-drop shift assignment, same as HR staff.
35	Week off Configuration	Managers	P-TEAM › Roster planner	DEDUPE	Week-off patterns in the same planner.
36	Employee Level Features	Employee, Mobile App	P-PAY › Claims	REPLACE	Heading only.
37	Employee Login	Employee, Mobile App	P-HOME	REPLACE	"Five screens" (Dashboard, Client List, Leave Request, Leave History, Leave Balance) map to Home, Field and My time.
38	Login	Employee, Mobile App	P-ME › Security (sign-in)	MERGE	One sign-in for the whole product; company code remembered; biometric unlock.
39	Employee Dashboard	Employee	P-HOME with a Field card	MERGE	Punch time, today follow-ups, calendar, add client and map become the Field card and Today's plan.
40	Add Client	Employee, Mobile App	P-FIELD › + Lead (quick add) and Account	KEEP+	Capture with photo and phone in 3 fields; the rest is optional (FR-FFM-006, FR-FFM-015).
41	Client List	Employee	P-FIELD › Pipeline board	REPLACE	Two dashboards by dropdown become one board with a List toggle.
42	a Client Demo Status	Employee	P-FIELD › Pipeline board	MERGE	Demo columns become stages; no second view.
43	b Client Status	Employee	P-FIELD › Pipeline board	MERGE	Won/Lost/Interested are outcomes on the visit, not a second board.
44	Travel Approvals	Employee, Mobile App	P-FIELD › Travel (day record)	MERGE	Employee sees an auto-built day record with status; no search form (FR-FFM-013).
45	Leave Request	Employee	P-REQ › Leave	DEDUPE	Balance and approver shown in the sheet (UXP-5).
46	Leave Balance	Employee	P-TIME › Balances	DEDUPE	Balances beside the calendar.
47	Dashboard	Mobile App	P-HOME	MERGE	Mobile main dashboard is Home with the punch card first.
48	Today's Followup's	Mobile App	P-FIELD › Today's plan	KEEP+	Opens on today and me by default; managers switch to Team; Scheduled/Exceeded/Unscheduled chips (FR-FFM-009).
49	Punch In/Punch Out	Mobile App	P-HOME › Punch card	KEEP+	One tap with selfie and geo-fence (FR-ATT-002, FR-FFM-001).
50	Activity Dashboard	Mobile App	P-FIELD › Pipeline board	MERGE	Same board as web; stages from the one master.
51	a Add Activity	Mobile App	P-FIELD › Visit › Outcome	KEEP+	Outcome step of the visit, prefilled type and next follow-up.
52	b Activity List	Mobile App	P-FIELD › Account › Timeline	EMBED	Timeline on the account.
53	c Client Details	Mobile App	P-FIELD › Account › Details	EMBED	Edit in place.
54	d Client Associates	Mobile App	P-FIELD › Account › Contacts	EMBED	Contacts tab with + button.
55	e Client Payments	Mobile App	P-FIELD › Visit › Collect payment	EMBED	Step in the visit; Final Price and Pending Amount shown read-only (FR-FFM-011).
56	More	Mobile App	P-ME and tab bar	REPLACE	No "More" bucket; leave is in + Request, history in My time.
57	a Leave Request	Mobile App	P-REQ › Leave	DEDUPE	Same sheet as every other app screen.
58	b Leave History	Mobile App	P-TIME › My requests	DEDUPE	One list.
59	Employee Location	Mobile App	P-FIELD › Team map (mobile)	KEEP+	Manager list of people with last seen; tap to see on map (gap FFM-G04; FR-MOB-018).
60	a Travel Approvals	Mobile App	P-FIELD › Travel (day record)	MERGE	Reports tab entry removed.
61	b Team Travel Approvals	Mobile App	P-INBOX › type Travel	MERGE	Swipe verify; KM Revised editable.
62	c Pending Approvals	Mobile App	P-INBOX	MERGE	The one inbox shows every pending type.
63	Claim Management for Finance Manager	Admin	P-INBOX › Claims filter and P-PAYROLL › Reimbursements	REPLACE	Left-menu module entry removed; finance sees claims in the inbox and a payout queue.
64	Claim Dashboard for Finance Manager	Admin	P-INSIGHT › Claims dashboard (and counts on the inbox)	KEEP+	Counts by status, settlement ratio, scorecard, paid by type (FR-CLM-010).
65	Claim Approval	Admin	P-INBOX › type Claim (Approve, Pay)	MERGE	Bulk approve and bulk pay with the filters City-Branch, Manager, Employee, dates (FR-CLM-008).
66	Claims Module for Manager	Managers	P-INBOX › type Claim	REPLACE	Module landing is removed.
67	Claims Approval	Managers	P-INBOX › type Claim (Verify)	MERGE	Per-bill accept, reject or reduce, with selected summary (FR-CLM-007).
68	Employee Level Features	Employee	P-PAY › Claims	REPLACE	Heading only.
69	Claims Module for Employee	Employee	P-PAY › Claims	EMBED	Employee dashboard counts become a header strip over my claims.
70	Claims Request	Employee	P-REQ › Claim	KEEP+	Snap receipt, category, amount, submit (FR-CLM-003).
71	Claims Management by Employee	Mobile App	P-REQ › Claim and P-PAY › Claims	DEDUPE	Claims is no longer a "More" path in a CRM app shell.
72	Claims History	Mobile App	P-PAY › Claims (and P-TIME › My requests)	MERGE	Status timeline with the same statuses as every request.
73	Claims Management - Manager	Mobile App	P-INBOX › type Claim	DEDUPE	Same inbox as the employee app; no separate manager path.
74	Claim Pending Approvals	Mobile App	P-INBOX › type Claim	MERGE	Search by name or claim ID stays in the inbox search (P-SEARCH).

Rows covered: 62 of 62 (CRM / Field Force) + 12 of 12 (Claims) = 74 of 74. Treatment tally: MERGE 23, DEDUPE 19, KEEP+ 13, REPLACE 10, EMBED 9. No Spryple capability is dropped (UXP-10); DEDUPE rows keep their capability in the named home place.

5.3 Redesigned workflows

Baseline = documented UI actions from workflow-actions.json (documented-actions estimate, not a live measurement). Where the baseline is 0 the workflow documents no click-level steps, so there is no saving to claim; the redesign taps are shown for completeness and excluded from the saving total.

ID	Workflow	Spryple documented UI actions	Redesigned flow	Taps after (estimate)	Saving
G1	Claim request with bills (web, Employee)	11	+ Request → Claim → snap receipt → confirm category and amount → Submit (P-REQ, PAT-3); a second bill adds 3	6	5
G2	Claim verification and finance approval/payment (web)	3 (tabs only)	Manager swipe-verifies in Inbox (1); finance bulk Approve (1) then bulk Pay (1)	3	0 (same count, one list, one status model)
G3	Claim (mobile): request, verify, approve, pay	16	Employee 6 as G1; manager 1 swipe verify; finance 1 approve + 1 pay on mobile or web; paid status pushes to employee	9	7
G4	Claims dashboard	1	Counts strip on P-PAY and Inbox filter (0 extra taps); full dashboard 1 tap in report centre	1	0
I1	CRM masters	3	Settings › Masters › Pipeline stages / Contacts: Add, name, Save; deactivate offers inline "move to"	3	0 (5 masters become 2 lists)
I2	CRM leave policies	3	Settings › Policies › Leave types (shared with HR): Edit, change, Save	3	0 (copy removed)
I3	Add client to activity to payment (web)	17	+ Lead → visit outcome sheet (stage, type, next follow-up prefilled) → Won price → Collect payment (see journey 2)	10	7
I4	Manager view of clients, reassignment	2	Pipeline board (Team) → open account → Reassign → pick person	2	0
I5	Client Associates (mobile)	3	Account › Contacts: +, fill (type, name, phone), Save	3	0
I6	Client Payments (mobile)	3	In the visit: Collect → amount (method defaults to last used) → Save	3	0
I7	Travel approvals (Pending, Verified, Approved, Claimed)	5	Day record auto-built; manager swipe-verify with optional revised km (1); finance approves in Inbox (1); mileage claim auto-created and paid with claims	2	3
I8	Mobile CRM daily flow: punch, client, activity	16	Punch card 1 tap (selfie auto) → check-in 1 → outcome 3 → next follow-up 1 (prefilled) → new lead 2	8	8
I9	Device approvals	0 (not documented)	Inbox: swipe Approve (1); employee waits screen with Remind	1	n/a
I10	GPS monitoring and tracking reports	1	Field › Live map (1 tap), scope picker, past-date scrubber	1	0 (3 report copies become 1)
I11	Sales Manager reports and CRM attendance (web)	0 (not documented)	Reports › topic (Field or Attendance) → scope → saved view (2)	2	n/a
J8	Mobile punch with camera (CRM)	0 (not documented; see I8 step 1)	Home punch card: 1 tap, selfie and geo-fence prefilled	1	n/a

Total (16 workflows): the 13 workflows with a documented baseline have 84 documented UI actions (G 31 + I 53) and fall to 54 redesign taps, a saving of 30 (about 36%). The three workflows with no documented click steps (I9, I11, J8) add 4 redesign taps (58 in all) and are excluded from the saving. All numbers are estimates.

Journey 1: the field day (punch → plan → visit check-in → activity → next follow-up → payment)

Before (Spryple, I8 + I3 + I6; about 16 + 3 documented actions on mobile): Camera tab → Take Picture → Punch In; open Dashboard → Today's Follow-ups arrow → pick date and employee → Search; open client from Activity Dashboard → Add Activity → pick Activity Type, Follow-up date, Follow-up time, Demo Status, Status, Final Price, Description → Save; Client Payments tab → Add (+) → Payment Method → Amount → Description → Save. Location check is a passive icon (§21.7).

After (P-HOME → P-FIELD):

1. Home, punch card: tap Punch in (selfie and geo-fence prefilled; tracking chip turns On). 1 tap.
2. Plan: the Field card shows "Today: 6 visits, 1 overdue". Tap the first stop on Today's plan. 1 tap (opens on today and me; overdue first).
3. Check-in: at the account, tap Check in; photo optional, geo compared to the account (match, flag or block by policy). 1 tap.
4. Activity (outcome): pick the outcome chip (Interested / Demo done / Won / Lost); type is prefilled as Visit; notes by voice or text. 1 tap, plus 1 for notes optional.
5. Next follow-up: a suggested date (for example +3 days) is prefilled; tap to accept or change. 1 tap.
6. Payment (only if Won): enter amount, method defaults to last used (Cash), Save. 2 taps. Check-out is automatic when leaving the geo-fence or on tap.

Total about 8 taps for one visit with payment (punch 1 is once a day; each further visit is about 5 without payment). Principles: UXP-1, UXP-4, UXP-5; patterns PAT-1, PAT-6, PAT-11; FR-FFM-001, 007, 009, 011, 014. Works offline; synced later (FR-FFM-014).

Journey 2: adding a lead from the field

Before (I8 step 2, I3 step 1): Add Client → camera → Organization, Contact Person, Contact Number, Email, Address1, Address2 → Country, State, City, Pin code → Expected Price, Description → Save (about 14 documented actions); client lands in Leads; a second visit is needed to add an activity.

After:

1. Field tab → + Lead (1 tap).
2. Fields: Organization (typed or picked from nearby places, 1), Contact phone (1, can be a contact-book pick), photo (optional, 1). Address, city and pin are prefilled from GPS (not counted); email, expected price and the rest sit behind "More details" (UXP-9).
3. Save (1 tap) with a toggle "Log this visit now" that opens the outcome sheet with the same photo.

About 4 taps (vs 14 documented). The lead appears in the Leads stage; duplicates (same phone) are flagged before save. Principles UXP-4, UXP-9; FR-FFM-006, FR-FFM-015.

Journey 3: the manager's live team view

Before (I10, I11): Dashboard → GPS Monitoring (web, 3 role copies); Employee Location tab (mobile) → tap location icon per person; separate Employee Activity Report → Summary → Tracking Log → Employee Tracking Log Report → Employee Tracking Details for the route; Today's Follow-ups needs employee and date → Search.

After (P-FIELD › Live map; P-TEAM › Team today):

1. Field tab, Team scope (1 tap, remembered). The map shows each person with status (Punched in, On visit, Idle, No GPS), battery and last seen; counts at top "9 of 11 punched in".
2. Tap a person → day drawer: route replay, timeline of stops with stay and travel durations, kms, visits and activities (replaces the 4 tracking screens).
3. Row actions in the drawer: Call, Reassign visit, Approve revised km.

1 tap to see the team, 2 to see one person's day, versus 3 to 5 documented screens. The same view serves Admin with Location and Org scope. Principles UXP-3, UXP-2; PAT-4, PAT-8; FR-FFM-003, FR-FFM-004.

Journey 4: travel to reimbursement through claims

Before (I7, G1, G3): Travel Approvals: Select Employee, From Date, To Date, Minimum Visits, Search; select records; Selected Records Summary; manager Verify or Reject; Finance Manager approves (screen not documented); "Claimed" step not documented; reimbursement then needs a separate bill claim (G1) or a payout that is not documented.

After:

1. Auto: the day record (kms from tracking, visits) builds itself at punch-out (PAT-11). The employee does nothing, and sees "Travel 42 km, 6 visits, Submitted" on Home.
2. Manager: Inbox › Travel card shows records with Selected summary (visits, travelled km, revised km). Swipe right to verify (1 tap); tap the km to revise with a reason (original kept).
3. Finance: Inbox › Claims shows the mileage claim (km × policy rate, FR-CLM-011); Approve (1 tap, bulk), then it flows to payroll as a reimbursement (FR-CLM-009).
4. Employee gets a push and a Paid line on the claim timeline.

2 taps (manager, finance) vs 5 documented actions plus an undocumented tail. Minimum-visits rule becomes a policy flag, not a search filter. Principles UXP-2, UXP-6, UXP-8; FR-FFM-013, FR-CLM-011.

Journey 5: a claim with a receipt photo, through verify, approve and pay

Before (G3, 16 documented actions on mobile and web): More → Claim Management → Claims History → Claim Request → Add Bills → Bill Date, Reimbursement Type, Bill No., Bill Amount, Upload Image (2 MB) → Add Bill → Description → Save. Manager: Claims Pending Approvals → open → Verify → Verified Amount → Verify. Finance on web: Approve, then Paid (steps not documented as buttons).

After:

1. Employee (6 taps): + Request → Claim → snap the receipt (compressed; the 2 MB limit disappears for the user) → category suggested (confirm) → amount (typed, or OCR in R4) → Submit. The sheet shows "Within limit: Food ₹500/day" or "Over by ₹120, add a reason" (FR-CLM-004). A duplicate receipt is blocked (FR-CLM-005).
2. Manager (1 tap): push "Asha: Food ₹420". Open the Inbox card (receipt big, policy line, history); swipe right = Verify; per-bill Reject or reduce by tap if needed.
3. Finance (2 taps): Inbox › Claims › Verified: select all → Approve; then Mark Paid (or included in the next payroll). Status timeline: Submitted → Verified → Approved → Paid.
4. Employee sees each step on Home and in P-PAY.

9 taps end to end (vs 16 documented). Principles UXP-1, UXP-5, UXP-8; PAT-3, PAT-2, PAT-10; FR-CLM-003…009.

Journey 6: a device change

Before (I9): Employee installs on a new phone, logs in, is blocked; the Manager finds Device Approvals (web screen under Super Admin or Manager) and approves; button names, notifications and statuses are not documented.

After:

1. New phone: employee signs in (P-ME › Security); sees "Waiting for your manager, Ravi, to approve this device" with Remind and the old device name. Punches are queued and not lost.
2. Manager: push → Inbox › Device change card (model, OS, last device, location of login); swipe Approve (1 tap) or Reject with a reason.
3. Optional policy: HR or auto-approve if the old device is verified by OTP on the same number (PAT-11).
4. The old device is signed out remotely (FR-IAM-015).

1 tap for the manager and no hunting; the employee has a status instead of a blocked screen. Principles UXP-1, UXP-6.

5.4 UX enhancements beyond Spryple

• [Proposed] One-tap "Log this visit" from a push at the customer geo-fence ("Arrived at Apollo Clinic? Check in") so check-in is a single tap or automatic (FR-FFM-007).
• [Proposed] Voice note to activity: dictate the notes of a visit; on-device transcription fills the description.
• [Proposed] Beat plan with route order: Today's plan sorted by distance, with a "next stop" button opening navigation (FR-FFM-012).
• [Proposed] Offline-first visit capture with a visible "3 waiting to sync" chip (FR-FFM-014).
• [Proposed] Duplicate account guard: matching phone or place name warns before saving a new lead (FR-FFM-006).
• [Proposed] Next-step suggestions: after each outcome the follow-up date is prefilled by stage (for example Demo Completed → +2 days); never forced.
• [Proposed] Day-end summary on Home: visits, kms, collections, claims created; one tap to submit the day's travel.
• [Proposed] Receipt camera with auto-crop and compression; OCR to fill amount, date and vendor in R4 (FR-CLM-013).
• [Proposed] Claim from a visit or trip: "Add expense" button inside a visit with account and date prefilled (FR-CLM-003).
• [Proposed] Swipe-to-verify claims with a "Why flagged" line (over limit, duplicate, late) so the manager decides in seconds.
• [Proposed] Tracking transparency card in P-ME › Privacy: when tracking ran today, what was stored, retention 90 days (FR-FFM-016).
• [Proposed] Manager coaching nudges: lead aging red (15+ days) list for the team with a one-tap "Reassign" (FR-FFM-010, FR-FFM-012).

5.5 PRD impact

Proposed ID	UX requirement	Priority (MoSCoW)	Release	Source issue
UX-FR-FFM-01	One pipeline stage master and one board (list toggle); demo is an activity type; outcomes Won/Lost with reason. Extends FR-FFM-008.	Must	R3	UX-FFM-01, UX-FFM-12
UX-FR-FFM-02	Single visit flow: check-in (photo, geo) → outcome → next follow-up → collect payment, on one sheet with prefilled defaults; ≤ 5 taps per visit. Extends FR-FFM-007, 009, 011.	Must	R3	UX-FFM-02, UX-FFM-03
UX-FR-FFM-03	Today's plan opens on today and me by default, overdue first; manager Team toggle. Extends FR-FFM-009, FR-FFM-012.	Must	R3	UX-FFM-13
UX-FR-FFM-04	Quick-add lead in ≤ 4 taps with GPS-filled address and duplicate warning. Extends FR-FFM-006.	Must	R3	UX-FFM-02
UX-FR-FFM-05	Manager Team scope on the live map, day drawer with route and timeline; replaces 3 report copies. Extends FR-FFM-004, FR-RPT-002, FR-RPT-004.	Must	R3	UX-FFM-06
UX-FR-FFM-06	Travel as an inbox approval type with editable revised km and auto-created mileage claim. Extends FR-FFM-013, FR-CLM-011.	Must	R3	UX-FFM-04
UX-FR-FFM-07	Device-change approval as an inbox type; waiting state with Remind on the new device; queued punches. Extends FR-IAM-015.	Must	R1	UX-FFM-07
UX-FR-FFM-08	No CRM copies of leave, shift, week-off and attendance screens; field users reach them via P-REQ, P-TIME, P-TEAM. Extends FR-ATT-002 and the ATT/LVE FRs.	Must	R3 (rows use ATT/LVE releases)	UX-FFM-05
UX-FR-FFM-09	Mobile navigation of four tabs (Home, Field, Inbox, Me) and "+ Request"; no "More" bucket. Extends FR-MOB-001, FR-MOB-018.	Must	R3	UX-FFM-08, UX-FFM-09
UX-FR-FFM-10	One configurable lead-age scale across board, list and plan; follow-up chips Scheduled / Exceeded / Unscheduled. Extends FR-FFM-010.	Should	R3	UX-FFM-10
UX-FR-FFM-11	Geo-verification at check-in with block / flag / allow and a "Wrong place?" flag; first-visit location needs confirmation. Extends FR-FFM-007.	Should	R3	UX-FFM-11
UX-FR-FFM-12	Masters editor with inline "move to" when deactivating; associate-wise report. Extends FR-ORG-009, FR-FFM-006.	Should	R3	UX-FFM-12
UX-FR-FFM-13	Tracking status chip on Home (On, Paused, No GPS), gap explanation on the map. Extends FR-FFM-001, FR-FFM-003.	Should	R3	UX-FFM-14
UX-FR-FFM-14	Voice note, geo-fence arrival prompt and route-ordered plan.	Could	R3 or later	UX-FFM-02, UX-FFM-13
UX-FR-CLM-01	One claim status vocabulary (Draft, Submitted, Verified, Approved, Paid, Rejected, Withdrawn) for all roles and travel. Reinforces FR-CLM-006.	Must	R2	UX-CLM-01
UX-FR-CLM-02	Claim in the "+ Request" sheet on the one mobile app; receipt-first capture, suggested category, live policy line, drafts. Extends FR-CLM-003, 004, 005.	Must	R2	UX-CLM-03, UX-CLM-04
UX-FR-CLM-03	Mobile inbox supports verify, approve and mark paid, with bulk; web adds payout file. Extends FR-CLM-007, 008, 009.	Must	R2	UX-CLM-02, UX-CLM-07
UX-FR-CLM-04	Approve and pay as visible actions with mandatory reject reason and inline timeline. Extends FR-CLM-006.	Must	R2	UX-CLM-05
UX-FR-CLM-05	Claim counts as a strip on the inbox and P-PAY; finance dashboard in report centre. Extends FR-CLM-010.	Should	R2	UX-CLM-06
UX-FR-CLM-06	Push and Home action card on every claim state change, with "Claim paid ₹X". Extends FR-NTF-001, FR-CLM-009.	Should	R2	UX-CLM-08
UX-FR-CLM-07	"Add expense" inside a visit or trip; OCR on receipt. Extends FR-CLM-011, FR-CLM-013.	Could	R3 / R4	UX-CLM-04, UX-FFM-04