Electrical Conductivity Testing Form: Record Samples, Calibration, Readings and Results

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.

Form Overview and Purpose

This Electrical Conductivity Testing Form is a comprehensive, structured record designed for measuring the electrical conductivity of chemical solutions, process liquids and selected materials prepared as extracts or eluates. The form spans twelve well-organised sections, moving logically from sample identification through preparation, instrument and calibration records, test conditions, raw readings, calculated results, acceptance criteria comparison, quality checks, safety notes, deviations and finally sign-off. This progressive structure mirrors the natural workflow of a laboratory measurement, which is a notable design strength.

The introductory section sets expectations clearly by including explanatory paragraphs on what conductivity represents, common units and the factors that can affect readings (temperature, electrode condition, sample preparation and cell geometry). Two equations describing the cell constant relationship are provided as reference material. Importantly, the form explicitly states that it is a general-purpose record template and does not replace any method, specification or procedure, which is a responsible and transparent framing.

Section: Test Request and Sample Identification

This section collects the core traceability information. Sample ID/laboratory sample number provides a unique identifier linking each record to the physical material tested. Sample name or description adds a human-readable label so reviewers can quickly understand what was measured. Batch, lot or campaign identifier (optional) connects results to production or process context, which is useful for trend analysis and root-cause work.

Sample matrix type is an effective single-choice field with ten options covering a wide range of possible materials. The conditional follow-ups for 'Solid material prepared as extract or eluate' and 'Other' ensure that unusual matrices are described in enough detail to be interpreted later. Source or sampling point grounds the result in a physical location, supporting process traceability.

Date sample collected and Time sample collected together establish the temporal origin of the sample. Collected by and Requested by (name) capture accountability. Date received for testing helps calculate holding time before analysis.

The yes/no question Was the sample received under controlled or monitored temperature conditions? is a thoughtful inclusion: its conditional branches ask for transport temperature or a description of uncontrolled conditions, which is relevant because conductivity can change with temperature and sample state during transport. Priority of the test request with a follow-up for investigation/troubleshooting contexts helps plan and prioritise work. The checkbox Sample label matches the submitted details on this form is a simple but valuable identity-check step.

Section: Sample Condition and Preparation Before Testing

Was the sample homogeneous and free of visible particles, film or phase separation when tested? uses a conditional design that asks for appearance when the sample is clean, and a description of observations and actions when it is not. This captures important context that could explain anomalous readings.

Pre-treatment applied before measurement is a well-designed single-choice field covering common treatments (none, filtered, diluted, degassed, equilibrated, sonication, pH adjustment, other). The conditional follow-ups ask for precisely the right details: filter type and pore size, dilution factor and diluent, degassing method and duration, or a free-text description. This level of detail supports result interpretation and repeatability.

Sample temperature at the time of measurement (°C) is a key input given the temperature sensitivity of conductivity. Was the sample temperature stable before the first reading? further documents equilibration or temperature drift, with appropriate conditional follow-ups. Container used for measurement records the physical setup, including temperature-controlled vessels where relevant. The multiple-choice field Select any hazard characteristics noted on the sample label or accompanying information is a practical safety-awareness step, with a follow-up prompt for precautions when the material is unknown.

Section: Instrument, Electrode and Accessory Details

Instrument type classifies the equipment used across six categories including benchtop, portable, in-line and specialised options. Instrument ID/asset or equipment number links the result to a specific device for equipment-history tracing. Instrument make and model and firmware or software version capture device identity details that may matter when interpreting data or investigating inconsistencies.

Electrode/probe ID or serial number and Electrode or cell type record the sensing element, with conditional follow-ups for inductive cell ranges and custom electrode descriptions. Nominal cell constant (cm⁻¹) is a direct input of the geometry parameter discussed in the introductory equations.

