Aquatic Vegetation Survey, Identification, and Authority Handoff Record

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.

Browser-local record boundary

Field values are not uploaded by this form. Standard page analytics may record this page visit, not entered values. Nothing is autosaved: download a completed-record CSV or print before leaving. Downloads may contain personal, precise-location, conservation-sensitive, incident-sensitive, restricted-infrastructure, or health-sensitive information; use approved storage and sharing. Do not publish restricted locations, private assets, household or health records, or conservation-sensitive evidence unless each controlling authority and owner has approved the exact scope and precision.

Computed record state

blank

Operational dispositionSTOP WORK: field safety prerequisite unresolved

Stable record IDNot started

Full-record documentation0 of 77 required fields documented

Independent aquatic vegetation v1 states

field Safety: not assessed
survey: not started
identification: not started
invasive Status: not evaluated
management: not evaluated
implementation: not started
effectiveness: not evaluated
public Communication: not authorized

Survey, identification, jurisdictional status, authorization, implementation, effectiveness, and public communication remain separate attributable decisions.

Safety and authority boundary

This record does not authorize boating, wading, diving, ice access, specimen collection, transport of regulated material, harvesting, drawdown, stocking or biological control, pesticide use, treatment, or public notice. Do not enter suspected HAB, spill, sewage, unsafe-weather, or entanglement conditions. Current project plans, landowner and collection permissions, protected-species requirements, decontamination procedures, pesticide labeling, permits, licenses, and responsible authorities control the work. Field or image identification is provisional unless the recorded determination evidence supports the stated rank. This form does not declare a species invasive. Non-detection applies only to the documented survey design, area, time, method, and effort and never proves absence.

LakeTech Learning Center · Field record

Aquatic Vegetation Survey, Identification, and Authority Handoff Record

Template ID: aquatic-vegetation-survey-and-identification-record
Version: 1.0.0
Reviewed: 2026-07-15
Record ID: Blank
Record state: blank
Disposition: STOP WORK: field safety prerequisite unresolved
Reviewer attestation: Not recorded
Source guide: aquatic-vegetation-survey-identification-and-mapping

Start a browser record to enter values and create a stable ID. You can still print this blank form.

Record view Guided workflow view Full record

Guided view follows recorded workflow branches and preserves evidence from branches you later change. Full view and print always include every field.

Record sections

1. Record control and survey event

Use stable event, plan, station-set, and authority references. Keep names out of role-ID fields and protect sensitive survey geometry.

Core record

Record ID · requiredNot recordedGenerated when you start a browser record; preserved on export and import.Sensitive data class: operational.Project or parent record IDNot recordedSensitive data class: operational.Completed by and role · requiredNot recordedSensitive data class: personal.Survey event ID · requiredNot recordedSensitive data class: operational.Waterbody and station-set ID or version · requiredNot recordedSensitive data class: operational.Survey extent geometry, map, or protected GIS referenceNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Survey purpose, intended use, target population, audience, and decision owner · requiredNot recordedSensitive data class: operational.Governing QAPP, survey plan, SOP, permits, permissions, and versions · requiredNot recordedSensitive data class: operational.Federal, state, Tribal, territorial, local, landowner, and program authority references · requiredNot recordedSensitive data class: operational.Survey start local date and time · requiredNot recordedSurvey end local date and timeNot recordedUTC offset · requiredNot recordedSurvey team stable role IDs and assigned scope · requiredNot recordedSensitive data class: operational.

2. Field safety gates

Record Unknown - HOLD, No - HOLD, or Yes. A hold stops the affected field work until resolved under the governing plan.

Core record

Current safety and hazard plan accessible · requiredNot recordedWeather, lightning, access, and shoreline conditions acceptable · requiredNot recordedBoat, PFD, buddy, wading, diving, and ice controls satisfied as applicable · requiredNot recordedVegetation entanglement, cutting-tool, propeller, and retrieval hazards controlled · requiredNot recordedNo unauthorized contact with suspected HAB, spill, sewage, or contaminated water · requiredNot recordedSensitive data class: personal.Check-in, communications, stop-work, and emergency escalation confirmed · requiredNot recordedSafety evidence, verifier, hold reasons, authority direction, and resolution references · requiredNot recordedSensitive data class: incident sensitive.Stop-work or restricted-access direction and case referenceNot recordedSensitive data class: incident sensitive.

3. Controlled survey design

Copy the project-controlled design. This form supplies no universal station spacing, point count, depth limit, rake count, abundance class, or revisit frequency.

Core record

