Guest and campus reporter
Personas
Map, Learn, report, confirm, then follow impact
Guests explore without an account. Campus reporters (often students or staff with a reporter pack) complete verification when they submit, then track what happened.
These packs typically unlock Map, Learn, Report, Impact, and Inbox. Names vary by school. Features stay the same.
Feature map
| Feature | What they do | Where |
|---|---|---|
| Map | Find bins by search, pan, QR, or list fallback | /maps |
| Place sheet | See bin code, waste stream, directions, report CTA | Map sheet |
| Learn | Read short sorting and campus guides | /learn |
| Report | Photos, optional note, verification at submit | /report |
| Confirm | “I’m seeing this too” on an open issue | Report / place sheet |
| Impact | Personal contribution after authenticated reports | /impact |
| Inbox | Closure and status updates | /inbox |
| Profile | Name, matric, department when the school collects them | /profile |
Guest flow (no account yet)
Open Map or Learn. Guests can browse bins and guides freely.
Pick a bin. Search, scan the label, or open a place from the map.
Start Report. Capture clear photos. Drafts can wait if the network is weak.
Verify to submit. Email and campus identity fields your school requires appear only at send.
See confirmation. Wait for success before leaving. Offline drafts sync later.
Campus reporter flow (signed in)
Sign in with the campus identity your school uses.
Report faster when profile fields are already known.
Confirm duplicates instead of opening a second ticket for the same active problem.
Watch Impact and Inbox when jobs close or status changes.
Practice path
- As a guest, file one training report with two photos.
- Sign in (or use a reporter pack account) and open the same bin.
- Confirm the open issue, then open Inbox and Impact.