Aquatic Invasive Species Prevention, Detection, and Response 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 dispositionMORE EVIDENCE: no identity, absence, establishment, status, movement release, response, or effectiveness conclusion implied

Stable record IDNot started

Full-record documentation0 of 36 required fields documented

Independent aquatic invasive species edrr v1 states

immediate_safety_state
movement_hold_state
observation_evidence_state
report_submission_state
specimen_authority_state
specimen_custody_state
edna_evidence_state
taxonomic_determination_state
occurrence_verification_state
establishment_state
jurisdictional_status_state
surveillance_design_state
biosecurity_protocol_state
decontamination_clearance_state
rapid_response_readiness_state
response_eligibility_state
response_authorization_state
implementation_state
long_term_management_state
effectiveness_state
public_release_correction_state

Observation, reporting, specimen and eDNA evidence, taxonomic determination, occurrence, establishment, jurisdictional status, surveillance, biosecurity, movement release, response eligibility, authorization, implementation, long-term management, effectiveness, and public correction remain separate attributable decisions.

Safety and authority boundary

This record does not identify an organism from a photograph or description; establish occurrence, establishment, absence, eradication, origin, invasive or regulated status, or legal compliance; issue current jurisdiction or reporting-contact advice; authorize access, capture, retention, euthanasia, transport, release, disposal, boating, wading, diving, watercraft inspection, decontamination, launch, sampling, eDNA work, pesticides, biocontrol, stocking, barriers, removal, treatment, public restriction, reopening, or response; or provide a temperature, chemical, pressure, contact-time, drying-time, rinseate, waste, or species-specific recipe. A report is not a verified occurrence. eDNA detection is evidence of genetic material, not proof of a live organism, abundance, reproduction, or establishment. A non-detect and database absence are not biological absence. Nonnative is not automatically invasive. Occurrence is not establishment or harm. Inspection is not decontamination; protocol completion is not universal clearance. A plan, grant, design, permit application, or detection is not authorization. Implementation is not control, restoration, eradication, or effectiveness. Current employer/owner, Tribal, federal, state, territorial, local, land, water, wildlife, pesticide, waste, protected-resource, safety, privacy, and public-communication authority controls. Generalize or suppress sensitive occurrence locations, protected resources, infrastructure, and personal contacts in public exports.

LakeTech Learning Center · Field record

Aquatic Invasive Species Prevention, Detection, and Response Record

Template ID: aquatic-invasive-species-prevention-detection-and-response-record
Version: 1.0.0
Reviewed: 2026-07-15
Record ID: Blank
Record state: blank
Disposition: MORE EVIDENCE: no identity, absence, establishment, status, movement release, response, or effectiveness conclusion implied
Reviewer attestation: Not recorded
Source guide: aquatic-invasive-species-prevention-rapid-response-and-management-program

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, safety, and movement hold

Protect people first and stop avoidable movement of water, organisms, watercraft, trailers, sampling gear, anchors, ropes, waders, and other potentially affected equipment under the controlling plan. This record does not identify an organism or prescribe decontamination.

Core record

Stable record ID · requiredNot recordedProgram, incident, visit, or parent record IDNot recordedRecord date · requiredNot recordedCompleted by and role · requiredNot recordedSensitive data class: personal.Waterbody, jurisdiction, Tribal/landowner authority, generalized site, and access status · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Immediate safety and incident-routing state · requiredNot recordedSafety plan, active hazard, exposure, emergency/incident handoff, direction, date, and paused scopeNot recordedSensitive data class: incident sensitive.Potential pathway and movement-hold state · requiredNot recordedAsset IDs, water/organism contact, source and destination waters, timestamps with offsets, isolation, owner, exact hold/release scope, and evidence · requiredNot recordedSensitive data class: operational.

2. Bounded observation and authority reporting

Record what was observed without converting a photograph, app suggestion, common name, database record, or public report into taxonomic confirmation, verified occurrence, establishment, invasive status, or response authority.

Core record

Observation-evidence state · requiredNot recordedSensitive data class: incident sensitive.Exact date/time/offset, generalized location, habitat/substrate/host, observable descriptors, count or extent basis, method/effort, photo/video IDs, scale, look-alikes, and limitations · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Reporting and authority-handoff state · requiredNot recordedCurrent state/Tribal/territorial/local/federal channels, recipient, submitted time, case/report IDs, attachments, acknowledgement, next owner, open channels, and correction history · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.

3. Specimen authority, custody, eDNA, and taxonomic determination

No-handling and no-specimen branches are valid. Collection, retention, euthanasia, transport, shipping, disposal, and eDNA work require the controlling authority, safety, biosecurity, laboratory, and custody procedures.

Core record