Controlled survey design ID, version, effective date, and owner · requiredNot recordedSensitive data class: operational.Controlled survey design state · requiredNot recordedSensitive data class: operational.Survey method type · requiredNot recordedTarget population, lake area, littoral boundary, strata, season, and inference extent · requiredNot recordedStation frame, selection rule, inclusion/exclusion rule, and replacement rule · requiredNot recordedSensitive data class: operational.Planned eligible station count · requiredNot recordedDepth, zone, shoreline, and water-level reference design · requiredNot recordedObservation unit and controlled abundance, occurrence, cover, density, or biomass scale · requiredNot recordedSearch, rake, transect, image, replicate, and identification effort rule · requiredNot recordedProject completeness calculation, eligible denominator, acceptance rule, and decision owner · requiredNot recordedRevisit, inaccessible-site, not-raked, and non-detection interpretation rule · requiredNot recorded

4. Station observations and bounded detections

Preserve actual effort, inaccessible and not-sampled states, taxa observed, and limitations. Never convert non-detection into absence.

Core record

Station rows: station ID, coordinates, time/offset, access, depth/reference, method, effort, observer role ID, and result state · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Station identities, coordinates, times, and plan reconciled · requiredNot recordedSensitive data class: operational.Inaccessible, not sampled, not raked, unsafe, dry, outside-frame, or replacement-station rows and controlled reason codes · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Vegetation rows: occurrence ID, station, growth form, field taxon, recorded rank, detection, controlled abundance metric, depth, and quality flag · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Water level, clarity, substrate, weather, access, recent disturbance, and management contextNot recordedPhoto rows: photo ID, occurrence/station link, diagnostic structures, scale, direction, original file, metadata, and restricted storage · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Survey deviations, missed stations, changed effort, equipment failure, and authority direction; explicitly record none when applicable · requiredNot recordedSensitive data class: incident sensitive.Survey completion state · requiredNot recordedSensitive data class: operational.Survey completion and inference scope: eligible, completed, inaccessible, omitted, and replacement station IDs · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Detection summary state · requiredNot recorded

5. Specimens, vouchers, and biosecurity

Observation or photography can continue where authorized even when specimen collection is held. Do not collect, retain, or transport protected or regulated material without current permission.

Core record

Specimen collection permission state · requiredNot recordedSensitive data class: operational.Rare, protected, culturally sensitive, and regulated-taxon collection state · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Boat, gear, fragment, water, sediment, specimen, and between-site biosecurity state · requiredNot recordedSensitive data class: operational.Voucher/specimen rows: specimen ID, occurrence, collector role ID, structures, collection authority, time, condition, preservative/pressing, and disposition; document none · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Occurrence, photo, field taxon, specimen, duplicate, voucher, laboratory, and accession crosswalk · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Specimen transfer rows: stable role IDs, time/offset, condition, destination, permit, and exception evidenceNot recordedSensitive data class: personal.Protected interim storage, herbarium, laboratory, authority, retention, return, or disposal referenceNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Collection, handling, transport, decontamination, or permit deviations and authority directionNot recordedSensitive data class: incident sensitive.

6. Taxonomic identification and confidence

Keep each field name, later determination, taxonomic rank, evidence, determiner, and revision attributable. Image or field identification remains provisional unless the evidence supports the recorded rank.

Core record

Identification rows: occurrence/specimen ID, initial and current name, rank, name authority, key/source/version, diagnostic characters, determiner role ID, confidence, and date · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Identification confidence state · requiredNot recordedIdentification state scope: occurrence, specimen, voucher, taxon, and rank IDs · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Taxonomic keys, floras, databases, nomenclatural sources, and versions · requiredNot recordedSensitive data class: operational.Determiner, qualified reviewer, herbarium, laboratory, or authority determination referenceNot recordedRequired for a confirmed-to-rank state. Browser-entered details are not identity-verified.Sensitive data class: personal.Voucher repository and accession referenceNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Molecular, microscopy, or other laboratory evidence reference and limitationsNot recordedSensitive data class: operational.Lookalikes, hybrids, missing diagnostic structures, seasonal limitations, conflicting evidence, and unresolved rank · requiredNot recordedIdentification change history: prior name/rank, new determination, reason, actor, date, and affected products · requiredNot recordedSensitive data class: operational.Identification reviewer attestation: name, role, date, rank, evidence reviewed, and limitations (not identity-verified) · requiredNot recordedSensitive data class: personal.

7. Jurisdiction-specific invasive or regulated status

Record only an attributable authority determination. A taxon name, nonnative distribution record, common-name list, or LakeTech page cannot declare status for a jurisdiction.

Core record

Exact taxon name, recorded rank, naming authority, and identification reference used for status review · requiredNot recordedFederal, state, Tribal, territorial, county, local, waterbody, and program scope · requiredNot recordedSensitive data class: operational.Authority list, statute, rule, policy, watch list, occurrence procedure, version/effective date, and access date · requiredNot recordedSensitive data class: operational.Recorded authority status state · requiredNot recordedStatus decision scope: occurrence, taxon, rank, jurisdiction, date, and affected records · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Responsible authority confirmation, case, reviewer, or published decision referenceNot recordedRequired for either authority-confirmed state.Sensitive data class: operational.Authority status review date · requiredNot recordedNew-occurrence report, alert, case, or tracking referenceNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Authority-issued possession, cleaning, movement, transport, quarantine, or disposal restrictionsNot recordedSensitive data class: operational.Authority notification, containment, reporting, or follow-up directionNot recordedSensitive data class: incident sensitive.

