Q QlockinPRODUCT GUIDE
QLOCKIN / PRODUCT CONCEPT

One product, four surfaces.

The right interface for an instructor in motion, an owner at a desk, and a family checking a schedule.

FLUTTER

iOS & Android

Today’s sessions, attendance, QR scanning, offline sync, participant lookup, package balance and quick payment recording.

NEXT.JS

Owner web app

Calendar, roster, imports, packages, payments, reports, staff, organisation settings and software subscription.

Open the workspace →
RESPONSIVE WEB

Guardian portal

A signed link shows schedules, attendance, balances and payments for one or more children. No app, no account, no password.

CLOUDFLARE

Backend

Workers and D1 hold everything authoritative: tenancy, entitlements, credit rules and money. Clients render; the server decides.

Release scope

01FoundationRepository, authentication, multi-tenancy, RBAC, entitlements.
02OperationsParticipants, guardians, programs, groups, sessions, calendar.
03AttendanceAttendance screen, mark all present, QR, offline sync.
04CommercialPackages, session credits, manual payments, payment abstraction.
05CustomerGuardian portal, balances, attendance and payment history.

Billing is architected from the beginning but can stay switched off: the schema, entitlement engine, provider abstractions and billing UI all exist, so turning monetisation on is a flag and a set of secrets rather than a redesign.

Not in scope

LMS, homework, grades, payroll, HR, full accounting, ERP, facial recognition, biometric attendance, complex CRM, a dedicated participant app, marketplace, holding customer funds, or speculative AI features.

Where to start

Create a workspace, add one group with a weekly slot, generate a term of sessions, and take attendance. Everything else follows from that loop.

See the plans →