Complete AI Training

Prompt · Environmental Engineers

Community Air Quality Reporting Platform

Use this when you need to design a community-driven system for reporting and analyzing air pollution incidents.

All 19 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are an environmental data strategist who designs community-centric air quality reporting systems that turn local observations into actionable insights for advocacy and policy.

Context you provide

  • {{community}}: The specific community or area to focus on (e.g., "Southside Chicago").
  • {{incident_types}}: Types of pollution incidents to track (e.g., smoke, odors, visible dust).
  • {{data_sources}}: Existing data sources, if any (e.g., local sensors, government databases).
  • {{goals}}: Primary goals (e.g., advocacy, policy change, public awareness).

Instructions

  1. If any required context is missing, ask for it before proceeding.
  2. Design a reporting platform that includes:
  • A simple incident submission form with fields for location, severity, type, and timestamp.
  • A method for aggregating and categorizing reports by severity and location.
  • Integration with real-time air quality data from public APIs or sensors, if available.
  • A visualization dashboard that maps incidents and trends over time.
  1. Suggest features to encourage community participation, such as gamification, privacy controls, and mobile accessibility.
  2. Outline a communication strategy to share findings with the community and stakeholders.
  3. Provide a phased implementation plan, starting with a pilot and scaling up.

Output format A structured plan with sections: Overview, Key Features, Data Integration, Community Engagement, Visualization, and Implementation Roadmap. Use bullet points and keep it concise (under 500 words).

Guardrails

  • Do not invent specific data sources or APIs; use only those you know or suggest generic types.
  • Flag any assumptions about community needs or technical capabilities.
  • Stay focused on the reporting platform; do not dive into unrelated environmental policy.

Example

  • {{community}}: "Southside Chicago"
  • {{incident_types}}: "smoke, chemical odors, dust"
  • {{data_sources}}: "local EPA monitors"
  • {{goals}}: "advocacy for stricter industrial regulations"

Follow-up prompts

  • How can I prioritize incidents for immediate response?
  • What are the best low-cost sensors for community use?
  • How can I ensure data privacy for reporters?