Loading...
CleanLoop connects waste reports, cleanup activity, follow-up observations, and recurring hotspots to make environmental problems easier to understand.
Understand the core problem of blind cleanups and explore the deterministic verification loop step-by-step.
Why traditional waste management cleans the same spots endlessly without solving anything.
The Problem: Standard campus operations treat every report as an isolated ticket. Trash is swept and the ticket is closed, yet 24 hours later, the identical spot is littered again. Facilities teams stay trapped in an endless, expensive cleanup loop with zero visibility into chronic root causes.
How CleanLoop Solves It: CleanLoop fixes this by assigning immutable Hotspot IDs to campus locations and recording the post-cleanup lifecycle. Instead of closing tickets, CleanLoop tracks whether waste returns after cleaning.
A swept area is no longer treated as "case closed". It enters a monitored post-clean observation phase.
All events at Library Gate, Cafeteria, etc. are bound to a single timeline to expose repeated dumping.
Separates one-off accidental litter from locations needing structural bins and schedule changes.
⚠️ Trash returns 24h later unnoticed. Facilities records a “successful job” while the problem festers.
✓ Full persistence. When waste returns post-clean, recurrence is automatically logged.
Traditional waste reporting stops the moment an area is swept. Without follow-up verification, campus teams miss the recurrence cycle.
Trash is swept once, marked "completed", but returns within 48 hours because waste generation sources remain invisible.
Standard reporting systems lack a formal follow-up observation stage to verify whether the location remained clean or accumulated trash again.
Facilities coordinators cannot distinguish an isolated incident from a chronically recurring hotspot that requires structural intervention.
A 5-step deterministic lifecycle ensuring continuous accountability from initial report to hotspot identification.
Student logs in, chooses a predefined hotspot, picks waste category, and uploads photo evidence.
Cleanup Team takes action, logs notes, optionally adds cleanup photo, and marks incident cleaned.
Observation is performed. Is the site still CLEAN or did WASTE_PRESENT return?
Deterministic algorithm calculates repeat incidents post-cleanup for the exact hotspot.
Aggregated hotspot timeline and rankings allow facilities to target chronic locations.
Laser-focused functionality built to prove end-to-end incident tracking without non-essential bloat.
Library Gate, Main Entrance, Cafeteria, Science Block, and Parking Area with fixed geographic references.
Strict permissions enforced at backend API Gateway and Lambda for STUDENT, CLEANUP_TEAM, and ADMIN.
Secure direct-to-S3 photo uploads via presigned URLs. No public bucket exposure.
Cleanup crews capture execution notes and completion timestamps before moving status to CLEANED.
Observers document condition (CLEAN vs. WASTE_PRESENT) to trigger immediate recurrence analysis.
No black-box AI. Transparent rules-based classification (Normal, Monitor, Recurring) based on incident counts.
Serverless, reproducible, and minimal infrastructure defined via AWS CDK / SAM.
User Pool with custom role groups: STUDENT, CLEANUP_TEAM, and ADMIN with JWT authorization.
RESTful routing with Cognito Authorizer dispatching to Node.js/TypeScript serverless functions.
Single-table design supporting incident lookups, hotspot timelines, and recurrence aggregation.
Private bucket with signed PUT/GET links; CloudWatch audit logs for structured request diagnostics.
Moving beyond vanity metrics to actionable recurrence intelligence.
By comparing incident dates directly after verified cleanups, campus administration gets empirical recurrence metrics rather than guessing why bins overflow.
Every report, cleaning activity, and verification audit is stitched together into a chronological log for each campus location.
Track incidents, dispatch cleanup crews, and monitor chronic campus hotspots in real time with CleanLoop.