Use this log to document a single hydrophone recording session and the acoustic detections observed within it. Please complete every field as accurately as possible from your instrument readings and field notes. Entries in this form are observational records only and do not constitute certified measurements, regulatory notifications, or professional determinations.
Station or Survey Identifier
Log Entry Reference Number
Deployment Start (Local Time)
Deployment End (Local Time)
Observer/Analyst Name
Contact Email
Deployment Platform Type
Moored buoy
Vessel-mounted
Shore-based cable
Autonomous drifting unit
Bottom-mounted lander
Other
Mooring or buoy identifier
Vessel name or call sign
Approximate cable run length (meters)
Autonomous unit serial or asset number
Lander or frame identifier
Please describe the platform used:
Is this log a continuation of a previous entry for the same deployment?
Previous log reference number
Is this the first recording session for this deployment?
Survey objective or research question for this session
Record the instrument settings and in-situ water properties that influence how acoustic energy propagates from a source to the receiver. Depth and salinity are used later when interpreting signal levels and estimated source distances.
Hydrophone Depth (meters)
Local Water Depth at Deployment Point (meters)
Water Salinity (PPT)
Water Temperature (degrees Celsius)
Hydrophone Sensitivity (dB re 1 V per micropascal)
Sampling Rate (kHz)
Recording Gain Setting
Low
Medium
High
Automatic gain
Unknown
Channel Configuration
Single channel
Dual channel
Hydrophone array (3 or more elements)
Unknown
Number of array elements
Was the hydrophone system calibrated before this deployment?
Date of most recent calibration
Please describe any potential effect this may have on how the recorded levels are interpreted:
Sensor depth was verified with an independent pressure reading
Anti-fouling measures or protective housing were fitted to the sensor
Environmental and traffic conditions strongly affect background noise and how far a sound may be detected. Please describe conditions as observed during the logging window.
Sea State
Calm (glassy)
Smooth
Slight
Moderate
Rough
Very rough
Not observed
Wind Speed (meters per second)
Weather Conditions During Logging
Clear
Overcast
Light precipitation
Heavy precipitation
Fog or low visibility
Other
Please describe the weather conditions
Estimated Ambient Noise Level (dB re 1 micropascal)
Is the deployment site within or immediately adjacent to a commercial shipping lane?
Approximate straight-line distance to the nearest shipping lane (meters)
Vessel Traffic Observed During the Logging Window
Cargo ships
Tankers
Fishing vessels
Passenger ferries
Small recreational craft
Research or survey vessels
No vessels observed
Other
Please describe the other traffic observed:
Approximate Distance to Nearest Vessel During Logging (meters)
Additional environmental observations (currents, thermocline, biological activity, surface conditions)
Enter one row for each acoustic detection recorded during the session. In the Visual Match column, use one of these categories: Blue Whale, Orca, Submarine Noise, or Unknown. The Source Level Assumption column is the reference source level you are assuming for the detected signal; it is used together with the Received Level to estimate range.
Illustrative passive sonar relationship used for the distance estimate
Where RL is received level, SL is the assumed source level, R is the slant range in meters, and alpha is an approximate frequency-dependent absorption coefficient in dB per kilometer. The Absorption Coefficient column uses a simplified textbook-style estimate based on peak frequency, and the Estimated Distance to Source column applies a single-pass correction for absorption. These values are indicative estimates only; they assume spherical spreading and a simplified absorption model, and they do not account for surface or bottom reflections, refraction, array gain, or source directivity. Treat them as planning aids rather than precise measurements.
Acoustic Detections
Timestamp | Peak Frequency (kHz) | Received Level (dB re 1 micropascal) | Visual Match | Source Level Assumption (dB re 1 micropascal at 1 m) | Absorption Coefficient (dB per km) | Estimated Distance to Source (meters) | Distance to Nearest Shipping Lane (meters) | Within 500 m of Shipping Lane | ||
|---|---|---|---|---|---|---|---|---|---|---|
A | B | C | D | E | F | G | H | I | ||
1 | 5/14/2027, 6:15 AM | 0.020 | 118.0 | Blue Whale | 185.0 | 0.003 | 2237.0 | 2400.0 | ||
2 | 5/14/2027, 7:02 AM | 3.500 | 132.0 | Orca | 180.0 | 0.218 | 249.6 | 320.0 | ||
3 | 5/14/2027, 9:40 AM | 0.100 | 125.0 | Submarine Noise | 170.0 | 0.004 | 177.8 | 1200.0 | ||
4 | ||||||||||
5 | ||||||||||
6 | ||||||||||
7 | ||||||||||
8 | ||||||||||
9 | ||||||||||
10 |
The final column is ticked automatically when the estimated distance to the source is under 500 meters and the detection lies within 500 meters of a commercial shipping lane. If either distance is unknown, leave the corresponding numeric cell blank and describe the situation in the interpretation notes below.
Were any detections excluded from the table because they could not be measured reliably?
Please describe the excluded detections and the reason:
Classification of an acoustic signal is often uncertain, especially when only a single hydrophone is available. Please describe your confidence level and any alternative interpretations you considered.
Overall Confidence in the Visual Match Classifications
High
Moderate
Low
Unresolved
What additional information or equipment would help resolve the classification?
Signal Characteristics Observed
Repetitive pulse train
Continuous tonal sweep
Broadband transient
Low-frequency moan
Impulsive clicks
Regular mechanical or rhythmic signature
Faint broadband background only
Other
Please describe the other signal characteristics:
Were any detections potentially attributable to vessel, industrial, or platform-generated activity?
Please describe the suspected source characteristics and how you distinguished them from biological signals:
Did water salinity or hydrophone depth appear to influence signal clarity or received levels?
Please describe the observed influence:
Do you recommend a follow-up survey, re-analysis, or equipment check?
Suggested follow-up priority
Low
Medium
High
As soon as practical
Please rank the following follow-up actions in order of priority for this station
Re-deploy hydrophone at a different depth | |
Repeat calibration check | |
Extend recording duration | |
Add a second sensor for direction finding | |
Review raw audio files manually | |
No further action required |
Rate the overall data quality for this logging session
Please rate the following aspects of this logging session
Poor | Fair | Good | Very good | Excellent | |
|---|---|---|---|---|---|
Clarity of acoustic recordings | |||||
Accuracy of depth and salinity records | |||||
Completeness of detection entries | |||||
Confidence in source classification | |||||
Timeliness of data transfer to storage |
Analyst notes, anomalies, and caveats
Attach the supporting material that allows another analyst to review this log. Only upload material you are authorized to share.
Upload the raw or processed audio data file for this session
Upload the calibration record or instrument maintenance log
Upload the detection summary or spectrogram export
Upload a photo of the deployment setup or instrument in situ
Station Coordinates (decimal degrees, latitude/longitude)
Raw data files have been backed up to a separate storage location
Field notebook entries have been cross-checked against this log
Any third-party or restricted material has been removed from the attachments
By signing below, you confirm that the entries reflect your own observations and the instrument readings recorded during this session. This log is an internal record and does not by itself establish regulatory status, safety clearance, or scientific validation.
I confirm that the entries in this log reflect my own observations and the recorded measurements for this session
I have flagged any values that are estimated, interpolated, or otherwise uncertain
Name of Person Completing This Log
Role or Position
Reviewed By (if applicable)
Date of Submission
Signature
Analysis for Oceanographic Bio-Acoustic Log Form
Important Note:
This analysis provides strategic insights to help you get the most from your form's submission data for powerful follow-up actions and better outcomes.
AI-Generated Content: This template and its accompanying guidance are AI-generated to provide a practical starting point for your form-building needs. Please review and customise the content to ensure it is accurate, appropriate and suitable for your intended use.
This guide is provided for general informational and planning purposes only. It does not constitute professional, legal, financial, medical, employment, privacy, regulatory, or advice of any other kind, nor does it certify that this template is suitable or compliant for any particular jurisdiction or purpose.
Laws, regulations, industry practices and business requirements vary. You are responsible for reviewing and customising the template to suit your intended use and obtaining advice from appropriately qualified professionals where necessary.
Please delete this section before publishing your form. See our Terms of Service for further information.
The Oceanographic Bio-Acoustic Log Form is a comprehensive, well-structured field logging instrument designed to capture a single hydrophone recording session and the acoustic detections observed within it. The form spans seven logically organized sections — from deployment identification through sensor configuration, environmental conditions, detection logging, interpretation, supporting media, and declaration — creating a clear workflow that mirrors the natural sequence of a field recording session. Its strengths include thoughtful use of conditional follow-ups that reduce unnecessary data entry, a formula-driven detection table that automates distance estimation and shipping-lane proximity flagging, and careful framing language that positions entries as observational records rather than certified measurements. The form balances technical depth with usability, though its length and the number of open-ended fields may present some friction for time-constrained field teams.
Station or Survey Identifier anchors every entry to a specific deployment location or survey effort, enabling downstream analysts to group and cross-reference records. Requiring this field early ensures traceability from the outset.
Log Entry Reference Number provides an optional unique record identifier. While not mandatory, filling it in supports orderly record-keeping, especially when multiple sessions are logged for the same deployment.
Deployment Start (Local Time) and Deployment End (Local Time) establish the temporal window of the recording session. The start time is mandatory, which is sensible since it is the primary temporal anchor; the end time is optional, which may reflect that some sessions are ongoing or logged retrospectively.
Observer/Analyst Name and Contact Email capture who performed the logging. The name is mandatory, supporting accountability and follow-up queries, while the email is optional — a reasonable choice that respects that not all field contexts require direct contact details.
Deployment Platform Type uses a well-designed single-choice list with conditional follow-ups for each platform type (mooring identifier, vessel name, cable length, unit serial number, lander identifier, or free-text description). This is an effective design choice that collects only the platform-specific details relevant to the selected option, reducing form length and improving data relevance.
Is this log a continuation of a previous entry for the same deployment? is a yes/no question with branching logic: a yes answer prompts for the previous log reference number, while a no answer asks whether this is the first recording session. This conditional structure efficiently handles both continuation and initial-entry scenarios without burdening the respondent with irrelevant fields.
Survey objective or research question for this session is an open-ended multiline field that captures the purpose of the recording effort. This qualitative context is valuable for later interpretation and helps other analysts understand the motivation behind the session.
Hydrophone Depth (meters) records how deep the sensor was placed. This is a key physical parameter that influences signal propagation and is referenced in the distance estimation logic later in the form.
Local Water Depth at Deployment Point (meters) captures the total water column depth at the site, which can help contextualize whether the hydrophone was near the surface, mid-water, or near the seabed.
Water Salinity (PPT) is a required environmental input that affects acoustic absorption characteristics. Its inclusion here aligns with the form's stated purpose of documenting conditions that influence signal propagation.
Water Temperature (degrees Celsius), Hydrophone Sensitivity, and Sampling Rate (kHz) capture additional instrument and environmental parameters. These are optional, which may reflect that they are not always available or directly relevant to every session.
Recording Gain Setting and Channel Configuration use single-choice dropdowns with a follow-up for array element count when a hydrophone array is selected. This conditional design is efficient and collects only pertinent details.
Was the hydrophone system calibrated before this deployment? uses a yes/no structure with appropriate follow-ups: a yes answer prompts for the calibration date, while a no answer invites a description of potential interpretation effects. This is a thoughtful design that acknowledges the practical reality that not all deployments are freshly calibrated.
The two checkboxes — Sensor depth was verified with an independent pressure reading and Anti-fouling measures or protective housing were fitted — capture quality-assurance observations without requiring lengthy text entries.
Sea State is a mandatory single-choice field using a descriptive scale. This is a core environmental variable that directly affects ambient noise levels and detection range.
Wind Speed (meters per second) and Weather Conditions During Logging provide additional context on surface conditions. The weather field includes a conditional follow-up for 'Other' selections, which is a practical design touch.
Estimated Ambient Noise Level captures the background noise floor, which is important for interpreting received levels of detections.
Is the deployment site within or immediately adjacent to a commercial shipping lane? is a mandatory yes/no question with a conditional follow-up for the distance to the nearest shipping lane. This is directly relevant to the form's shipping-lane proximity flagging logic and is appropriately required.
Vessel Traffic Observed During the Logging Window uses a multiple-choice list with an 'Other' follow-up, enabling efficient capture of traffic types without requiring free-text for common categories.
Approximate Distance to Nearest Vessel During Logging and Additional environmental observations round out the environmental context with optional fields that capture conditions not covered by the structured options.
This section is the operational core of the form. It introduces the passive sonar relationship used for distance estimation and clearly explains its assumptions and limitations — a commendable transparency choice that helps users interpret the automated outputs appropriately.
The Acoustic Detections table collects nine columns per detection: Timestamp, Peak Frequency, Received Level, Visual Match, Source Level Assumption, Absorption Coefficient (formula-calculated), Estimated Distance to Source (formula-calculated), Distance to Nearest Shipping Lane, and a Within 500 m of Shipping Lane checkbox (formula-calculated). The formula columns automate the absorption coefficient estimate and distance calculation, reducing manual computation errors. The shipping-lane flag is automatically checked based on both the estimated source distance and the shipping-lane distance, which is a practical and efficient design.
The Visual Match column is described in the introductory paragraph as accepting Blue Whale, Orca, Submarine Noise, or Unknown, though the table column itself is defined as open-ended single-line text. This may be a deliberate choice to allow flexibility, but it could also lead to inconsistent entries if not carefully managed.
The sample rows demonstrate realistic detection scenarios — a low-frequency blue whale call at 0.02 kHz, an orca call at 3.5 kHz, and a submarine noise detection at 0.1 kHz — providing useful guidance for users.
Were any detections excluded from the table because they could not be measured reliably? is a yes/no question with a follow-up for descriptions. This captures important caveats about data completeness and is a good practice for observational logging.
Overall Confidence in the Visual Match Classifications is a mandatory single-choice field with a follow-up for unresolved classifications. This is an important quality-assurance measure that flags uncertainty in the detection data.
Signal Characteristics Observed uses a multiple-choice list with an 'Other' follow-up, enabling structured capture of signal descriptions alongside free-text for unusual cases.
The yes/no questions about attributable vessel/industrial activity, salinity or depth influence on signal clarity, and recommended follow-up each have appropriate conditional follow-ups that collect details only when relevant.
The ranking field for follow-up actions and the digit rating and matrix rating fields for data quality assessment provide structured evaluation tools that support quality review processes. The matrix rating covers five key aspects — recording clarity, depth/salinity accuracy, detection completeness, classification confidence, and data transfer timeliness — offering a balanced self-assessment framework.
Analyst notes, anomalies, and caveats is an open-ended multiline field that captures qualitative observations not covered by structured fields, which is essential for thorough field logging.
This section collects supporting materials through four upload fields (audio data, calibration record, detection summary/spectrogram, and deployment photo) and a map reference. The map provides an illustrative deployment area reference with example coordinates, which users are prompted to replace with their actual station location.
Station Coordinates is an optional text field for decimal-degree coordinates. The three checkboxes — raw data backup confirmation, field notebook cross-check, and third-party material removal — serve as practical data-management reminders.
The declaration section establishes accountability through a mandatory confirmation checkbox, name, submission date, and signature. The optional fields for role, reviewer, and the uncertainty-flagging checkbox add useful context without overburdening the sign-off process. The framing language correctly positions the log as an internal record without implying regulatory or scientific validation.
The form demonstrates several notable strengths: logical section ordering that mirrors the field workflow, extensive use of conditional follow-ups to minimize irrelevant data entry, formula-driven calculations in the detection table that reduce manual errors, and clear framing language that manages expectations about the nature of the data. The mandatory field selection is generally well-balanced, focusing on core identifiers, key environmental parameters, and accountability touchpoints.
Potential areas for improvement include: the Visual Match column in the detection table is defined as free text rather than a dropdown, which could lead to inconsistent classification entries; the form is quite lengthy, and while its structure is clear, field teams working in challenging conditions may benefit from a condensed summary view or progress indicator; and the formula for Estimated Distance to Source uses a simplified model that is appropriately caveated in the text, but users unfamiliar with passive sonar relationships may benefit from a worked example alongside the sample rows. Overall, the form is a well-designed, technically informed logging instrument that balances data completeness with practical usability.
Mandatory Question Analysis for Oceanographic Bio-Acoustic Log Form
Important Note:
This section explains why certain fields in this form are marked as required and provides general guidance on how these requirements may support the collection of complete, accurate and relevant information.
Required fields and information-collection obligations may vary depending on your industry, jurisdiction, business operations and intended use of the form. A field marked as required in this template does not necessarily mean that collecting the information is legally mandatory.
Please review each required field to determine whether it is necessary, appropriate and lawful for your particular purpose. Consider applicable privacy, data protection, consent and industry-specific requirements, and consult an appropriately qualified legal, privacy or compliance professional where necessary.
Please delete this section before publishing your form. See our Terms of Service for further information.
Station or Survey Identifier
Recommendation: Requiring this field ensures that every log entry can be tied to a specific deployment location or survey effort, which is foundational for record-keeping and later data retrieval. Without a station identifier, entries become difficult to organize and cross-reference. Form administrators should confirm whether a standardized naming convention is in place to maintain consistency across entries.
Deployment Start (Local Time)
Recommendation: Marking the deployment start time as mandatory establishes the primary temporal anchor for the recording session. This timestamp is essential for contextualizing all subsequent detection entries and environmental observations. The necessity of requiring the exact end time may depend on whether sessions are always logged retrospectively or in real time.
Observer/Analyst Name
Recommendation: Requiring the observer or analyst name supports accountability and enables follow-up queries about specific entries. It ensures that each record can be attributed to a responsible individual. Form administrators should consider whether capturing full names or initials better serves their internal record-keeping practices.
Deployment Platform Type
Recommendation: This field is required because the deployment platform directly influences instrument performance, signal propagation characteristics, and the interpretation of detection data. The conditional follow-ups that collect platform-specific details (mooring ID, vessel name, etc.) only when relevant further support efficient data collection. Requiring this selection ensures that no entry lacks essential deployment context.
Hydrophone Depth (meters)
Recommendation: Hydrophone depth is a core physical parameter that influences how acoustic energy propagates from source to receiver. Requiring this field supports the accuracy of downstream distance estimates and helps analysts interpret received levels. The decimal precision allowance (up to 2 decimal places) is appropriate for instrument readings.
Water Salinity (PPT)
Recommendation: Water salinity affects acoustic absorption characteristics and is referenced in the form's distance estimation logic. Requiring this field ensures that the environmental inputs needed for signal interpretation are consistently captured. Form administrators should confirm whether in-situ salinity measurements are routinely available at all deployment sites, or whether estimated values from regional data may be acceptable in some cases.
Sea State
Recommendation: Sea state is a mandatory field because surface conditions directly affect ambient noise levels and detection range. Requiring this selection ensures that environmental context is always available alongside detection records. The inclusion of a 'Not observed' option is a practical design choice that acknowledges that not all conditions are directly witnessed.
Is the deployment site within or immediately adjacent to a commercial shipping lane?
Recommendation: This question is required because shipping-lane proximity is directly relevant to the form's automatic proximity flagging logic and to the interpretation of anthropogenic noise in detection records. The conditional follow-up for distance to the nearest shipping lane collects additional detail only when the answer is yes, which is an efficient design. Form administrators should consider whether the definition of 'immediately adjacent' needs clarification for consistent responses.
Overall Confidence in the Visual Match Classifications
Recommendation: Requiring a confidence assessment supports data quality review by flagging entries where classification uncertainty may affect downstream analysis. The follow-up for unresolved classifications collects useful detail about what additional information would help. This field serves as an important quality-assurance checkpoint.
I confirm that the entries in this log reflect my own observations and the recorded measurements for this session
Recommendation: This mandatory confirmation checkbox establishes a basic accountability checkpoint at the point of sign-off. It supports record integrity by requiring the respondent to affirm the accuracy of their entries. This is a standard practice for field logging forms and helps reinforce careful data entry habits.
Name of Person Completing This Log
Recommendation: Requiring the completer's name at the sign-off stage ensures that every submitted log is attributable to a specific individual. This supports accountability and enables follow-up if questions arise about the entries. Note that this field duplicates the Observer/Analyst Name captured earlier in the form; form administrators may wish to consider whether a single name field with a confirmation step would be sufficient.
Date of Submission
Recommendation: The submission date is required to establish when the log was finalized and submitted. This supports record-keeping timelines and helps track data transfer and processing workflows. Requiring this field at the sign-off stage is a natural and low-friction requirement.
Signature
Recommendation: A mandatory signature serves as the formal sign-off for the log entry, reinforcing accountability and providing a clear record of who authorized the submission. This is a conventional practice for field documentation. Form administrators should confirm whether a digital signature capture mechanism is in place for electronic submissions.
The form's mandatory field strategy is generally well-balanced, with required fields concentrated in three areas: core deployment identifiers (station ID, start time, observer name, platform type), key environmental and instrument parameters (hydrophone depth, water salinity, sea state, shipping-lane proximity), and accountability touchpoints at sign-off (confirmation checkbox, name, date, signature). This distribution ensures that essential data is always captured while leaving detailed and contextual fields optional.
Balancing data collection depth against completion rates: The form is substantial in scope, and while its logical structure helps manage complexity, the number of fields may present friction for field teams working in challenging conditions. Keeping secondary fields optional — as the form currently does for items like contact email, water temperature, and hydrophone sensitivity — is a sensible approach that helps maintain reasonable completion rates. Form administrators may wish to monitor completion times and drop-off points to identify whether any sections need to be condensed or restructured.
Use of conditional logic: The form makes effective use of conditional follow-ups throughout — for platform-specific details, continuation references, calibration status, shipping-lane proximity, and classification confidence. This approach collects detailed information only when relevant, which reduces respondent burden and improves data relevance. Continuing this pattern for any future additions would be advisable.
Mandatory field selection and placement: The mandatory fields are distributed across the form rather than clustered in a single section, which is a reasonable approach for a multi-section logging form. However, the duplication of the observer name (captured both in the identification section and at sign-off) could be streamlined. Additionally, the Visual Match column in the detection table is currently free text rather than a dropdown; if consistent classification entries are important for downstream analysis, form administrators may wish to consider whether a structured option list would better support data quality.
Observations on mandatory field count: With 13 mandatory fields across seven sections, the required-field load is proportionate for a detailed technical logging form. The concentration of mandatory fields in the sign-off section (four fields) is appropriate for accountability purposes. Form administrators should periodically review whether any currently mandatory fields could be made optional without significantly affecting data utility, particularly for users who may be logging under time constraints or in field conditions where certain measurements are not readily available.
To configure an element, select it on the form.