Specimen collection and movement authority state · requiredNot recordedDirection, collector, permit/permission, material, method, quantity, transport, destination, restrictions, dates, and issuing authorityNot recordedSensitive data class: operational.Specimen custody and repository state · requiredNot recordedSpecimen/voucher ID, label, container, preservation, seal, transfers, condition, repository/accession, shipping authority, disposition, and deviationsNot recordedSensitive data class: operational.Environmental-DNA evidence state · requiredNot recordedSensitive data class: incident sensitive.Target/assay, sample IDs, method, field/lab controls, contamination and inhibition review, custody, laboratory, qualifiers, reporting limits, validation, and permitted inferenceNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Taxonomic-determination state · requiredNot recordedAsserted taxon and resolution, identifier/organization, method/key/reference, evidence IDs, confidence, look-alikes, limitations, determination date, and revision history · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.

4. Occurrence, establishment, and jurisdictional status

Identity, occurrence, establishment, origin, harm, regulated/invasive status, and management eligibility are separate authority-controlled decisions. Database absence is not biological absence.

Core record

Occurrence-verification state · requiredNot recordedAuthority/database, record ID, evidence basis, location/date scope, verification status, access date, metadata limits, and correction historyNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Establishment state · requiredNot recordedLife stages, repeated evidence, reproduction/recruitment indicators, delimiting scope, method/detectability, responsible authority, conclusion, uncertainty, and dateNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Origin, invasive/regulated, and jurisdictional-status state · requiredNot recordedControlling jurisdiction/list, taxon, status category, source version/effective date, access date, authority, scope, conflicts, and limitations · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.

5. Surveillance design, biosecurity, and decontamination clearance

A non-detection is bounded by the sampled frame, methods, season, effort, controls, and detectability. LakeTech does not provide decontamination recipes; only an adopted protocol and its responsible owner may control work and movement.

Core record

Early-detection and delimiting-surveillance state · requiredNot recordedDecision, target taxon/life stage, population/frame, sites, pathway/habitat basis, timing, effort, replication, complementary methods, controls, detection probability/sensitivity, unsampled units, and limitations · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Field biosecurity and pathway-control state · requiredNot recordedIssuer, protocol title/version/effective date, equipment/taxon/pathway scope, required user-entered steps, dedicated/shared assets, waste/rinseate controls, evidence, exceptions, and reviewer · requiredNot recordedSensitive data class: operational.Decontamination and movement-clearance state · requiredNot recordedLinked ledger/asset, protocol evidence, completion, exception resolution, destination requirements, release owner, exact scope, decision time/offset, expiration/supersession, and limitations · requiredNot recordedSensitive data class: operational.

6. Rapid-response readiness, eligibility, authorization, and implementation

A report, detection, risk screen, response plan, grant, permit application, or confirmed occurrence does not authorize eradication, containment, suppression, pesticide use, removal, stocking, barriers, access restrictions, or other action.

Core record

Rapid-response readiness state · requiredNot recordedAuthority/team, activation procedure, contacts, communications, funding/procurement, qualified staff, equipment, laboratory, safety, biosecurity, sensitive-resource controls, exercises, gaps, and review date · requiredNot recordedSensitive data class: restricted infrastructure. Restrict private-well, septic, utility, access-boundary, construction, pumping, and exact asset-location records.Response-alternatives eligibility state · requiredNot recordedDelimiting evidence, objectives, no-action/protection/action options, feasibility, uncertainty, protected resources, animal welfare, off-target/adverse effects, permits, waste, lifecycle cost, funding, and rejection reasons · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Response-authorization state · requiredNot recordedAction/design, label and permit where applicable, Tribal/federal/state/local/owner authorizations, protected-resource review, funding conditions, qualified implementer, dates, exact scope, and stop criteriaNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Implementation state · requiredNot recordedAuthorization link, implementer, exact time/location/scope, as-designed/as-built, materials/equipment, field logs, deviations, stop work, waste, inspections, adverse observations, and acceptanceNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.

7. Long-term management, effectiveness, and controlled public release

Control is not restoration; treatment is not effectiveness; one season without detection is not eradication or long-term control. Protect sensitive occurrence locations and preserve corrections and supersession.

Core record

Long-term management and maintenance state · requiredNot recordedObjectives, owner, recurring prevention/surveillance/control/restoration work, funding, contracts, training, assets, maintenance, pathway controls, trigger/review dates, and gapsNot recordedSensitive data class: operational.Effectiveness-evidence state · requiredNot recordedMechanism, implementation fidelity, pathway/inspection/surveillance/population/ecological/restoration endpoints, baseline/comparator, effort/detectability, confounders, adverse effects, uncertainty, reviewer, and dateNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Public release, correction, and supersession state · requiredNot recordedRelease owner, audience, generalized location/status/action scope, excluded sensitive locations/personal contacts/protected resources, version, limitations, correction contact, supersession, and next review · requiredNot recordedSensitive data class: conservation sensitive. Restrict exact locations, images, and specimen links unless an attributable release decision approves them.Qualified reviewer attestation: role, organization, evidence reviewed, bounded conclusions, limitations, conflicts, and dateNot recordedSensitive data class: personal.