The question Was the instrument within its scheduled calibration or maintenance interval at the time of testing? documents equipment status with appropriate follow-ups. Was the electrode cleaned before testing? captures cleaning steps or reasons for not cleaning, and Was the electrode visually inspected for damage, deposits or trapped air bubbles? records physical condition with a conditional detail prompt for deposits or damage. Optional file and image upload fields allow instrument printouts and photographs to be attached, which strengthens the evidence base for each record.

Section: Calibration and Verification Records

This section is central to result credibility. Calibration status at the time of testing offers six meaningful options, including a 'not calibrated' case with a follow-up asking how the result should be interpreted. Reference or standard solutions used (nominal values) lists seven common nominal values plus an 'Other' option with follow-up for custom standards. Standard solution lot/batch identifier and Standard solution expiry or preparation date provide traceability for the reference materials themselves.

Temperature of the calibration standard during calibration (°C) is important because standard-solution values are temperature-dependent. Calibration outcome distinguishes between accepted, adjusted, failed-and-stopped and failed-but-proceeded cases, each with conditional detail prompts. Measured or recalculated cell constant after calibration, Calibration slope or electrode efficiency (%) and Blank or deionised water reading recorded before testing (µS/cm) capture quantitative calibration diagnostics.

The yes/no question Was a second standard used to verify accuracy across the expected measuring range? prompts either a second-standard reading or a note on how accuracy was established. Was automatic temperature compensation enabled during calibration and measurement? documents the compensation approach with conditional follow-ups for reference temperature selection (20 °C, 25 °C or other). An illustrative linear temperature correction equation is included as reference material.

Section: Test Method and Measurement Conditions

Test method reference links the record to a defined procedure or specification. Measurement approach covers seven strategies (single point, replicate, continuous logging, comparison, multi-temperature, dilution series, other) with conditional prompts for logging intervals and temperature controls. Conditions controlled or recorded during measurement is a multiple-choice field listing eight factors (sample temperature, ambient temperature, stirring rate, probe immersion depth, stabilisation time, vessel cleanliness, air exposure, elapsed time after opening), which is thorough without being burdensome.

Stabilization criterion or waiting time before each reading and Stirring or agitation method document the practical approach to achieving stable readings. Units in which readings are recorded ensures the measurement scale is unambiguous. Was the reported value temperature-corrected to a defined reference temperature? records the correction approach with conditional reference-temperature selection. Number of replicate readings planned, Expected or nominal conductivity value and Instrument range or mode setting used round out the conditions context.

Section: Raw Conductivity Readings and Repeat Measurements

The Repeat conductivity readings table is a well-structured data-entry grid with eight columns: reading number, raw reading, units, sample temperature at reading, correction factor per °C, a calculated corrected reading (with an explicit formula referencing 25 °C), a checkbox for whether the reading agreed with expected level, and an observations column. The inclusion of an automated calculation column is a strong efficiency and consistency feature.

The Reading set summary table captures mean, standard deviation and relative standard deviation per reading set, along with a reason for repeat. The conditional question Was any reading discarded or excluded from the calculation? promotes transparency by requiring the excluded reading, reason and authorisation to be documented. Did the instrument display any warning, error or instability message during the readings? captures instrument-level anomalies.

Section: Results, Calculation and Reporting

Reported value is based on clarifies the aggregation method (mean, single reading, median, maximum, defined temperature or other). Numeric fields for Mean conductivity reading, Lowest reading recorded, Highest reading recorded, Range and Relative standard deviation (%) capture the summary statistics. Dilution or extraction factor and Blank or background reading subtracted document adjustments applied.

Reported conductivity value and Units of the reported value are the key outputs. Reference temperature of the reported value (°C) anchors the number to a defined condition. The question Is the reported value an estimate or indicative figure rather than a fully measured value? is a thoughtful data-quality prompt with a follow-up explaining the basis. Calculation notes, conversion factors used and any assumptions provides a free-text area for documenting the arithmetic.

Section: Acceptance Criteria and Comparison with Specification

