Driftwise is the system of record that agencies and conservation organizations run their fisheries, habitat, and waterway monitoring programs on. Crews capture data in the field, and Driftwise turns it into the evidence your agency and funders expect.
Choose one below and the rest of the page — the example flow, mobile companion, and intelligence panels — rewrites itself to match.
Driftwise keeps catch photos, sampling CSVs, and recapture matches organized by watershed and reach. The population record stays defensible because every match is logged and reviewed.
Anglers and biologists submit photos, lengths, and locations from the field. Electrofishing and seining events upload as CSV batches.
PIT tag and mark-recapture matching links each capture to a known individual. A reviewer confirms the match before it enters the population record, so nothing gets counted twice.
Recapture intervals, growth curves, and reach-level abundance estimates come out as the figures that go straight into agency and grant reports.
Multi-stakeholder restoration falls apart when each crew keeps its own spreadsheet. Driftwise holds every infestation, treatment, and re-survey in one place, with the privacy and partner controls that shared work requires.
Field crews and volunteers drop sightings with species, density, and photos. Hotspots emerge as clusters and heatmaps when the map zooms out.
Every sighting carries a status: untreated, treated, or re-survey due. A treatment log per visit keeps the chain of custody intact across crews and seasons.
See where infestations are expanding year over year, which sites sit on top of sensitive habitat, and which treatment methods are actually holding. Shareable with partners.
When a tree comes down or the river spikes, paddlers find out from your map before they put in. A structured corridor model and a fast review workflow keep what is published accurate.
Define the trail with segments, access points, portages, and amenities. Every attribute change is versioned, so you can see who changed what and when.
Publish closures, advisories, hazards, and condition reports with a verification level and urgency attached. Conflict detection catches contradictory updates before they reach the public map.
A branded public map, an embeddable widget for your site, and shareable URLs. Visitor analytics and seasonal patterns tell you where to focus next season's programming.
Here is what a mark-recapture season looks like in Driftwise: crews log captures on the water, the data organizes itself by reach, and the monitoring report writes itself from there.
Driftwise offers fully supported in-field data collection — capture catches on-site or import them on the web, whichever fits your workflow. Offline field entries queue and sync the moment a connection returns.
Drag in a CSV of sampling events. Photos batch by event and watershed on their own. Everything files itself under the right project, reach, and reporting period.
Every observation lands on a watershed map. PIT tag and mark-recapture matching proposes links to known individuals, and a QA reviewer confirms each one before it enters the population record.
Recapture intervals, growth curves, and reach-level abundance estimates roll into dashboards your agency partners recognize. Export the exact figures that go into the monitoring report.
One shared map holds every infestation and the treatment history behind it. Partner crews see the same picture, so the same patch does not get sprayed twice or missed entirely.
Field crews drop a sighting with species, density, and a photo, even with no signal. Sensitive-habitat overlays show on the map while you log, so crews know what they are standing next to.
Every sighting drops as a point on a shared map. Clusters and heatmaps surface hotspots as you zoom out. Drill into any single sighting and the photo, GPS, and timestamp are still attached.
Each sighting carries a status: untreated, treated, or re-survey due. A treatment log captures method, crew, and conditions on every visit, so partners can coordinate timing without stepping on each other.
See year-over-year spread, which sites score highest against sensitive habitat, and which methods are holding the line. Export partner-shareable maps and the reports your funders ask for.
Plot the trail once. After that, a field report turns into a public advisory in minutes, and the way visitors use the map tells you what to fix before next season.
Group projects by state, county, or town — or by watershed resolution — into one collection, with each sub-map assigned to its own child organization. An optional parent map rolls every sub-project into a single regional view.
Draw segments, access points, portages, and amenities, or import what you already have from CSV, GeoJSON, or KML. Attribution is versioned from the first edit.
A volunteer logs a downed tree from the river. The update carries a verification level, an urgency, and the photo. Conflict detection flags overlapping advisories before anything goes live.
Your branded public map updates the instant staff approves. Color-coded status, shareable links, and an embeddable widget for your site mean paddlers see the current picture, not last week's.
Crews flag infestations and log treatments from the site itself, with sensitive-habitat overlays visible while they work.
Volunteers and rangers report a hazard from the put-in. Staff approve it, and it is on the public map before the next paddler arrives.
Identity-matched recaptures trace how fish move and grow across the river network, while a live read on study coverage and data completeness shows how much of the picture is filled in — and where the gaps are. These are the figures and methods agency reports cite.
Every number on this page is traceable back to the field record it came from.
Walk through a mark-recapture reportSpread analysis shows how infestations changed between survey periods. Priority scoring ranks sites by their overlap with sensitive habitat, so a short field season goes to the patches that matter most.
Every number on this page is traceable back to the field record it came from.
See how priority scoring builds a season planDriftwise pulls live USGS gauge readings and NOAA's National Water Model to give every reach in your corridor a current flow and a 5-day forecast.
Every number on this page is traceable back to the field record it came from.
See flow data drive a closure decisionRun a mark-recapture program, coordinate a multi-partner invasive species response, or run the waterway program for a State Park or conservation nonprofit. Driftwise is the software those organizations run on — field observations in, the evidence your agency and funders accept out. We'll demo it against your own program, not a sample dataset.
Request a demoFree 30-minute demo · No commitment · Bring your own data
Tell us about your program — a watershed, an infestation, a trail system. We'll walk through how a field record becomes the report your agency and funders sign off on, for an organization like yours.
A working call, not a pitch
We spend the time on your actual program — the data you have now and the report you owe.
Guided onboarding
We import your existing records and configure the setup alongside your team.
Start with one season
Run a single pilot first and expand when it earns the next watershed.
Send us your corridor, watershed, or program and we'll set up a working demo against your own data — not a sample dataset. We reply within one business day.
Click to reveal — we obscure the address to cut spam.