Skip to content
Lake and pond expertiseSoftware, monitoring, and consulting
Get Started

Software for universities

Field data software for university water research that survives every handoff.

LakeTech connects study configuration, field observations, manual samples, connected sensors, instrument context, review notes, and structured exports so faculty, students, staff, and research partners can preserve continuity across cohorts.

See it with your workflowExplore the platform

Teams in the field

Built around real water programs.

University researchers ask different questions than cities, consultants, wineries, or community boards, but they share responsibility for understanding water carefully. LakeTech preserves the field context that lets research travel beyond one student, season, or partner.

Stanford University
University of California, Davis

Why LakeTech for universities

A durable field and monitoring record before analysis begins.

LakeTech helps research teams configure sites, parameters, roles, forms, equipment, and collection cadence; capture observations beside measurements; document flags and review notes; and export structured records for downstream analysis. It complements statistical tools and institutional repositories rather than replacing them.

Why one record matters

Why longitudinal water research is vulnerable at every handoff.

LakeTech does not replace professional judgment. It gives that judgment a complete, usable history.

  1. 01

    People rotate faster than the study

    Students, assistants, collaborators, and field staff change, while methods and longitudinal continuity need to remain stable.

    LakeTech

    A durable study workspace

    Keep design, locations, roles, protocols, field records, sensors, and documents connected across cohorts.

  2. 02

    Context is easy to strip from data

    Files may preserve values but lose instrument status, weather, site observations, method notes, or who reviewed an exception.

    LakeTech

    Reviewable field provenance

    Preserve who collected, changed, flagged, and reviewed a record along with the context needed to interpret it.

  3. 03

    Collaboration creates version risk

    Parallel sheets and exports make it difficult to know which record is current and how a change entered the dataset.

    LakeTech

    Structured data when analysis begins

    Export usable records for statistics and specialized tools without manually reconstructing field meaning.

A day in the system

From study design to reviewable, structured export.

Each handoff adds to one continuous operational waterline instead of starting a new file.

  1. 01

    Design

    Translate the protocol

    Define sites, parameters, methods, forms, equipment, roles, and expected cadence before collection.

  2. 02

    Collect

    Keep observation with measurement

    Capture manual readings, samples, photos, notes, calibration, and connected sensors in one study chronology.

  3. 03

    Review

    Make changes attributable

    Flag records, add QA notes, document exclusions, and preserve who reviewed each decision.

  4. 04

    Export

    Move cleanly into analysis

    Create structured outputs with the identifiers and context needed for reproducible downstream work.

Shaped to your work

Protocols, field context, sensor records, review notes, and export across cohorts.

Protocol

Study-aware configuration

Create repeatable locations, parameters, field forms, methods, roles, and collection schedules.

Teams

Roles across cohorts and partners

Give contributors appropriate access while preserving continuity as people enter and leave the project.

Provenance

Timestamped field context

Keep the record's source, location, method, instrument, collector, observations, and attachments together.

Review

Flags and QA notes

Document the human review that turns collected data into a defensible research record.

Export

Portable, structured datasets

Move records into statistical, GIS, or modeling environments with stable identifiers and useful context.

Different mandates. One shared commitment.

LakeTech customers span private lake-management businesses, wineries, public agencies, parks, consultants, universities, and resident communities. Their mandates differ, but they share one thing: they care about their water and need a clear record to manage it well.

All customer types
Software for consulting firmsOne field-to-client water record for environmental consulting teams.Software for wineriesWinery water management software for every reservoir, pond, and season.Software for water districtsSource-water monitoring software for water district operations and reporting.

Questions from universities

What teams ask before bringing their water program into LakeTech.

Can LakeTech combine field observations and continuous sensor data?
Yes. Manual readings, samples, photographs, field notes, and connected monitoring can be organized in the same study chronology while retaining their different sources and contexts.
How does LakeTech help when students or research assistants change?
Sites, parameters, roles, protocols, forms, equipment context, and prior records remain attached to the study, reducing the amount of project knowledge that depends on one contributor.
Is LakeTech a research repository or statistical analysis platform?
No. LakeTech is the operational field and monitoring record. Structured exports support downstream statistics, GIS, and modeling, while formal archiving, publication, and reproducibility requirements remain with the research team and its institutional systems.

Bring your real workflow

Give the study a record that survives the semester.

We'll review your protocol, field roles, data sources, and export needs to shape a practical research workspace.

Plan a research workspace