case study · EdTech · Hackathon finalist · UNILAG Quality Assurance challenge

WhisperLag

A student who whispers is still speaking.

Role
Full-stack engineering
Timeline
2026
Status
Live
Links
live ↗code ↗
Stack
Next.js 14ExpressPrismaPostgreSQL (Neon)GroqCloudinaryBrevoPWA

An anonymous-by-design quality assurance and feedback platform for UNILAG: students give feedback without an account, and staff get routed, de-noised issues and accreditation-ready reports.

01

The problem

University feedback forms offer an ‘anonymous’ checkbox but still log accounts, matric numbers or IP addresses. Students know this, so they stay quiet, and quality assurance teams make decisions with half the picture.

Who it’s for

UNILAG students, lecturers and faculty heads, and the Quality Assurance & SERVICOM unit.

02

Goals & constraints

Goals

  • Anonymity enforced by the architecture, not promised by a checkbox.
  • Let students track what happened to their feedback.
  • Cut the noise so staff act on real issues.

Constraints

  • Patchy campus networks
  • Three very different user groups with different powers

03

Approach

  1. 1.

    The Whisper Lock

    The feedback table has no user column at all. Students never sign up. Each submission gets an unlinked reference code (WL-YYYY-XXXXXX) for tracking, and uploaded evidence is stripped of EXIF/GPS and renamed.

  2. 2.

    AI triage for staff

    Groq routes each message to the right course, lecturer and department, and isolates low-substance or spam submissions into a ‘noise’ filter.

  3. 3.

    Reports in minutes

    Accreditation summaries, department snapshots and 14-day trend reports are drafted by AI and exported to PDF or CSV.

04

Architecture

A mobile-first, installable PWA with an Express API behind it.

  1. 01Next.js 14 PWA (whisper, track, polls, evaluations, faculty, admin)
  2. 02offline outbox → queues submissions → flushes on reconnect
  3. 03Express API (Zod, JWT, Helmet) with three-tier RBAC
  4. 04Prisma → Neon Postgres, immutable audit log
  5. 05Groq triage · Cloudinary evidence · Brevo email alerts

05

Key decisions

Privacy by schema

If the column doesn’t exist, it can’t leak. That one decision made the anonymity promise believable.

Email over HTTP, not SMTP

Cloud hosts block SMTP ports, so alerts go through Brevo’s HTTP API on port 443.

!

Challenges

Anonymity vs accountability

Students need to be invisible; moderators must not be. Staff actions are written to an immutable audit log.

✓

Outcome & lessons

  • 4th place at the UNILAG Quality Assurance challenge.
  • Live, installable PWA with demo staff accounts.

What I learned

  • Trust is designed into the data model.
  • Offline-first is a must on campus.

What’s next

  • Integration with the official student portal and Moodle
next projectContinuum→