A neighborhood group is cleaning a small park on Saturday morning. The coordinator wants one internal total for planning and thanking participants, not certificates or official service credit. The group creates a dated HelpHours journal, shares the submission QR code at the check-out table, and reviews entries that afternoon.
Define the cleanup and its honest boundary
The journal is named “Riverside cleanup — 3 August” and covers litter collection, sorting, tool return, and final loading. It explicitly says accepted entries are for the group’s internal summary and do not verify identity or attendance.
Place submission where volunteers finish
The coordinator prints the focused QR code and keeps the adjacent copy link in the group chat. Maya reports 95 minutes of litter collection; Alex reports 60 minutes sorting bags. Each receives a private receipt and both entries remain pending.
Review entries against the event context
The manager recognizes both activities and accepts them. A third 300-minute entry with an unclear activity is left pending while the coordinator asks the group for context. No automatic rule rejects it, and the possible mismatch is not treated as fraud.
Count exact accepted minutes and keep the claim modest
The journal shows 155 accepted minutes and one pending entry. The group may format that as 2 hours 35 minutes, but stores the exact minute total. It calls the result an internal cleanup total, not verified community-service evidence.