Field Crew Proficiency Return-Demonstration Checklist

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 dispositionHOLD: safety prerequisite or reviewer disposition unresolved

Stable record IDNot started

Full-record documentation0 of 30 required fields documented

Safety and authority boundary

This checklist covers one observed task scope only. It does not confer credentialing, accreditation, approval, safety certification, employment qualification, or authorization to work independently. Project staff, trainers, and responsible authorities govern training, supervision, methods, safety, and data acceptance.

LakeTech Learning Center · Field record

Field Crew Proficiency Return-Demonstration Checklist

Template ID: field-crew-proficiency-return-demonstration-checklist
Version: 1.0.0
Reviewed: 2026-07-15
Record ID: Blank
Record state: blank
Disposition: HOLD: safety prerequisite or reviewer disposition unresolved
Reviewer attestation: Not recorded
Source guide: community-lake-monitoring-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.

1. Participant and observation control

One checklist per observed return demonstration. Keep personal identifiers out of exports unless your program requires and protects them.

Core record

Record ID · requiredNot recordedGenerated when you start a browser record; preserved on export and import.Sensitive data class: operational.Participant ID or anonymized code · requiredNot recordedSensitive data class: personal.Participant role in the program · requiredNot recordedSensitive data class: personal.Evaluation purpose and observed task bundle · requiredNot recordedObservation date and local time · requiredNot recordedUTC offset (for example −07:00) · requiredNot recordedObservation location, station, or access pointNot recordedSensitive data class: precise location.

2. Scope and governing documents

Name exactly what was observed and what was excluded. Do not expand scope beyond the demonstrated task bundle.

Core record

Task bundle ID and version · requiredNot recordedSensitive data class: operational.Intended data tier and acceptable use · requiredNot recordedGoverning SOP, training module, QAPP element, and method references with versions · requiredNot recordedSensitive data class: operational.Observed task steps and decision points · requiredNot recordedEquipment, instruments, and consumables in scopeNot recordedSensitive data class: operational.Stations, depths, matrices, and access conditions in scopeNot recordedSensitive data class: precise location.Explicit exclusions and tasks deferred to supervision or staffNot recordedPrerequisite training, orientation, or prior demonstration evidence reviewedNot recordedSensitive data class: operational.

3. Safety go/no-go gates

Any Unknown or No means HOLD until the responsible authority records resolution. N/A requires documented rationale in safety gate evidence.

Core record

Current hazard analysis, site briefing, and stop-work authority understood · requiredNot recordedEmergency contacts, check-in, and stop-work escalation path confirmed · requiredNot recordedRequired training, PPE, and boat/shore/ice controls in place for the task · requiredNot recordedWeather, water, bloom, spill, electrical, and access conditions acceptable for the task · requiredNot recordedEvidence IDs, verifier, hold reasons, and resolutions for every gate · requiredNot recordedSensitive data class: incident sensitive.

4. Trainer demonstration

Record what the trainer demonstrated before the return performance. This is not a substitute for a written SOP or safety plan.

Core record

Trainer, demonstration time, and topics covered · requiredNot recordedSensitive data class: personal.Demonstration topic checklist: safety, calibration, sequence, labeling, cooling, paperwork, escalationNot recordedParticipant questions, trainer responses, and stated limitationsNot recorded

5. Return-performance checks

Observe one complete return demonstration. Document prompts given and whether performance was independent, acceptable with coaching, unacceptable, not observed, or N/A with rationale.

Core record

Stop-work recognition and escalation · requiredNot recordedStation access, hazards, and site orientation · requiredNot recordedEquipment setup, inspection, and readiness · requiredNot recordedCalibration or verification steps · requiredNot recordedSampling order and contamination controls · requiredNot recordedCollection technique and representative handling · requiredNot recordedLabeling, IDs, and field documentation · requiredNot recordedPreservation, cooling, and custody handoff · requiredNot recordedRecordkeeping and metadata completeness · requiredNot recordedAnomaly recognition and escalation · requiredNot recordedDecontamination and closeout · requiredNot recorded

6. Observation evidence and coaching

Link photos, duplicates, deviations, and coaching prompts to the observed performance.

Core record

Evidence IDs: photos, duplicates, instrument readouts, paperwork, and timestamps · requiredNot recordedSensitive data class: operational.Prompts, corrections, and coaching given during the return demonstrationNot recordedDeviations, near misses, or incidents observed during the sessionNot recordedSensitive data class: incident sensitive.N/A rationales for gates or checks not observedNot recordedParticipant acknowledgement of feedback and limitsNot recordedSensitive data class: personal.Participant commentsNot recordedSensitive data class: personal.

7. Reviewer disposition and reassessment

Disposition is project-recognized and reviewer-attested; it is not accreditation, certification, or independent-work authorization.

Core record

Reviewer basis: evidence reviewed, comparisons, and unresolved itemsNot recordedSensitive data class: personal.Disposition · requiredNot recordedDisposition scope: task bundle, stations, tiers, and effective periodNot recordedSensitive data class: operational.Supervision limits, prohibited tasks, and escalation triggersNot recordedRetraining plan, owner, and due date when requiredNot recordedSensitive data class: operational.Reassessment date or windowNot recordedReassessment triggers: method change, incident, lapse, or equipment changeNot recordedReviewer attestation: name, role, date (not identity-verified) · requiredNot recordedBrowser-entered reviewer details are not identity-verified and do not authenticate proficiency approval.Sensitive data class: personal.Second reviewer or coordinator concurrence when required by the programNot recordedSensitive data class: personal.