Turn the approved plan into exact field visits.
Compare entered visit dates with entered plan expectations, keep tentative and canceled work visible, and expose only those role, equipment, and availability conflicts supported by your entries.
- Starting point
- Your controlling sampling plan
- Data handling
- Browser memory; explicit CSV
- Boundary
- No design, frequency, safety, or approval claim
Confirm the prerequisite
Review the governing method before entering or interpreting data.
Return to the source guide
Shared route boundary
Does not choose stations, depths, methods, frequencies, sample counts, routes, forecasts, safety controls, field authorization, scientific adequacy, representativeness, or compliance.
Start from a controlling sampling plan. This tool supplies no stations, methods, or frequencies.
Schedule only what the controlling plan already defines.
The tool checks entered dates, resources, and counts. It does not decide what, where, or how often to monitor.
Name stations, work packages, and coverage windows.
Stations
Work packages
Coverage windows
Detect only conflicts supported by entered role and equipment IDs.
Non-personal role resources
Equipment sets
Availability windows
Leave counts blank unless the controlling plan states them.
Place plan-defined work on exact dates with explicit offsets.
Compare the entered schedule with the entered plan.
Complete required plan references and valid explicit-offset times to display coverage and conflicts.
Save the work and continue
Carry the result into its governed record and broader workflow; these links do not approve the work.
Open the sampling plan worksheet Keep the entered plan reference, coverage windows, and expectation counts with the schedule.
Continue the monitoring-program path Carry the visit schedule into the broader monitoring design and data-release workflow.
Shared route boundary
Does not choose stations, depths, methods, frequencies, sample counts, routes, forecasts, safety controls, field authorization, scientific adequacy, representativeness, or compliance.
Entered-plan arithmetic, not monitoring design.
Visits use strict local date-times with explicit UTC offsets. Overlap uses half-open intervals, so one visit ending exactly when another begins is not an overlap. A conflict is reported only when overlapping non-canceled visits share an entered role or equipment ID. Coverage counts planned, tentative, and canceled visits separately against explicit plan expectations.
- EPA National Lakes Assessment 2022 Field Operations ManualField-protocol context; not a universal project schedule
- EPA manuals used in National Aquatic Resource SurveysMethod and planning context
Controlled preview. Internal technical review is complete. Independent review is pending, so this artifact remains available for review but is excluded from search-engine discovery. Next review: 2026-10-15.