Were acceptance criteria supplied for this test? branches into either a source-of-criteria selection (customer requirement, internal specification, method limit, control chart, historical range, other) or a prompt to state how the result will be judged. Numeric fields for Lower acceptance limit and Upper acceptance limit, along with Units and reference temperature of the limits and Specification or requirement document reference, make the comparison auditable.

Outcome of comparison with the criteria distinguishes within-criteria, outside-criteria (above or below), borderline, not-applicable and cannot-determine cases, each with targeted follow-ups. Was a repeat or re-test carried out after an unexpected result? documents remedial action. The multiple-choice field Possible contributing factors reviewed lists eleven potential factors (mix-up, temperature difference, calibration drift, electrode issues, instrument malfunction, sample change, preparation error, transcription error, procedure not followed, none, other), which supports structured root-cause thinking.

Section: Quality Control, Checks and Data Integrity

Was a blank or deionised water check performed before and after the measurement sequence? captures blank readings or explains their absence. Was a control or check sample analysed alongside the test sample? records control sample identity and expected values. Was the measurement repeated or confirmed by a second operator? supports independent verification.

The multiple-choice field Records and evidence completed asks which supporting artefacts exist (raw readings, printout, checked calculation, retained sample, photographs, environmental notes). The checkbox All raw data entries are legible, dated and initialled is a concise data-integrity reminder. Was any record corrected, overwritten or re-entered after the original entry? with a detail follow-up promotes transparent change documentation.

The matrix rating question asks respondents to rate their agreement with six statements covering instrument suitability, calibration adequacy, preparation documentation, temperature handling, data support and acceptance-criteria clarity. The digit rating question captures confidence in the reported result on a 5-point scale. The ranking question asks respondents to order eight potential influencing factors by impact, which encourages reflective review of the measurement.

Section: Safety and Environmental Notes

Protective equipment used during the test records what was worn, with an 'Other' follow-up. Were any spills, splashes or exposure events recorded during the test? captures incidents and immediate actions. Handling approach for the sample and rinse liquids after testing covers waste handling options. Additional safety, environmental or housekeeping notes provides a free-text area. This section is framed as a record of what happened during the test and explicitly does not replace local instructions, which is an appropriate and responsible framing.

Section: Deviations, Comments and Limitations

Was the test carried out without deviation from the stated method? branches into either a method-reference confirmation or a deviation description, reason and likely effect on the result. Does the result require review or approval by another person before it is used? captures reviewer identity when applicable. Attachments or supporting material included with this record lists six attachment types plus 'Other'. Comments, observations and known limitations of this measurement is an important free-text field encouraging honest caveats. Would you recommend any further measurement or check on this sample? closes the loop on follow-up actions.

Section: Analyst Declaration and Sign-off

Analyst name, Date test performed and Analyst signature establish accountability for the record. Analyst role or position and Time test completed add context. Reviewed or approved by (name), Reviewer role or position, Date of review and Reviewer signature support a second-check workflow when needed. Record or report reference number for filing provides a filing reference.

Data Collection Implications

The form is designed to collect a rich, multi-dimensional dataset: sample identity and origin, sample condition and preparation history, instrument and electrode configuration, calibration evidence, measurement conditions, replicate raw readings with automatic temperature correction, derived statistical summaries, acceptance comparison and quality-assurance evidence. This data supports result traceability, repeatability assessment and structured review. The inclusion of fields for data-integrity corrections, discarded readings and deviation descriptions promotes transparent record-keeping. As with any record containing named individuals and equipment identifiers, basic data-handling and access-control practices appropriate to the operating environment are advisable.

User Experience Considerations

The form uses progressive conditional logic (yes/no follow-ups, option-indexed follow-ups) effectively, so respondents are only asked for detail when it is relevant. This reduces unnecessary typing while maintaining thoroughness. The logical section ordering follows the measurement workflow. The use of tables for replicate readings, checkboxes for simple confirmations and multiple-choice for common categories improves speed and consistency. Potential friction points include the overall length of the form — which reflects the level of detail needed for a defensible testing record — and the number of numeric fields in the results and calibration sections, where careful entry is required. The inclusion of illustrative placeholders in many fields is helpful. The introductory reference equations provide useful context without requiring calculation.

