Evidence: measured UX patterns in Spryple

Computed by script from the crawled Help Center (feature tree) and the fact-only workflows. App boilerplate sections (Introduction, Installation and so on) are excluded. Screen names are compared after removing their numbering.

Headline numbers

Measure	Value	What it tells us
Functional screens documented	368	The size of the surface users and trainers must learn
Unique screen names	277	91 screens are repeats of another screen
Screen names repeated in 2 or more places	47	The same screen rebuilt per role or per module
Report-like screens (report, summary, history, log, dashboard)	118 (32%)	A third of the product is read-only lists, each with its own filters
Approval screens (approve, pending, verify)	35	Approvers hunt across modules; there is no single inbox
Request screens (request, apply, regularize, permission, separation, claim)	40	A separate form and history per request type
"On behalf" screens	3	Separate copies of request forms for managers
Configuration and master screens	49	Settings scattered across modules
"Messages Master" screens	4	The same tool repeated per module
Attendance, leave and shift screens repeated inside CRM	18	Field users get a second copy of HR screens
Approval entry points for one attendance request	3	Team widget, dashboard button and Pending Approvals
Documented UI actions across 119 workflows	656	The baseline effort the redesign must cut

Most repeated screens

Screen (numbering removed)	Places it appears
dashboard	8
attendance summary report	5
leave history	5
summary report	4
missed punch report	4
employee dashboard	4
gps monitoring	3
employee activity report	3
employee tracking log report	3
activities	3
current day attendance report	3
punch summary report	3
week off configuration	3
reports	3
sales manager	2
clients	2
clients report	2
summary	2
tracking log	2
device approvals	2
employee summary details	2
employee tracking details	2
team travel approvals	2
assignments report	2
monthly attendance report	2

Heaviest workflows (documented UI actions)

ID	Workflow	Documented steps	Documented UI actions
B1	New hire to first login (end-to-end)	10	19
D11	Optional holiday request (employee), approval and on-behalf (manager)	5	19
C11	Shift rotation: create sequence, assign, reassign	3	18
F2	Separation request, approval, offboarding checklist (end-to-end)	6	17
I3	Add client to activity to payment (Sales Executive, web)	6	17
G3	Claim (mobile): request, verify, approve, pay	3	16
I8	Mobile CRM daily field flow: punch, client, activity	6	16
C2	Attendance request by employee (three entry points)	5	15
C8	Manager attendance regularization and approval	4	14
H1	Timesheet setup chain (Admin): client, project, assign team, task, roles	5	13
C3	Attendance request on behalf of employee (Manager)	3	12
C4	Attendance request approval (three ways)	3	12
A3	Employee Password Reset (Admin)	5	11
C5	Shift change request (employee) and approval with swap (manager)	4	11
E10	Variable pay distribution and schedule	3	11
G1	Claim request with bills (web, Employee)	4	11
J1	Attendance request (employee) and approval (manager), Spryple HCM	5	11
L3	Work Location	0	11
B6	Induction program (HR manager)	4	10
C6	Permission request (employee) and approval (manager)	4	10

Densest Help Center pages (screens per page)

Page	Screens
Mobile App › Sales CRM Mobile Application	34
For Managers › Payroll Management	29
For Managers › Attendance Management	28
For Employee › Attendance Management	22
For Admin › Employee Management	20
For Managers › CRM Field Force Management	20
For Managers › Leave Management	17
For Super Admin › CRM Field Force Management	16
For Admin › CRM Field Force Management	16
For Admin › Leave Management	15