Develop or test protocols to monitor ecosystems

Send the draft monitoring protocol and the associated sampling schedule to Protocol Lead, Javier Morales, and then to the monitoring technicians, asking for signatures by next Wednesday; check that sampling frequency, QA checks and equipment lists are fully specified before sending.

Before I distribute this monitoring protocol to field techs, make it easy to implement: put the sampling frequency and critical QA checks up front, make the equipment checklist and calibration steps findable, and flag any items likely to make a technician hesitate (special consumables, permit requirements).

A technician told me this morning that the dissolved oxygen meter had no calibration log for the last week. I told Javier I assumed it was done but he wants the evidence; we cannot revisit the whole field season. What is the most likely lapse and the quickest protocol tweak or instruction to give so technicians can produce acceptable QA evidence going forward?

Over several monitoring cycles we keep failing basic QA checks like missing calibration or timestamps, and that forces re-sampling. Where are we losing reliability — unclear protocol steps, poor technician checklists, or lack of immediate validation — and what one habit should we change now to stop repeat failures?