8. Management eligibility and authorization

Eligibility, recommendation, authorization, and method selection are separate. The form does not select a product, calculate an application rate, or replace a pesticide label, permit, license, or responsible-authority decision.

Core record

Documented habitat, use, access, infrastructure, restoration, spread, or other management problem and evidence · requiredNot recordedNamed endpoint, protected resource, spatial scope, time horizon, adverse endpoint, and decision rule · requiredNot recordedManagement basis · requiredNot recordedNo-action, prevention, source control, physical, mechanical, biological, pesticide, integrated, and monitoring alternatives with tradeoffs · requiredNot recordedNative plants, fish, wildlife, protected species, habitat, cultural resources, downstream waters, intakes, and water uses · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Management method class · requiredNot recordedManagement eligibility and authorization state · requiredNot recordedManagement decision scope: taxa, area, timing, method class, endpoint, exclusions, and restrictions · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Responsible authority authorization and effective-version referenceNot recordedSensitive data class: operational.Approved management or implementation plan versionNot recordedSensitive data class: operational.Current pesticide product label, EPA registration, supplemental labeling, and state registration referenceNot recordedSensitive data class: operational.Current pesticide discharge and other permit-coverage determination by the responsible authorityNot recordedSensitive data class: operational.Applicable licensed/certified applicator or supervision authorization referenceNot recordedSensitive data class: personal.Mechanical, drawdown, dredging, stocking, biological-control, navigation, habitat, water-right, or other permit referencesNot recordedSensitive data class: operational.Authority- or label-controlled intake, irrigation, recreation, access, notification, setback, timing, and water-use constraintsNot recordedSensitive data class: operational.Responsible management decision owner, role, and decision date · requiredNot recordedSensitive data class: personal.

9. Implementation and effectiveness validation

Scheduling, implementation, compliance documentation, endpoint monitoring, and effectiveness validation remain separate attributable events.

Core record

Implementation state · requiredNot recordedImplementation scope: authorization, taxa, area, method, date, exclusions, restrictions, and affected event IDs · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Scheduled and completed implementation event referencesNot recordedSensitive data class: operational.Original application, harvest, removal, drawdown, stocking, disposal, monitoring, notification, and compliance record referencesNot recordedSensitive data class: operational.Weather, access, scope, equipment, label, permit, non-target, spill, exposure, incomplete-action, and stop-work deviationsNot recordedSensitive data class: incident sensitive.Controlled effectiveness design, endpoints, comparison logic, schedule, uncertainty, adverse outcomes, and decision owner · requiredNot recordedSensitive data class: operational.Baseline, reference, untreated comparison, prior survey, or counterfactual evidence reference and limitations · requiredNot recordedSensitive data class: operational.Effectiveness validation state · requiredNot recordedEffectiveness decision scope: endpoint, area, taxon/community, dates, evidence, exclusions, and limitations · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Qualified reviewer decision, analysis package, and version referenceNot recordedSensitive data class: operational.Non-target, habitat, oxygen, water-use, downstream, recolonization, fragment-spread, or other adverse findingsNot recordedSensitive data class: incident sensitive.Next monitoring, validation, corrective action, or decision and due date · requiredNot recordedImplementation attestation: name, role, date, event IDs, and authorization basis reviewed (not identity-verified)Not recordedSensitive data class: personal.Effectiveness reviewer attestation: name, role, date, scope, evidence, and limitations (not identity-verified)Not recordedSensitive data class: personal.

10. Public communication and handoff

A public product requires attributable authority and a location-release decision. It may communicate uncertainty or non-detection but cannot silently upgrade evidence or expose restricted locations.

Core record

Public communication state · requiredNot recordedResponsible communication authority and decision referenceNot recordedSensitive data class: personal.Public product scope: taxon/rank, area generalization, dates, survey state, identification state, authority status, management state, and limitationsNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Published, corrected, withdrawn, or superseded product/version referenceNot recordedSensitive data class: operational.Required uncertainty, non-detection, jurisdiction, authorization, effectiveness, and location limitations · requiredNot recordedSensitive-location release decision · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Unresolved identifications, status conflicts, permissions, authorization, implementation, effects, corrections, and owners; explicitly record none · requiredNot recordedNext responsible role, action, evidence needed, and due date · requiredNot recordedSensitive data class: personal.Reviewer attestation: name, role, date, states and evidence reviewed, scope, and limitations (not identity-verified) · requiredNot recordedSensitive data class: personal.