Continuous Monitoring Station Service and Calibration Log

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: safety, access, reference, or raw-record preservation prerequisite unresolved

Stable record IDNot started

Full-record documentation0 of 49 required fields documented

Safety and authority boundary

This log records field service evidence; it does not validate affected data, approve corrections, certify the technician, authorize public-health or treatment action, or replace project, manufacturer, electrical, diving, boating, confined-space, or laboratory requirements. Governing QAPPs, SAPs, SOPs, work plans, permits, and qualified review still control every disposition. This form provides no universal acceptance thresholds, calibration limits, or service intervals.

LakeTech Learning Center · Field record

Continuous Monitoring Station Service and Calibration Log

Template ID: continuous-monitoring-station-service-calibration-log
Version: 1.0.0
Reviewed: 2026-07-15
Record ID: Blank
Record state: blank
Disposition: STOP WORK: safety, access, reference, or raw-record preservation prerequisite unresolved
Reviewer attestation: Not recorded
Source guide: continuous-monitoring-station-operations-quality-assurance

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, station, and visit control

Use stable IDs. Keep personal contact details out of exports unless your program requires and protects them. Reference the current approved work plan, SOP, and manufacturer instructions before any change.

Core record

Record ID · requiredNot recordedGenerated when you start a browser record; preserved on export and import.Project or parent record IDNot recordedCompleted by and role · requiredNot recordedSensitive data class: personal.Reviewer attestation recorded byNot recordedBrowser-entered reviewer details are not identity-verified and do not authenticate validation.Sensitive data class: personal.Reviewer attestation dateNot recordedWaterbody, station name, and site description · requiredNot recordedSensitive data class: operational.Station ID, asset tag, or telemetry node ID · requiredNot recordedSensitive data class: operational.Station coordinates, datum, accuracy, depth reference, and mounting locationNot recordedSensitive data class: precise location.Visit purpose: routine service, calibration, repair, deployment, retrieval, or incident response · requiredNot recordedGoverning work plan, SOP, QAPP element, manufacturer manual, and permit references with versions · requiredNot recordedSensitive data class: operational.Visit start local date and time · requiredNot recordedVisit end local date and timeNot recordedVisit UTC offset (for example -07:00) · requiredNot recordedCrew, roles, boat/vessel ID, and check-in or lone-worker controlsNot recordedSensitive data class: personal.Work order, ticket, or authorization referenceNot recordedSensitive data class: operational.

2. Safety and access gates

For every gate record Unknown - HOLD, No - HOLD, or Yes. Any No - HOLD or unresolved Unknown - HOLD requires stopping work until the responsible authority records resolution in gate evidence.

Core record

Current approved work plan and SOP present on site or accessible · requiredNot recordedSite, weather, and access conditions safe for the planned work · requiredNot recordedElectrical and power isolated, locked out, or de-energized as required · requiredNot recordedLifting, boat, ice, diving, or confined-space controls satisfied as applicable · requiredNot recordedSpill, HAB, sewage, or biological exposure controls satisfied · requiredNot recordedCorrect calibration standards, buffers, gases, or references available and in date · requiredNot recordedSensitive data class: operational.Raw data files, logger memory, and configuration backed up before changes · requiredNot recordedSensitive data class: operational.Evidence IDs, verifier, hold reasons, authority direction, and resolutions for every gate · requiredNot recordedSensitive data class: incident sensitive.Stop-work direction received and case referenceNot recordedSensitive data class: incident sensitive.

3. As-found station, power, communications, clock, depth, and configuration

Record the station state before service. Do not overwrite prior configuration history; add a new chronological row.

Core record

Public output or dashboard maintenance state before disturbance · requiredNot recordedSensitive data class: operational.Raw logger and telemetry snapshot preserved before disturbance · requiredNot recordedSensitive data class: operational.Maintenance window flag or annotation applied · requiredNot recordedSensitive data class: operational.Logger, telemetry, and field clock verified against project criterion · requiredNot recordedSensitive data class: operational.As-found station and sensor state captured before cleaning or adjustment · requiredNot recordedSensitive data class: operational.As-found power source, battery state, solar/charger, modem, telemetry, and communications status · requiredNot recordedSensitive data class: operational.As-found logger clock, timezone, depth reference, pressure offset, and sounding basis · requiredNot recordedSensitive data class: operational.As-found configuration rows: sensor/channel, parameter, unit, interval, gain, equation, and firmware version · requiredNot recordedSensitive data class: operational.As-found alarm, alert, and diagnostic state with timestamps and last known good transmission · requiredNot recordedAs-found instrument rows: manufacturer, model, asset ID, serial, sensor/cap/membrane, and install dateNot recordedSensitive data class: operational.As-found raw file IDs, checksums, download time, and preserved locationNot recordedSensitive data class: operational.

4. Fouling and pre-clean reference evidence

Document fouling, biofilm, sediment, ice, damage, or obstruction before cleaning. Preserve photo or measurement evidence linked to sensor channels.

Core record

