Aveniq

Many schools still track attendance on paper, which makes patterns invisible and reporting slow. Administrators had no reliable way to compare classes, flag absenteeism early, or share records with parents.

I spoke with school administrators and teachers about their daily routine and mapped where the register actually breaks down. The recurring themes were time pressure during morning roll call, weak internet, and the need for one account to manage several arms of a school.

I scoped a multi tenant architecture so each school operates in its own isolated space while sharing one codebase. The roadmap prioritised fast roll call, role based access, and reporting before any secondary features.

The interface favours speed and clarity. Roll call is reduced to a few taps, dashboards use restrained typography and calm colour, and every screen is legible on the low cost devices teachers actually use.

I built the platform on Next.js with a PostgreSQL database, deploying the API layer on Railway and the frontend on Vercel. Tenant isolation, authentication, and attendance aggregation were the core engineering pillars.

The hardest problems were keeping data strictly separated between schools and keeping the experience responsive on unstable networks.

I enforced tenant scoping at the data layer, added optimistic interface states so teachers are never blocked by latency, and designed the schema around the queries the dashboards needed most.

Schools gained a single source of truth for attendance, faster daily operations, and reporting that surfaces absenteeism while it can still be addressed.

Designing for the constraints of local infrastructure first, rather than as an afterthought, produced a product that feels effortless in the field.