Monitoring Program Builder: From Question to Verified Result
Design a durable program across stations, methods, equipment, telemetry, data review, maintenance, communication, and management-effect verification.
- For
- Municipalities, parks, consultants, watershed programs, HOAs, and community-science coordinators
- Field stops
- 8
- Reading + practice
- About 180 minutes
- Review status
- Controlled preview
Finish with a field-ready draft, not a badge.
A program architecture with decision owners, station logic, field/lab methods, equipment roles, QA/QC, maintenance, data states, alerts, and verification endpoints.
Complete Lake Manager Foundations or bring a documented management question, site model, intended data use, program owner, and current method requirements.
Field route
Use an authored handoff; this is not an automatic recommendation or approval.
Open Lake Field Unit Converter Move from unit checks into the full monitoring design and release curriculum.
Open Monitoring Visit Schedule & Coverage Explorer Carry the visit schedule into the broader monitoring design and data-release workflow.
Open Field Crew Proficiency Return-Demonstration Checklist Document attributable states in Field Crew Proficiency Return-Demonstration Checklist before leaving Monitoring Program Builder: From Question to Verified Result.
Route boundaries
- Refuses empirical pseudo-conversions that require calibration, density, chemistry, or more measurements.
- Does not choose stations, depths, methods, frequencies, sample counts, routes, forecasts, safety controls, field authorization, scientific adequacy, representativeness, or compliance.
Loading local progress…
Decide · 24 minutes Set the decision architecture
Define the intended decision, data-quality objectives, station/depth logic, schedule, and ownership.
Field exerciseWrite the decision-to-data chain from management action backward to evidence, method, station, time, QC, and responsible person.
CheckpointDoes every collected value have a stated use or reason for retention?
Measure · 20 minutes Choose water-sampling equipment by method
Match discrete, integrated, depth-specific, and automated collection to matrix and method requirements.
Field exerciseCreate an equipment-to-method matrix with contamination, cleaning, depth, compositing, volume, and custody constraints.
CheckpointIs the sampler compatible with the analyte, fraction, depth, and container workflow?
Measure · 22 minutes Select sondes and sensors by data need
Evaluate sensor ranges, accuracy, response, compensation, fouling, calibration, deployment, and maintenance burden.
Field exerciseBuild a sensor acceptance table from project requirements rather than the longest available parameter list.
CheckpointDid you include QA standards, maintenance, replacement consumables, and data validation effort?
Practice · 22 minutes Design the monitoring station
Connect location, mooring, power, sensor depth, service access, weather, navigation, ice, and redundancy.
Field exerciseDraw the station with datum, depths, mooring, protected water-column zones, access route, service interval, and failure modes.
CheckpointCan the station survive and still measure the intended water mass?
Practice · 22 minutes Plan telemetry and data states
Design acquisition, buffering, transmission, clock, power, alarms, raw storage, flags, and failure recovery.
Field exerciseTrace one reading from sensor through logger, transmission, validation, alert, dashboard, correction, and archive.
CheckpointCan the system distinguish missing, delayed, provisional, accepted, estimated, and rejected data?
Practice · 24 minutes Build an early-warning workflow
Use continuous data for state change and escalation without treating one threshold crossing as diagnosis.
Field exerciseDefine a persistence, confirmation, human-review, escalation, and reset rule for one alert.
CheckpointDoes the alert retain raw context and require an appropriate confirmation path?
Practice · 20 minutes Integrate community monitoring
Match volunteer roles, training, methods, supervision, QA/QC, communication, and retention to intended use.
Field exerciseSeparate tasks suitable for trained volunteers from tasks requiring project staff, laboratory, or agency control.
CheckpointAre training, proficiency, safety, data review, and escalation ownership explicit?
Document · 26 minutes Verify management effectiveness
Define endpoints, reference or comparison logic, before/after evidence, confounders, uncertainty, and decision timing.
Field exerciseCreate an endpoint table with mechanism, expected direction, station/depth, method, baseline, comparison, window, adverse endpoint, and decision owner.
CheckpointCould the design detect failure, adverse effects, and an inconclusive result, not only apparent success?