Ahmed AlsaidyProduct & Systems Engineer
← All projects

For organizations tracking lecture attendance

Attendance management

QR check-in and administrator attendance records. The PTC lecture implementation uses rotating codes and device binding to reduce proxy attendance

PTC lecture attendance interface

PTC lecture attendance interface

The idea

Static QR codes can be forwarded. This implementation combines rotating QR tokens, device binding and an audit trail

System Architecture

How the architecture fits together

Architecture diagram of Nexus Class multi-tenant SaaS, 7 shared Dart packages, and rotating QR clientsARCHITECTURE BLUEPRINT · MULTI-TENANT EDTECH SAAS7 DART PKGS · 30s QR · 187 TESTSWINDOWS DESKTOPStaff & Center AppOffline Cache · QR Check-InTEACHER & STUDENT MOBILEFlutter iOS / AndroidCohorts · Grades · FeesWEB IDE & ANTI-FRAUD QRPortal + 30s Rotating QRDevice Binding · Results7 SHARED DART PACKAGES (MODULAR WORKSPACE)api_client · auth · domain_models · local_cache · realtime · design_system · shared_uiMULTI-TENANT BACKEND · LARAVEL 12 + POSTGRESQL + REDIS + DOCKER / CADDYTenant Isolation GuardBootstrap Roles + Strict ScopeKido & Nexus Schemas48 Migrations + 32-Table ERPAudited Results & PayrollBatch Rollback · Rate Limiting

What it does

What can you do with it?

QR check-in

Students check in from their phones using the session’s displayed QR

Reduce proxy check-ins

Refresh the code every 30 seconds, bind accounts to devices and log suspicious attempts for review

Manage & review

Administrative records and roles with Arabic and English web interfaces

Inside the project

Take a closer look

Select a screen to view it at full size

Implementation

The local project is named PTC-ATTENDANCE. This case shows lecture attendance; shift or payroll rules are separate implementation requirements

Related services

Technical Evaluation · GCC / Remote / Egypt

Building an operational system, rescuing an AI cloud stack, or hiring a Product Engineer on retainer?

Complete the 30-second scope qualifier so our first conversation goes directly into system architecture, milestones, and budget fit.