Overall Assessment

Overall, this is a well-designed, comprehensive and logically structured form that covers the full lifecycle of an electrical conductivity measurement, from sample receipt through to sign-off. Its key strengths are the progressive conditional logic that minimises unnecessary data entry, the structured tables for replicate readings and summary statistics, the built-in calculation column for temperature-corrected readings, and the clear separation of raw data, derived results, acceptance comparison and quality-assurance evidence. Areas that could be refined include streamlining optional fields where duplication exists (for example, units are recorded both in the readings table and in the results section) and considering whether some open-text fields could be converted to structured selections to improve data consistency and downstream analysis. Nevertheless, the form achieves a strong balance between depth of record-keeping and usability, and it would serve as a dependable template for documenting conductivity measurements in a variety of laboratory or process settings.

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.

Mandatory Question Analysis

Sample ID/laboratory sample number
Recommendation: Requiring this field ensures that every result can be unambiguously linked back to the specific sample tested. A unique sample identifier is foundational for traceability, record retrieval and avoiding confusion between similar samples. The form creator may wish to confirm whether a predefined naming convention should be enforced or whether free-text entry is sufficient for their workflow.

Sample name or description
Recommendation: Marking this field as mandatory supports human-readable identification, complementing the sample ID. It helps reviewers, colleagues and downstream users understand at a glance what material was measured without needing to cross-reference external systems. Requiring it reduces the risk of records being left without sufficient descriptive context.

Sample matrix type
Recommendation: Requiring a sample matrix classification helps establish the general category of material under test, which is useful for interpreting results and for any subsequent grouping or filtering of records. The conditional follow-ups for solid materials and other matrices ensure that non-standard samples are described adequately. Whether this level of classification is essential depends on how the collected data will be used downstream.

Source or sampling point
Recommendation: Capturing the sampling point as a mandatory field supports traceability back to the process, vessel or location from which the material was drawn. This is operationally valuable when results are compared across locations or used to inform process decisions. The necessity of this field depends on the form creator's traceability requirements.

Date sample collected
Recommendation: Requiring the collection date helps establish the temporal context of the sample and allows holding time before testing to be calculated. This is useful for understanding whether the sample state may have changed between collection and measurement. The date provides an anchor point for any subsequent timeline reconstruction.

Requested by (name)
Recommendation: Recording who requested the test as a mandatory field supports accountability and provides a point of contact for queries about the work. It helps link the record to a specific request and can simplify administrative follow-up. Whether a full formal name or an employee identifier is preferable will depend on the form creator's internal conventions.

Instrument type
Recommendation: Requiring the instrument type categorises the equipment used and helps ensure that the measurement context is clear. Different instrument types may have different capabilities or limitations, so this field helps anyone reviewing the record to place the result appropriately. Requiring it prevents ambiguity about the measurement setup.

Instrument ID/asset or equipment number
Recommendation: Marking the instrument identifier as mandatory supports equipment-level traceability. It allows the result to be associated with a specific device, which is useful for equipment history, maintenance tracking and investigating any inconsistencies between readings. This is a practical record-keeping measure that supports data reliability.

Calibration status at the time of testing
Recommendation: Requiring the calibration status is operationally important for understanding the reliability context of the reported result. The conditional follow-ups capture either verification details or explanations for uncalibrated use, which helps reviewers assess how much confidence to place in the measurement. The specific requirement level may vary depending on the form creator's quality practices.

Test method reference
Recommendation: Recording the method reference as a mandatory field links each measurement to a defined procedure or specification, supporting consistency and enabling others to understand or repeat the work. It also provides a basis for judging whether the test was performed as intended. Whether a formal procedure number is always available will depend on the operating context.

Units in which readings are recorded
Recommendation: Requiring the units of the raw readings prevents ambiguity in data interpretation. Conductivity can be expressed in several unit systems, and recording the unit at the point of entry helps avoid errors in later analysis or comparison. This is a straightforward data-clarity measure that supports reliable result interpretation.

