Spryple — Reverse KT Guide
Purpose: a presenter's guide for walking the team through how Spryple works, module by module and role by role, then checking understanding with teach-back questions. Sources: all 43 Help Center pages (https://spryple.com/help/, which is the same site as https://help.spryple.com/), re-crawled recursively on 2026-11-14 through the E2E engine. No page had changed since the 2026-10-31 capture. Screenshot-verified details are tagged [SS]. Companion documents:
- spryple-feature-tree.md: every screen, option and sub-item with its breadcrumb (438 screens, 2,054 sub-items).
- spryple-analysis.md: the critique.
- gap-analysis.md: Spryple vs our Spyrl PRD.
0. Session plan (≈ 2 hours, or two 1-hour sessions)
| # | Block | Time | Goal | Section |
|---|---|---|---|---|
| 1 | The product in five minutes | 5 min | Everyone knows what Spryple sells and to whom | §1 |
| 2 | How the product is organised | 10 min | Login, roles, menus, breadcrumbs | §2–§3 |
| 3 | Core HR: Employee Management | 15 min | Masters, onboarding, HR policies | §4.1 |
| 4 | Attendance | 15 min | Capture channels, requests, shifts, reports | §4.2 |
| 5 | Leave | 10 min | 10 leave types, rules, approvals | §4.3 |
| 6 | Payroll | 15 min | Pay groups, statutory items, payroll run, payslip | §4.4 |
| 7 | Exit, Claims, Timesheet, LMS | 15 min | Lifecycle and add-on modules | §4.5–§4.8 |
| 8 | CRM Field Force & mobile apps | 15 min | GPS, pipeline, travel; the 4 apps | §4.9–§4.10 |
| 9 | End-to-end flows | 10 min | How modules hand off to each other | §5 |
| 10 | Teach-back and quiz | 10 min | The team explains it back | §9 |
Presenter tip: keep spryple-feature-tree.md open in a second window. Every claim below can be traced to a breadcrumb in it.
1. The product in five minutes
- What it is: an HR + payroll + field-sales suite for Indian SMEs. The vendor is Devorks Solutions Pvt Ltd [SS], and the product is hosted on AWS (per the marketing site).
- Product line:
- SprypleHR: web + mobile HR and payroll.
- SprypleLite: face-recognition attendance + simple salary, for micro-businesses.
- SprypleCRM: field-force tracking + sales pipeline, branded "Sales Pro" in the app [SS].
- SprypleLMS: learning.
- Positioning: "AI-powered attendance and payroll software", with face detection, live tracking of field staff, "easy to use".
- Web modules (9): Employee, Attendance, Leave, Payroll, Exit, CRM Field Force, Claims, Time Sheet, LMS, plus a Super Admin dashboard.
- Mobile apps (4): Spryple HCM ("Spryple HR"), Spryple Lite, Spryple CRM, and Claims, which lives inside the CRM/HCM app shell [SS].
- Indian specifics everywhere: EPF, ESI, Professional Tax, TDS, gratuity, Variable DA, sandwich leave, comp-off, the IFSC bank master, and the Apr–Mar financial year.
2. How the product is organised
2.1 Login and navigation
- Every login (web and all apps) asks for Company Code + Username + Password. That means one shared multi-tenant deployment, with tenants identified by company code.
- After login, the main dashboard shows an employee card, Announcements and Alerts. For example, "dd-mm-yyyy – Attendance not recorded" appears with quick attendance and leave request icons [SS].
- A left icon rail lists the modules. Inside a module, the side menu is grouped by role: an Employee group first, then Admin, HR Manager, Manager, Finance Admin, Finance Manager, Sales Manager, Sales Admin and SuperAdmin groups, depending on the user's roles [SS].
- A chatbot widget and a help icon appear in the header [SS].
2.2 How the Help Center is organised (breadcrumbs)
Help
├── For Super Admin → Dashboard · CRM · Attendance · Payroll · Time Sheet
├── For Admin → LMS · Employee · Attendance · Leave · Payroll · Exit · CRM · Claims · Time Sheet
├── For Managers → Exit · LMS · Employee · Attendance · Leave · Payroll · CRM · Claims · Time Sheet
├── For Employee → Exit · LMS · Employee · Attendance · Leave · Payroll · Sales CRM Web · Claims · Time Sheet
├── Mobile App → Claims · Spryple HR (HCM) · Spryple Lite · Sales CRM Mobile
└── LMS Instructor → Course Builder · Dashboard · Reports
Breadcrumb format used in all our documents: Help › Audience › Module › Screen. Example: Help › For Managers › Payroll Management › Monthly Payroll (Generate Payroll).
2.3 Size of each area (screens documented)
| Module | Super Admin | Admin | Managers | Employee | Mobile | Total screens |
|---|---|---|---|---|---|---|
| Employee Management | — | 20 | 10 | 4 | — | 34 |
| Attendance | 5 | 13 | 30 | 23 | (in HCM/Lite) | 71 |
| Leave | — | 15 | 17 | 10 | (in HCM/CRM) | 42 |
| Payroll | 1 | 13 | 29 | 4 | (payslip) | 47 |
| Exit | — | 4 | 3 | 1 | — | 8 |
| CRM Field Force / Sales CRM | 16 | 17 | 21 | 21 (web) | 50 (CRM app) | 125 |
| Claims | — | 3 | 2 | 3 | 16 | 24 |
| Time Sheet | 3 | 6 | 11 | 5 | — | 25 |
| LMS | — | 3 | 3 | 5 | — | 11 (+4 Instructor) |
| Dashboard / apps | 1 | — | — | — | HCM 25, Lite 20 | 46 |
Takeaway: Attendance, Payroll and CRM carry most of the product's weight. Managers (HR, Finance, Reporting and Sales managers) do most of the operational work.
3. Roles: who does what
| Spryple role | Where it appears | What they do |
|---|---|---|
| Super Admin | For Super Admin | Org-wide dashboards and reports. It is a tenant role (company owner), not a vendor role |
| Admin (HR Admin) | For Admin | Sets up masters, shifts, holidays, checklists, announcements, credentials and the 48 HR policy rules |
| Finance Admin | For Admin › Payroll | EPF/ESI setup, pay schedule, pay groups, bank master, payroll policies, VDA, arrears |
| HR Manager | For Managers › Employee / Exit | New hires, the directory, onboarding checklists, document approval, induction, separation approvals, termination |
| Finance Manager | For Managers › Payroll / Claims | Assigns pay groups, generates payroll, statutory reports, TDS, variable pay, approves claims and advances |
| Manager (Reporting Manager) | For Managers › Attendance / Leave / Time Sheet | Approves requests; configures shifts, rotations and week-offs; acts "on behalf" of the team |
| Sales Admin / Sales Manager | For Admin / Managers › CRM | CRM masters / GPS monitoring, pipeline, travel verification, device approvals |
| Employee / Sales Executive | For Employee, Mobile | Self-service; field staff punch with a photo and log clients and activities |
| Receptionist | Mobile (HCM, Lite) | Front-office check-in/out on a shared device ("Front Office" in HCM, "Front Desk" in Lite [SS]) |
| LMS Instructor | LMS Instructor | Builds courses, views the dashboard and reports |
Explain this pattern to the team: a user can hold several roles, and each role adds a menu group inside a module. Spryple's help never documents the permission model itself. The "Roles & Permissions" page is a copy of "Users Login", and its screenshots are the same image files.
4. Module walkthroughs
For each module: purpose → screens by role → key flows → key rules → reports → gotchas. The exhaustive list of every option is in the feature tree.
4.1 Employee Management (Core HR)
Purpose: company masters and the employee record, from new hire to active employee.
Admin screens (Help › For Admin › Employee Management › …):
| Screen | What to say about it |
|---|---|
| Company Information | Edit, Save or Cancel the company profile |
| Department, Designation | Add, edit inline, Active/Inactive; duplicates are not allowed; to deactivate one, first transfer its employees |
| Work Location | Address and map pin; branch short code; Prefix + Seed drives employee-ID generation (the same prefix shares one sequence across branches; different prefixes give per-branch sequences) |
| Company Logo | jpg/png, ≤ 1 MB, shown in the header |
| Shift → Shift Timings → Grace Period → Overtime duration | Name; start/end (hours auto-computed); grace in/out; "lates more than N → deduct X leave"; minimum work hours |
| Holidays | Branch, date, Public/Optional, name; no duplicate date per branch |
| Checklist | Onboarding or Offboarding items per department. Each item has an approver [SS] |
| Induction | Program types (e.g. HR policies) |
| Announcements | Topic, title, publish window. Statuses: Draft → Published → Completed / Cancelled, with Stop and Republish |
| Messages Master | Edit every success/error message on every screen |
| Users Login | Admin sets the username; the password defaults to "Welcome1!" and is emailed in plaintext [SS] |
| Roles & Permissions | Undocumented (a copy of Users Login) |
| Onboarding Settings | Toggle auto-reminders; toggle probation (months) |
| HR Policies | 48 numbered rules: password complexity (1–9), reminders, probation and notice (10–15), default week-offs (16–18), auto shift assignment (19–21, 25–26), late → leave deduction (22–24), half/full-day hours (27–28), paid permission (29), flexible shift (30–31), regularization (32–33), employee self-edit (34), default punch-out (35), dept–designation mapping (36), backdated termination (37), lunch, tea and graces (38–42), extra-day pay (43–45), week-off absence penalty (46–48) |
| Employee Password Reset | Reset username, password or both. The admin can see the existing password (eye icon) [SS] |
| Department Designation Mapping | Limits designations per department (when Rule 36 = Yes) |
HR Manager screens (Help › For Managers › Employee Management › …): New Hires (Hired/Joined), Employee Directory (tabs: Personal, Contract/Promotions, Experience, Bank, Education, Documents [SS]), Onboarding Pending Checklist, Document Approval, Induction Program, Employee Reports (column chooser), Excel Upload.
Employee screens: dashboard (this month's attendance + leave balance), My Profile, Onboarding checklist, Edit Profile (with photo), Change Password.
Key flow: hire to first login
- The HR Manager adds a new hire (name, personal email, hired-on and joining dates, designation, mobile, emergency contact) [SS].
- The employee gets a pre-onboarding link that expires in 24 h [SS], then fills in personal, family, education and experience details and uploads documents.
- HR clicks Joining Formalities, completes work info (role, location, department, reporting manager, notice period), then bank and contract details.
- HR approves or rejects documents (each outcome is emailed; there is a re-upload loop). Documents HR uploads are auto-approved.
- HR ticks the onboarding checklist. When every item is done, No Due is enabled and the status moves Pending → Completed.
- The Admin is emailed to create credentials, does it manually, and the employee receives the credentials.
Gotchas to mention:
- HR policy changes only affect newly created employees.
- Probation and notice period are configured in two places each (settings vs rules).
- Several rule descriptions are copy-paste errors (Rule 2, Rule 20).
4.2 Attendance
Purpose: capture presence, apply shift rules, and feed payable days, lates, overtime, extra days and penalties into payroll.
Capture channels:
- Biometric devices (Admin maps the device ID to the employee ID: Mapping ID's)
- Web and mobile attendance requests
- HCM app self check-in with face, inside a per-branch geo-fence radius (e.g. 200 m) [SS]
- Receptionist front-office check-in
- CRM app punch with photo
- Manager Excel upload (the template comes from the vendor's implementation team)
Punches carry a source (Lite / CRM / mobile app), a location and photos [SS].
Day-status codes [SS]: P Present · A Absent · HD Half Day · W Week-off · H Holiday · L Leave · WP Week-off Present · HP Holiday Present · HL Half-day Leave. Half days count as 0.5.
Employee screens (Help › For Employee › Attendance Management › …):
- Dashboard: calendar, first in / last out, current and next shift
- Attendance Request: work types WFH, WFO, On-Duty, Work From Remote Location, with half-day options
- Monthly Detail Report
- Shift Change Request: needs an assigned shift
- Request Permission: short leave in minutes, one per day
- Attendance Regularization: days with a check-in but no check-out. The employee adds the out time or converts the day to leave
- Summary, Late, Missed Punch and Extra Days & Penalty reports
Manager screens (Help › For Managers › Attendance Management › …, 30 screens):
- Approvals, with three entry points (team widget, dashboard, Pending Approvals) and Approval History
- Request on behalf (auto-approved)
- Shift configuration, Shift rotation sequences, Assign/Reassign rotation, Week-off configuration
- Approve Shift Change: the manager can swap shifts between employees
- Approve Permission and Permission History
- Manager Attendance Regularization: full-day and half-day lists, with bulk conversion to attendance or leave
- Regularization Approval (bulk)
- Reports: Summary, Detailed, Late, Shift-wise, Punch Summary, Missed Punch, Current Day, Overtime, Extra Days & Penalty
Admin screens:
- Monthly Attendance, Monthly Shifts, Attendance Summary, Current Day, Punch Summary and Missed Punch reports
- Mapping ID's
- Attendance Messages Master
- Shift config, Shift-wise report, Week-off config
- Extra Days Slab configuration (per designation: min/max days worked → eligible extra days)
- Applicable Designations for Penalty
Super Admin: the same five branch-wise reports. Monthly Attendance is a day-by-day grid using the status codes above [SS].
Gotchas:
- Overtime is simply "hours beyond shift hours", with no approval step.
- When multiple punch sources exist, break time is not computed [SS].
- The Missed Punch report only works when HR Policy Rule 35 = Yes.
- No liveness or anti-spoofing is visible in face capture [SS].
4.3 Leave
Admin › Leave Policies:
- Common rules: sandwich over weekends (Fri+Mon); sandwich over holidays; past-dated leave window; emails on submit/approve/reject; leave cycle Apr–Mar or Jan–Dec; maximum optional holidays.
- 10 fixed leave types, each with its own numbered rules. Types can be activated from a pool or deactivated:
| Type | Rules worth remembering |
|---|---|
| Casual | Annual quota; credit frequency (monthly/quarterly/half-yearly/yearly); max per instance; minimum service; advance notice; lapse days; lapse → perks |
| Sick | Quota; frequency; document required above N days |
| Comp-off | Earned by working week-offs/holidays; minimum hours; backdated window; expiry days |
| Loss of Pay | Only the sandwich flags |
| Maternity / Paternity | Minimum service; gap between terms (years); maximum times; days per term. Eligibility is by gender + marital status (we drop this) |
| Wedding / Bereavement | Maximum times; days per term (Wedding also has a notice period) |
| Earned | Quota; frequency; carry-forward cap; times per year |
| Advanced | Borrow against monthly-accruing CL, SL or EL (choose one) |
Employee: dashboard (balances, calendar, holiday list), Leave Request (half days, auto count, Contact + Emergency Email [SS]), Leave History (edit or delete before approval; cancel future approved leave; the status becomes "Cancel Submitted" [SS]), Balance, Comp-off Request (only week-off and holiday dates are selectable), Company Leave Policies (read-only), Optional Holiday Request.
Manager: calendar; pending leave, comp-off and cancellation approvals; leave and comp-off history (Approved / Utilized / Expired); employee-wise, summary and Payroll reports (approved, LOP and absent counts); on-behalf leave, comp-off and optional holiday (auto-approved); optional-holiday approval.
Gotcha: policy edits apply only to new employees, and every Edit-button screenshot is the same image reused across leave types.
4.4 Payroll
Finance Admin (Help › For Admin › Payroll Management › …):
| Screen | Key points |
|---|---|
| Finance Dashboard | Salary, EPF, ESI and PF by month and department |
| EPF | Employee and employer contribution, admin charges, EDLI |
| ESI | "Include employer contribution in CTC"; ESI numbers by state |
| Pay Schedule | Same or different payroll and leave windows (e.g. 25th → 24th); basis = actual days in month or organisation working days |
| Pay group + configuration | Name + CTC range + earnings/deductions → each component as % or flat → status Configuration in Progress → Active |
| Bank Master | Bank, IFSC, account, and Is EPF / Is ESI / Is PT flags |
| Payroll Policies (14 rules) | Advance-salary instalments and cooling-off; OT in salary; gratuity act and monthly gratuity; VDA; absent = LOP; dynamic payroll processing; ESI/EPF independent of LOP; minimum OT hours; variable-pay frequency; proportionate week-off deduction after N LOP days; extra-day payment |
| Variable DA | CPI points, rate per point, effective date |
| Arrear Distribution / History | Arrears per employee → Pending/Paid → shown on the payslip |
Finance Manager (29 screens):
- Assign Pay Group: enter CTC → choose a matching pay group → CTC breakdown popup.
- Reassign: new CTC with the same or a new group.
- Monthly Payroll: choose FY and month → select employees → Calculate Salary → payslips are published.
- Reports: Monthly Payroll (bank PDF), EPF (for the portal), ESI, PT (by state; slab view), Employee Payments, Leave Balance, Detailed Payroll, Employee Pay Group List, Advance Salary, Payable Days.
- Deductions and salary entries: Other Deductions with pay-group mapping, Bank-wise Salary Summary, TDS Distribution (manual amounts), Variable Pay Distribution and Schedule (monthly share or lump sum).
Employee:
- Dashboard (payslips, EPF/ESI)
- CTC History (by duration period [SS])
- Pay Slips [SS]: UAN, ESI and PAN numbers, bank, leave panel, earnings, deductions, LOP amount, arrears, net in words
- Request Advance Salary (≤ gross; months to recover; recovery tracking [SS])
- IT Declaration and Form 16 menus exist but are undocumented [SS]
Super Admin: the Employee Pay Group List only.
Gotchas:
- No payroll lock, approval or reversal step is documented.
- Statutory outputs are "reports", not portal files.
- TDS is typed in manually.
- Gratuity shows as an employee deduction on the sample payslip [SS].
4.5 Exit
- Admin: Offboarding Settings (reminders, notice period), Termination Category, Reason for Separation.
- Employee: Separation, with a retention letter shown before Proceed [SS]. Form fields: exit date, reason, notes; relieving date = applied date + notice [SS]. It can be edited or cancelled before approval.
- HR Manager: Separation Pending Approvals (approve with the final exit date), Offboarding Pending Checklist (No Due → Completed), Termination (employee + category → termination checklist).
- Gotcha: no full-and-final settlement, exit interview or relieving letter is documented.
4.6 Claims
- Employee (web/mobile): a claim holds one or more bills (type, bill number, date, amount, image ≤ 2 MB [SS]) plus a description. The claim ID looks like
CL_GEN_<company>_<n>[SS]. Tabs: Submitted / In Progress / Paid / Rejected. - Manager: verify (bills can be rejected individually; there is a verified amount). Tabs: Pending / Verified / Approved / Paid / Rejected. Claim Report.
- Finance Manager: approves verified claims → marks them Paid. Dashboard: count by status, settlement ratio, previous-vs-current scorecard, paid amount by reimbursement type.
- Gotcha: there are no policy limits, and payout happens outside payroll.
4.7 Time Sheet
- Admin: Client, Project, Assign Team, Task and Project Roles masters.
- Employee: dashboard (assigned vs completed tasks); Submit Timesheet (date, project, task, description, hours, %, task completed, cumulative hours [SS]); Summary Report.
- Manager: dashboard (active projects, assigned employees, bench count, estimated vs consumed hours); Task, Assign Task, Pending Approvals (bulk), History, Defaulters with Send Notification, All History, Summary.
- Super Admin: dashboard, Summary, Effort Variance = (actual − planned) / planned [SS].
- Gotcha: a rule limiting timesheet hours to attendance hours is referenced but missing from the HR Policies list.
4.8 LMS
- Instructor: Course Builder (title, tags, description, difficulty, category, prerequisites, image → Module › Section › Content → Review → Submit); Dashboard; Reports.
- Employee:
- Course Library: filters by department, difficulty, instructor and status [SS].
- The course player has video and resources; assessments are MCQ with mark-for-review and a pass/score [SS].
- Learning Sphere: streak, leaderboard, and tabs Enrolled / Assigned / Recommended [SS].
- Achievements: badges APPRENTICE → SCHOLAR → MENTOR → GUIDE → PATHFINDER → EXPERT, plus certificates with an ID [SS].
- Admin / Manager: dashboard, Configurations (attributes), Reports.
4.9 CRM Field Force / Sales CRM
- Sales Admin masters: Demo Status, Status Master, Client Associate Type, Qualifications, Specializations. Sample data such as Doctor / MBBS / Cardiology [SS] points to pharma and medical-rep sales.
- Field executive (mobile/web):
- Punch with a photo (name and reverse-geocoded address shown).
- Add Client (organisation, contact, address, expected price, photo) → lands in Leads.
- Add Activity: type VISIT / CALL / MESSAGE / MAIL, follow-up date and time, demo status, status. A final price is required when Won.
- Client Associates.
- Client Payments: method (CASH/CARD), collected amount, pending amount [SS].
- Travel approvals; leave.
- Two pipeline views:
- By activity: Leads → Call for Demo → Demo Pending → Demo Completed → Future Leads.
- By status: Interested / Follow-up / Won / Lost / Not Interested.
- Lead age colours (0–7, 8–14, 15+ days) [SS].
- Sales Manager:
- GPS Monitoring: map, battery %, punched-in/out counts. Two modes: Point-to-Point and continuous GPS Monitoring [SS].
- Clients (with reassignment), Clients Report, Employee Activity Report (visits, km travelled), Tracking Log (stay and travel durations).
- Device Approvals (a new phone needs approval).
- Team Travel Approvals: Pending → Verified (manager, can revise km [SS]) → Approved (finance) → Claimed; amount = km × rate [SS].
- Assignments report (Cancelled, Exceeded [SS]).
- Location check: activities show whether the client location matched [SS].
- Gotcha: the CRM duplicates leave and shift screens, and its pipeline stages are hard-coded and demo-centric.
4.10 The four mobile apps
| App | Who | What |
|---|---|---|
Spryple HCM (com.hrmslatest) | Employee, Manager, Receptionist | Self check-in/out (face), attendance requests and approvals, Today Attendees, Capture Employee Image, Configure Location (geo-fence radius), leave and comp-off and approvals, payslips, Rewards & Recognition (Birthday, Outstanding, Job Well Done… [SS]) |
Spryple Lite (com.hrmslatestlite) | Manager, Receptionist, Employee | Add employee (name, mobile, monthly salary, shift), face enrolment, attendance and payroll reports (salary, PT, presents, payable salary). Not updated since Aug 2024 [SS] |
Spryple CRM (com.crmspryplesp) | Field executive, Manager | Everything in §4.9, plus leave; the manager also sees Employee Location and Team Travel |
| Claims | Employee, Manager | A module inside the CRM/HCM shell: Claims History, Claim Request with bills, manager verification |
5. End-to-end flows to whiteboard
- Hire → login: New Hire → 24 h pre-onboarding link → Joining Formalities → documents approved → checklist No Due → Admin creates credentials → employee logs in with the company code.
- Punch → payslip: punches (device, app or kiosk) → day status (P/A/HD/W/H/L…) → requests and regularization fix the gaps → lates → leave deduction, OT, extra days and penalties → payable days in the pay schedule window → Calculate Salary → payslip (LOP, arrears, variable pay, OT, extra days).
- Leave: apply (balance-checked, sandwich applied) → manager approves → it shows on the calendar → the payroll report counts LOP → cancelling a future approved leave needs manager approval.
- Claim: bills → manager verifies (per bill) → finance approves → finance marks it Paid.
- Field day: punch with a photo → visits and activities with GPS → km computed → manager verifies (revises km) → finance approves → claimed.
- Exit: separation (retention letter) → HR approves the exit date → offboarding checklist → No Due → completed. Or HR starts a termination → termination checklist.
6. Status cheat-sheet
| Object | Statuses |
|---|---|
| Attendance, shift-change and permission requests | Submitted → Approved / Rejected; Deleted; Cancelled (permission, after approval) |
| Leave | Submitted → Approved / Rejected; Deleted; Cancel Submitted → Cancelled |
| Comp-off | Approved → Utilized / Expired |
| Optional holiday | Submitted → Approved / Rejected; Deleted |
| Onboarding / offboarding checklist | Pending → Completed (via No Due) |
| Documents | Uploaded → Approved / Rejected (re-upload) |
| Announcement | Draft → Published → Completed / Cancelled (Stop, Republish) |
| Pay group | Configuration in Progress → Active |
| Arrears | Pending → Paid |
| Advance salary | Submitted → Approved / Rejected; recovery: Not Started → … |
| Claims | Submitted / Pending → Verified → Approved → Paid; Rejected |
| Travel | Pending → Verified → Approved → Claimed; Rejected |
| Separation | Submitted → Approved / Rejected |
| CRM client | Leads / Call for Demo / Demo Pending / Demo Completed / Future Leads; Interested / Follow-up / Won / Lost / Not Interested |
| Timesheet | Pending → Approved / Rejected; Defaulters (not submitted) |
| Induction | Scheduled (→ edited or cancelled, with emails) |
7. Spryple vocabulary
| Term | Meaning in Spryple |
|---|---|
| Company Code | The tenant identifier typed at every login |
| Pay group | A salary structure selected by CTC range |
| Pay schedule window | The attendance/leave period used for a salary month (e.g. 25th → 24th) |
| Sandwich leave | Week-offs or holidays between leave days are counted as leave |
| Comp-off | Leave earned for working on a week-off or holiday; it expires |
| Permission | Short leave in minutes (one per day) |
| Regularization | Fixing missed or single punches, by adding the out time or converting to leave |
| Extra days | Paid extra for working week-offs or holidays (slabs per designation) |
| Penalty days | A deduction for absence around a week-off or for lates |
| Dynamic payroll processing | A payroll-policy option with a leave threshold (undocumented detail) |
| Variable DA | A dearness allowance linked to CPI points |
| Demo Status / Status Master | The two CRM status systems |
| Lead age | Days since a client was added, colour-coded |
| Travel approvals | km-based reimbursement records from GPS tracking |
| Front Office / Front Desk | Receptionist check-in on a shared device |
| No Due | The checklist sign-off that completes onboarding or offboarding |
8. Known issues and quirks (worth flagging to the team)
- Security:
- Default password "Welcome1!" is emailed in plaintext.
- Admins can view existing passwords.
- Roles & Permissions is undocumented.
- Configuration:
- Rules are duplicated (probation, notice, default shift, late deduction).
- Policy changes skip existing employees.
- Leave types and CRM stages are fixed.
- Documentation defects:
- 16 found in total (see spryple-analysis.md §17).
- Examples: the separation rejection path says "approved"; the Admin "Claims" page is actually for the Finance Manager; the Advance Salary Report section is empty.
- Product fragmentation:
- 4 apps.
- Lite is a separate product that is no longer maintained.
- The Claims app is installed by searching "Spryple CRM".
- Data quality signals in screenshots:
- Late hours of 672:00:00.
- A payslip formula that omits arrears.
- Test environments on raw IPs.
9. Teach-back and quiz
9.1 Teach-back prompts
Ask team members to explain each of these in their own words:
- Walk through what happens between "HR adds a new hire" and "the employee's first login". Which step is manual and risky?
- An employee punched in but not out. List every way that day can be resolved, and by whom.
- How does Spryple decide which salary structure an employee gets? What breaks with that approach?
- Explain the sandwich rule with an example: leave taken Friday + Monday, with Saturday/Sunday off.
- Trace a field executive's day, from punch-in to a reimbursed travel amount.
- Which Spryple settings live in two places, and why is that a problem?
9.2 Quick quiz (answers below)
- What three fields does every Spryple login require?
- Name the four attendance work types.
- How many leave types are there, and can a tenant add a new one?
- What does Prefix + Seed on a work location control?
- Who can generate payroll?
- What are the two pay schedule bases for computing salary?
- What happens to a manager's "request on behalf of employee"?
- What are the two GPS modes in the CRM?
- What makes the "No Due" option available?
- What is the claim approval chain?
- What does WP mean in the attendance grid?
- How long is the pre-onboarding link valid?
Answers:
- Company Code, username/email, password.
- WFH, WFO, On-Duty, Work From Remote Location.
- 10 fixed types (activate or deactivate only); no custom types.
- Employee-ID generation: a shared or per-branch sequence.
- Only the Finance Manager.
- Actual days in the month, or organisation working days.
- It is auto-approved.
- Point-to-Point and continuous GPS Monitoring.
- All checklist items being completed.
- Employee → Manager verifies → Finance Manager approves → Finance Manager marks Paid.
- Week-off Present (worked on a week-off).
- 24 hours.
10. Where to go next
- Every option, with its breadcrumb: spryple-feature-tree.md
- Why we would build it differently: spryple-analysis.md
- What Spyrl covers, improves, defers or is missing: gap-analysis.md
- Raw crawl evidence:
research/raw/e2e-crawl/(E2E engine output and its_manifest.json)
Synced from
/research/reverse-kt.mdin the repository root. Edit the root file, not this page.