Fouling rows: sensor/channel, type, severity, extent, suspected cause, and observation time · requiredNot recordedPre-clean reference evidence: photo/video IDs, in-situ reading, comparison probe ID, and stabilization notes · requiredNot recordedSensitive data class: operational.Structural, mooring, housing, cable, or anti-fouling guard damage observed before serviceNot recordedWeather, stage, ice, inflow, treatment, or upstream event context affecting foulingNot recorded

5. Cleaning, parts, consumables, firmware, and configuration changes

Record every cleaning step, part replacement, consumable change, firmware update, and configuration edit with before/after references.

Core record

Service rows: time, sensor/channel, action (clean, replace, lubricate, desiccant), part/consumable ID/lot, technician, and result · requiredNot recordedSensitive data class: operational.Firmware and configuration change rows: component, prior version/settings, new version/settings, authority, backup ID, and rollback plan · requiredNot recordedSensitive data class: operational.Firmware, coefficient, equation, alarm, or configuration change control · requiredNot recordedSensitive data class: operational.Decontamination, waste handling, and spill-prevention steps performedNot recordedSensitive data class: operational.Removed parts retained for lab, warranty, or failure analysis with custody IDNot recordedSensitive data class: operational.

6. Sensor calibration and verification rows

One repeatable row per calibration or verification step. Include standards, acceptance criteria from the governing document, and pass/fail or flag outcome. This form provides no universal limits.

Core record

Calibration rows: step ID, sensor/channel, parameter, method, standard/reference ID/lot/expiry, expected range, as-found, adjustment, as-left, unit, criteria source, pass/fail/flag, time, technician · requiredNot recordedSensitive data class: operational.As-found verification summary against controlled project criteria · requiredNot recordedSensitive data class: operational.Stabilization time, rinse, equilibration, and environmental conditions during checksNot recordedFailed or marginal steps: corrective action, repeat attempt ID, hold decision, and authority consultedNot recordedSensitive data class: incident sensitive.

7. Independent comparison or laboratory evidence

Link grab samples, duplicate probes, reference instruments, or laboratory results used to support calibration decisions.

Core record

Comparison rows: evidence ID, type (grab, duplicate probe, lab), time, depth/reference, parameter, value/unit, method, agreement criterion source, and disposition · requiredNot recordedSensitive data class: operational.Laboratory sample IDs, custody, method, and result references when applicableNot recordedSensitive data class: operational.Spatial, temporal, or matrix limitations affecting comparison interpretationNot recorded

8. As-left configuration, alerts, and depth

Record the station state after service and before departure. Confirm alerts, depth reference, and transmission behavior match the approved plan.

Core record

As-left configuration rows: sensor/channel, parameter, unit, interval, gain, equation, firmware, and approved plan reference · requiredNot recordedSensitive data class: operational.As-left alarm thresholds, depth reference, pressure offset, transmission test, and observed telemetry confirmation · requiredNot recordedSensitive data class: operational.As-left active-channel acceptance under the controlled procedure · requiredNot recordedSensitive data class: operational.Alert delivery and public-output state after service · requiredNot recordedSensitive data class: operational.Post-service raw file IDs, checksums, download time, and preserved locationNot recordedSensitive data class: operational.Post-service field test readings: parameter, time, value, unit, flag, and evidence IDNot recordedSensitive data class: operational.

9. Affected raw-data interval and provisional flags

Identify the time range potentially affected by fouling, drift, service, or configuration changes. Provisional flags require a named correction owner; this record does not approve corrections.

Core record

Affected interval rows: start/end time with offset, channel/parameter, reason (fouling, drift, outage, config change), and evidence link · requiredNot recordedSensitive data class: operational.Potential effect on the recorded data interval · requiredNot recordedSensitive data class: operational.Provisional flag rows: record ID, channel, flag code, reason, applied by, and pending review state · requiredNot recordedCorrection or validation owner, due date, and governing review procedure · requiredNot recordedSensitive data class: personal.Raw-record and correction-lineage boundary · requiredNot recordedSensitive data class: operational.Data gaps, logger resets, clock corrections, and estimated versus measured uncertaintyNot recordedSensitive data class: operational.

10. Operational disposition, handoff, and closeout

Disposition documents field judgment and reviewer attestation; it does not validate data or authorize unrestricted operational use without project review.

Core record

Operational disposition · requiredNot recordedDisposition scope: channels, parameters, data intervals, and restrictions attached · requiredNot recordedSensitive data class: operational.Service attestation: technician name, role, date, and statement of work completed (not identity-verified) · requiredNot recordedBrowser-entered attestation is not identity-verified and does not certify the technician.Sensitive data class: personal.Handoff: operations contact, monitoring team, data manager, and instructions left on site or in ticketing system · requiredNot recordedSensitive data class: personal.Reviewer attestation: name, role, date, and basis reviewed (not identity-verified) · requiredNot recordedBrowser-entered reviewer details are not identity-verified and do not authenticate validation.Sensitive data class: personal.Next service trigger: project-defined interval, fouling indicator, alarm, or event basis (no universal schedule implied) · requiredNot recordedSensitive data class: operational.Unresolved issues, punch list, warranty claims, parts on order, and follow-up owner · requiredNot recordedAuthority or stakeholder notification log when incident, spill, or public concern required contactNot recordedSensitive data class: incident sensitive.