From data to decision

How Castwise turns fishing data into a decision

Other fishing apps give you the data. Castwise tells you what to do with it. Castwise is rolled out across the UK and ready to use for shore-fishing planning wherever you fish. A deterministic engine turns mark data and live marine conditions into transparent species and session recommendations, then AI explains the result in plain English.

The method, in short

How does Castwise decide where to fish?

Castwise uses a deterministic scoring engine. It scores each mark for each target species using tide, tidal range, season, time of day, wind, swell, pressure, ground type, structure, depth, clarity, sea temperature and moon/solunar factors, then ranks the results.

Does the AI choose the fishing marks?

No. The maths is done by a deterministic scoring engine. The coach receives approved mark, condition and score context, while server checks prevent it from changing the app’s mark or safety decision. Its explanation is still AI-generated guidance and can be wrong.

What is the difference between the score and the confidence?

Fishing potential estimates how well the species, mark and conditions line up. The recommendation score is that potential after transparent safety penalties. Confidence describes the completeness and quality of the inputs; it is not a catch probability.

Is safety part of the fishing score?

Safety is assessed separately from fishability, then detected risks can lower the ranked recommendation score. High-risk options remain visible and require acknowledgement before planning or directions; critical conditions or missing essential weather, marine or tide data make a result non-recommendable.

What data goes in

Each recommendation blends public or private mark features with live or forecast conditions. Missing essential safety data blocks a recommendation; other missing or estimated inputs are surfaced through confidence and data-quality labels.

The mark

Ground type, depth, structure (reef, kelp, gullies, sandbanks, drop-offs), exposure, casting range, difficulty and known species.

The tide

Tide stage, direction and the spring–neap range — because the strength of the run, not just the time of high water, drives the fishing.

The sea and sky

Wind, swell height and period, atmospheric pressure, sea temperature, water clarity, and moon/solunar feeding periods.

Your history

Your own logged catches and blanks, plus anonymised community outcomes where available, as priors that personalise results.

Safety context

Tide cut-off, access difficulty, exposure, swell, wind, lightning, darkness and data gaps are assessed separately and listed as individual concerns.

Data confidence

Fresh, complete inputs raise confidence. Missing, estimated or stale inputs are shown honestly instead of being invented.

Score versus confidence

Castwise separates three questions. Fishing potential is the raw 0–100 match between species, mark and conditions. The recommendation score is fishing potential after transparent safety penalties. Confidence describes the completeness and quality of the evidence behind the result; it is not the chance of catching.

A mark can have strong fishing potential but rank lower because exposed swell, strong wind, darkness or tide-cut-off adds risk. A result can also have lower confidence when mark detail is estimated or forecast inputs are stale. Both cases tell you why extra checking is required.

How safety changes a recommendation

Every detected concern is listed with its reason and a practical action. High-risk marks can remain recommendable, but they receive point penalties and require an explicit acknowledgement before planning, directions or starting a session. Critical conditions — or missing essential weather, marine or tide data — make a result non-recommendable. Extreme air temperature is still shown as an exposure warning, but it does not reduce the score because it does not distinguish nearby marks; sea temperature remains part of species suitability.

How it learns over time

The engine is deterministic, but it is not static. Your logbook builds a private picture of the baits, rigs, tides, ground and seasons behind your own results. When community contribution is enabled, completed catches and blanks can also enter thresholded aggregate learning. No aggregate bucket is published below eight sessions from five anglers, and private mark IDs or private region labels do not enter public mark or regional statistics. Community evidence nudges and calibrates the model; it does not replace the factor breakdown.

Limitations and responsible use
  • Forecasts can be wrong or go stale between updates — treat every score as a plan, not a promise.
  • Sea conditions can change quickly; swell, wind and visibility on the day can differ from any forecast.
  • Local access, parking, private land and seasonal restrictions must always be checked yourself.
  • Castwise is guidance, not a navigation or safety device, and does not replace your own judgement on the coast.
  • Fishing scores are guidance, not guaranteed catches.

Frequently asked questions

How does the logbook improve recommendations?
Every completed session you log — catches and blanks — can improve your private recommendations. If “Help improve Castwise” is enabled, its outcome can also enter sample-gated aggregate learning; the individual log and exact private mark remain private.
Do community reports change the scores?
Where enough evidence exists, thresholded catch and blank rates by species and condition can gently calibrate the wider engine. A bucket needs at least eight sessions from five anglers. Private mark IDs and private region labels are excluded from public mark and regional aggregates.
Can the recommendations be wrong?
Yes. Forecasts can be wrong or stale and sea conditions change quickly. Castwise scores are guidance to plan around, not guarantees. Always verify tide, access, weather and local safety before you fish.

Castwise updates

Turn the data into a decision.

Use Castwise for transparent UK shore-fishing recommendations you can understand and check.