Reported conductivity value
Recommendation: This is the primary output of the test, and requiring it ensures that every completed record contains a definitive result. It prevents records from being finalised without the key measurement being captured. The form creator should confirm whether rounding or significant-figure conventions should be specified.

Units of the reported value
Recommendation: Requiring the units of the reported value ensures that the headline result is unambiguous and can be compared correctly with acceptance criteria or other records. Consistent unit recording reduces the risk of misinterpretation and supports straightforward data aggregation.

Analyst name
Recommendation: Requiring the analyst name establishes clear accountability for the record and links the measurement to the person who performed it. This is a practical record-keeping measure that supports review workflows and provides a contact for follow-up questions about the work.

Date test performed
Recommendation: Marking the test date as mandatory anchors the record in time and allows the measurement to be placed in sequence with other activities. It supports timeline reconstruction and comparison with sample collection and receipt dates. This is a standard element of a complete measurement record.

Analyst signature
Recommendation: Requiring an analyst signature serves as a formal confirmation that the entries reflect the work carried out. It adds a layer of accountability and acts as a declaration of accuracy by the person who performed the test. The form creator should decide whether a digital or drawn signature better suits their record-keeping practices.

Describe the deviation, the reason for it and any likely effect on the result
Recommendation: This field is conditionally mandatory — it is required only when the respondent indicates that the test was carried out with a deviation from the stated method. Requiring detail in this case supports transparent record-keeping and helps anyone reviewing the result understand potential limitations. This conditional requirement is well-designed, as it avoids unnecessary data entry when no deviation occurred.

Overall Mandatory Field Strategy Recommendation

The form currently sets 16 fields as mandatory (plus one conditionally mandatory deviation-description field), distributed across sample identification, instrument details, calibration status, test method, reported results and sign-off. This distribution is broadly proportionate: the required fields cluster around the minimum data points needed to produce a traceable, interpretable and accountable measurement record, while a wide range of supporting detail (preparation steps, QC checks, safety notes, comments) remains optional.

Key Observations and Recommendations

• Balance between data depth and completion effort: The mandatory set is reasonably focused on core identification and output fields. Keeping the large number of optional context fields optional is a sensible strategy, since it allows thorough documentation when needed without creating barriers for routine tests. Form administrators should monitor completion rates and consider whether any optional field is consistently left blank — this may indicate either low relevance or user friction.
  
  
• Conditional logic for detailed follow-ups: The form already uses conditional logic extensively and effectively (yes/no follow-ups, option-indexed follow-ups). The conditional mandatory field for deviation descriptions is a good model. Consider whether similar conditional approaches could be applied elsewhere — for example, requiring dilution-factor details only when the pre-treatment field indicates dilution, or requiring re-test descriptions only when a re-test is indicated.
  
  
• Field placement and grouping: Mandatory fields are distributed across the form rather than concentrated at the beginning or end. This generally supports progressive completion — respondents enter mandatory data as they progress through each workflow stage. The mandatory sign-off fields at the end serve as a natural completion checkpoint.
  
  
• Units fields in two locations: Units are required both in the measurement-conditions section and in the results section. While this captures both the raw-reading units and the reported-value units, form administrators should consider whether a single dropdown or auto-populated reference would reduce redundant entry and the risk of inconsistent unit selection between the two fields.
  
  
• Signature requirements: The analyst signature is mandatory while the reviewer signature is optional. This reflects a reasonable design where the primary performer's declaration is always needed, but secondary review is situational. Organisations with formal review workflows may consider making the reviewer signature conditional on a specific 'review required' indicator.
  
  
• Periodic review: As with any structured record template, it is good practice to periodically review the mandatory field set against actual usage patterns, user feedback and the intended use of collected data. Requirements may vary by jurisdiction, industry and operating context, and what is essential for one organisation's workflow may be optional for another's.