SA
Sanchalan Docs
Overview

Sanchalan Attendance

BYOD parliamentary attendance system for Rajya Sabha Secretariat — staff, contract, vendor, and member punching from their own phones, with geofencing, device-bound cryptographic signatures, CCS-rules leave engine, and a central audit chain.

At a glance

LayerTechStatus
Backend APILaravel 12 (PHP 8.2)Live · /api/
Web adminBlade + TailwindLive · /admin/
OpenAPI / Swagger UIL5-SwaggerLive · /api/documentation
MobileFlutter 3.22+Source ready · build on dev workstation
DatabasePostgreSQL 16 (sds-dms-postgres-1)Live
Audit pipelineRedis stream → sds_audit PGLive · 19+ events landed
SSO (sb-iam Parichay)OAuth2 PKCEWired, dev mode default

What problem does this solve

The Rajya Sabha Secretariat needs daily attendance for ~2,300 staff across staff/contract/vendor categories, plus selective member-of-parliament tracking. Existing biometric punch posts are fixed locations and don't cover field staff or members. The CCS Leave Rules 1972 are the binding regulation for leave types and quotas.

Sanchalan Attendance replaces the punch posts with a BYOD app:

  • Each phone is one-time-bound to one employee with a P-256 keypair (private key never leaves the device).
  • Each punch is cryptographically signed, geofenced to Parliament campus polygons + Wi-Fi SSID allowlist, and anti-spoof checked (mock location, root, emulator).
  • Leave applications run through a CCS rules engine (CL/EL/HPL/COMMUTED/CCL/RH) with structured per-type day calculation.
  • Every action emits to a central audit chain (sds_audit) with a hash-chained log for forensic immutability.