What Should an Air Monitoring Grant Leave Behind?

That is the approach we want to develop with funders at the Open Air Foundation. Support local monitoring, while explicitly funding the shared designs, measurement methods, training and maintenance that future projects can build on. Not another central platform everyone must join, but a stronger starting point for the next community.

A useful project can still leave a gap

Muswellbrook in Australia shows why continuity deserves attention before equipment is installed. According to the New South Wales Government's case study, the council deployed three commercial sensors to investigate dust pollution. The project increased staff knowledge, but the devices were recalled after 20 months. Once project funding ended, the council could not cover continuing subscriptions, and the proprietary devices could not be reconfigured for a private network.

The council owned its data and could download it. Difficulties with public sharing involved limited IT capacity and uncertainty about interpreting and communicating readings, not a ban on releasing the data. The provider's support had also been valuable during the project. Open source would not automatically have solved the council's funding or capacity problems.

For me, the case raises two distinct tests. Can this community keep its network useful? And what could another community build upon? A network might operate for years yet leave little that others can reuse. Conversely, a published design is little consolation to residents if their own network stops working. Both objectives need funding.

The next project should not start from zero

The opportunity cost is not just the equipment that becomes unusable. It is also the development work that another team has to repeat. If a grant pays for a useful calibration procedure, a data-export tool or training materials, I would like the next grant to finance adaptation and local capability rather than recreate the same foundations.

That is not a claim that every open project will be cheaper. Manufacturing, validation, maintenance and local expertise still cost money. The question is which work genuinely needs to be done again, and which can become a shared asset.

OpenAQ already aggregates and harmonises air quality data from many sources. We should strengthen useful infrastructure like this, not build a competing platform simply because a new grant can fund one. The missing connections matter too, from the instrument producing a reading to the people deciding what it means.

Make reuse a practical capability

A reusable package should be more than a database of lessons learned. I mean a maintained collection of compatible resources, with identifiable versions and people responsible for them. That could include hardware designs and firmware, measurement and quality-assurance protocols, documented data interfaces, repair guidance and training materials that local teams can adapt.

Imagine a second community adopting a documented method for comparing its sensors with reference equipment. It should receive the procedure, the software version used, the conditions tested and the limitations discovered. Its team would still need to check performance locally. But it should not have to reverse-engineer what the first team did before it can begin.

Problems belong in that shared knowledge too. A correction that did not transfer well, a component that became hard to obtain, or instructions that confused new users could help another team avoid the same difficulty. Making that experience reusable requires time to document it and someone to review subsequent changes.

The practical benefit is greater choice. A local partner should be able to change its data platform, seek support from another provider or replace a component without discarding the entire investment. That is a capability to demonstrate, not something an open-source label guarantees.

Pay for the work that keeps it useful

Maintenance must be priced into the grant from the beginning, not left as an unfunded expectation. The local network needs an operating budget. Shared tools need people testing updates, reviewing measurement methods, maintaining documentation and helping users. These are related responsibilities, but they are not the same budget.

A grant should identify who maintains each shared resource, how changes are reviewed and how continued support will be financed. An independent team attempting to use the release would be a valuable test. If it can only succeed because the original developer quietly fixes everything, we have learned something important about the support still required.

The Open Air Foundation is distinct from AirGradient, the monitoring technology company. Our proposed partnerships should widen local options, not make participation depend on buying from AirGradient or relying on the foundation indefinitely. Governance matters as much as publication. Partners need a clear way to raise problems, contribute improvements and understand who decides what becomes part of the maintained release. That should include the ability to leave a partnership without losing access to the underlying tools.

A better test of a grant

I would evaluate a first partnership against a short checklist agreed before it starts.

• Local continuity. A responsible local team, operating budget and credible plan for servicing equipment and retaining data access.
• Independent reuse. Another team can adopt the documented tools, with the adaptation effort, costs and support required recorded honestly.
• Scientific usefulness. Measurement limitations and quality checks are documented, and local validation is not replaced by assumptions about performance elsewhere.
• Continued stewardship. Named maintainers, a review process and a funding plan for the shared resources beyond the initial deployment.
• Practical use. Evidence that the measurements informed a documented decision or action, rather than treating installed monitors as the final outcome.

This is an investment approach to develop and test with partners, not a claim of proven savings or guaranteed health outcomes. One well-documented example of independent reuse would tell us more than another deployment count alone.

If you fund air quality monitoring, I would like your next grant to do two things well. Help a community build the evidence and capability it needs, and leave maintained tools that someone else can build upon. At the Open Air Foundation, we would like to shape that first partnership with you.