as an aside, the unfortunate reality is that no matter what iNat staff do to help address these issues, there will always still be bioblitzes which frustratingly produce lots of low quality data like you describe. As one example:
A few years ago I was asked to help out with a bioblitz. I won’t reveal specific details, but basically it involved 2 or 3 main organisers of the event broadly, and then numerous local organisers each responsible for their own group/location; basically similar to the CNC, but on a much more localised scale. In the several months leading up to the event, which ran across a week or so, I did 3 separate hour long workshops over Zoom for the local organisers, going through a very basic how-to for iNat, both desktop and the app(s), and also doing an extensive run-through of all the dos and don’ts for bioblitzes and iNat broadly from a data quality perspective, touching on all of the things you mentioned, and the stuff that regularly gets discussed in other similar threads. These events were quite well-attended. In addition to me speaking and presenting (where I shared my screen and used iNat live in front of them), there was also lots of question time for the organisers. These local organisers would then ostensibly pass on the information they’d learned to their respective participants.
I then also provided supplementary resources, including written documents and videos (incl. existing material I had made, and custom material I had tailored to this event), to the main organisers who then distributed them to the local organisers, both to cater for people who missed one of my Zoom workshops, and also just provide extra info on top of what I presented.
And yet, when the bioblitz started, there was a flood of low quality records, with many examples of every single thing I told them to avoid/not to do (multiple pics of same individual split across records, multiple species in one record, unmarked cultivated plants, blindly trusting CV suggestions, numerous people uploading pics of the same blurry pot plant, etc etc). I don’t think I could have done much more to prepare them for this event, and yet it seemingly didn’t really make a difference. It was quite a frustrating experience and I felt like I’d just totally wasted my time (and then also felt somewhat guilty for all the dodgy records that were now on iNat).
Now this certainly isn’t a universal experience for me, and is in fact the exception rather than the norm; I’ve directly organised or helped out with many bioblitzes in Australia over the last 5 years, and there have been plenty that ran very smoothly, with diligent local organisers who did a great job at absorbing and passing on all the recommendations and info, and great participants who paid attention and followed them all. But my point is that it’s an inevitability that some bioblitzes will result in these landslides of low quality records.
(note that I don’t disagree at all with the importance of site-derived actions/initiatives/resources, and I’m not saying that just because some bioblitzes turn out poorly despite efforts otherwise that we should just give up and not do anything; I definitely think they’re really important and should be developed and implemented. But just emphasising that the successes + usefulness of these solutions are, frustratingly, sometimes out of the control of iNat staff, plus ambassadors etc, and it’s important to keep this mind)