Written and maintained by Jeremy Roberson. Published ; reviewed and expanded .
Read the editorial policy for sourcing and correction standards.
What this guide helps you do
A reporting tool should not only work for people who love apps. It should also work for neighbors who know the place but do not know the technology. Plain language, fallback options, and patient instructions make reports better.
- Use this when
- Use this guide when helping a neighbor, family member, volunteer, or first-time visitor report a litter location.
- Best outcome
- The person submits a clear report using the details they can provide without feeling blocked by GPS, photos, or unfamiliar form fields.
- Next step
- Start with location words first, then add photo or pin details only if they are comfortable and safe.
Start with what the person already knows
Many people know the road, landmark, store, church, bridge, or neighborhood better than they know a map pin. Ask them to describe the place in their own words first.
A report can still be useful without perfect GPS. ZIP, road name, cross street, and landmark can guide the next person close enough to check.
Do not make the person feel like the report failed because one technical feature did not work. Use the fallback details.
Explain photos as optional help
Photos are useful, but they should not feel mandatory when a person cannot take one safely or does not know how to upload it. A written report is better than no report.
If helping someone upload a photo, choose the clearest safe image and avoid private details. Do not overwhelm them with multiple uploads.
Let them know a wide photo is often enough. They do not need a perfect close-up.
Use plain field labels and examples
People submit better reports when examples are visible: “near the bridge,” “behind the store,” “bags in ditch,” or “tires near pull-off.” Examples reduce anxiety and guessing.
Avoid jargon when helping someone. Say location, type of trash, amount, and safety concern. Those are easier than technical data labels.
If the form has optional fields, say which ones can be skipped. Optional should mean optional.
Respect privacy and comfort
Do not pressure someone to share more personal information than needed. A litter report should not require a long personal story.
If they are worried about being identified, explain what should stay out of the report: faces, plates, home details, and accusations.
Trust grows when people feel the tool respects their limits.
Keep the follow-up simple
After the report, show the next easy step: check the map later, share the resource page, or send a correction through Contact. Do not give ten instructions.
If they made a mistake, fix it calmly. A confusing first report is an opportunity to improve the site and instructions.
The goal is participation without intimidation. A public cleanup tool should welcome people who have never used one before.
Make the report readable for someone tired or in a hurry
A useful report should not require technical language. Many residents will use the site quickly from a phone, after seeing a mess from a car, while walking, or while helping someone else. Plain words, short sentences, and familiar landmarks make the report easier to understand.
Use the order people naturally need: where it is, what is there, how much there is, what looks unsafe, and what the next step may be. A report that follows that order is easier to scan on mobile and easier for another person to verify later.
Avoid abbreviations that only local insiders understand unless you explain them. A road nickname, neighborhood phrase, or business landmark may be helpful, but it should be paired with a ZIP code, cross street, or public feature when possible.
Accessibility also means not requiring a perfect photo, exact GPS point, or polished writing. A safe, plain report with enough context is better than no report. LitterMeNot should help regular people submit useful information without making the process feel technical or intimidating.
Design the words around real phone use
Many reports will be written on small screens, outside, with poor signal, tired eyes, or limited time. The page should use familiar labels, visible buttons, readable text, and short helper language. A person should not need to understand mapping software or civic jargon to explain a problem.
The report itself should work with imperfect information. If a user knows the ZIP code and a nearby landmark but not exact coordinates, that still has value. If they cannot upload a photo safely, the written description should still be welcomed. The site should guide better reports without making people feel stuck.
Accessibility also means respecting different literacy levels. Plain terms like “road shoulder,” “ditch,” “bags,” “tires,” “near water,” or “too close to traffic” are often better than formal language. The clearer the words, the more likely another person can understand and act.
The simplest test is whether someone else could read the report aloud and find the same spot. If the answer is yes, the report is accessible enough to help even before any advanced map feature or profile tool is involved.