1
Map the block once
Add or confirm the fields you want Farmbit to keep in weekly view.
Field Change Alerts
Weekly watch for the blocks that still matter.
Farmbit compares mapped blocks against a rolling baseline and alerts you only when the next walk looks worth it.
Signal to field check
1
Signal shifts
Farmbit spots the block that moved enough to review.
2
Zone gets ranked
The alert shows where to start, not just that something changed.
3
Field check comes first
The note says where to start before the trucks leave.
Escalate only when needed
Alerts narrow the walk.
If the block still looks wrong after the field check, move into closer proof. If not, you keep moving.
Weekly watch
First useful check
Closer proof if still needed
How it works
How Field Change Alerts work
2
Wait for a signal strong enough to matter
Farmbit alerts only when satellite change is strong enough and persistent enough to justify a real field check.
3
Start with the first useful check
The alert points you toward the field or area that deserves the first walk, not another map to decode.
Conservative by design
An alert should be explainable before it is useful.
Farmbit is stronger when it stays selective. The alert model uses visible quality gates and baseline requirements so a weak or noisy scene does not turn into fake urgency for the field team.
>=70%
usable pixels
Cloudy or dirty scenes do not get promoted into action.
>=6
baseline observations
Thin history does not get sold as a real signal.
>=10%
affected area
Tiny noisy patches stay below the line unless the change is genuinely strong.
Farmbit still does not diagnose the cause. It flags a signal worth checking, then leaves room for closer proof when the block still needs it.
Alert reasons
Every alert needs a reason a grower can reject.
Field Change Alerts should never name a disease or pest from satellite alone. The useful decision is whether the field check is worth doing now, whether ground proof is required, or whether the scene should stay quiet.
Alert
Worth a field check now
Example reason: clean coverage passed, baseline window is strong, affected area is large enough, confidence is medium or higher, and the change persisted.
Needs ground proof
Signal is real enough to review, not enough to explain
Example reason: the block changed, but satellite cannot separate irrigation, canopy, pest-like signs, row damage, or management activity without field evidence.
No alert
Do not create work from a weak scene
Example reason: cloud, stale baseline, too little affected area, low usable pixels, or a one-scene wobble kept the signal below the action line.
Plans
Choose how many blocks still deserve season-long watch.
Field Change Alerts Starter
CAD $4.99/month
- Up to 5 monitored fields
- 30-day alert history
- Email alerts
Field Change Alerts Pro
Best for growing teamsCAD $15.99/month
- Up to 20 monitored fields
- 60-day alert history
- Email + push alerts
Need more than 20 monitored fields? Contact Farmbit for seasonal setup.
Block Reports
If the alert is still not enough, escalate one block.
Block Reports are the one-time closer-proof step after a free check or alert when one field still needs a stronger explanation or something easy to share.
CAD $10/report
- One credit = one finished paid closer check
- Priority map, result page, and PDF included
Field Change Alerts FAQ
Do Field Change Alerts use credits?
Field Change Alerts do not use credits. Credits are only for on-demand Block Reports and paid closer checks.
Which plan should I choose?
Starter fits teams monitoring up to 5 fields. Pro fits growing teams that need up to 20 monitored fields, longer history, and push alerts when available.
What if I need more than 20 monitored fields?
Need more than 20 monitored fields? Contact Farmbit for seasonal setup.
When should I use a Block Report?
Use a Block Report after a free check or alert when one field needs closer proof and one finished report.
Does Farmbit diagnose diseases or pests?
No. Farmbit is not diagnosing the cause. An alert means the satellite signal changed enough to review.