Farm task management, from observation to verified work
A reading that dropped, a probe that went quiet or a pivot due for a check becomes a work order with a parcel, a person, a due date and the evidence it needs. Crews record notes and photos from a phone, supervisors verify or send work back with a reason, and the lifecycle is enforced on the server, so no screen can skip a step.
How it works
- 01
Create the work order
Choose the parcel, type, priority, due date and the evidence required, from fifteen kinds of field work.
- 02
Assign people and crews
Give it to a person or a crew under a supervisor, with each person’s load in view and a warning for overlapping work.
- 03
Verify before it counts
Review the notes, photos and measurements against the original instructions, then accept the work or return it.
What it covers
What needs review, first
Detectors read the observation series, the forecast and the task table and raise what deserves a closer look, without repeating a finding you have already acknowledged. Notifications climb a ladder your organization configures instead of piling up unread.
Work orders and their proof
Turn an observation into a task carrying its field, its person, its priority, its due date, its instructions and the proof it requires, across fifteen kinds of work from irrigation checks and scouting to spraying, pruning and harvest. The crew submits photos and notes from a phone; a supervisor verifies the work or sends it back with a reason. The status lifecycle is enforced on the server, so no screen can skip a step.
Assignments, crews and workload
Assign a job to one or more people, a crew and a responsible supervisor while seeing what each person already has outstanding. Queues for due today, overdue, blocked and awaiting review sit beside the day’s shifts and the fields they cover, with workload by crew, supervisor or crop. Overlapping assignments and shift conflicts are flagged, and going ahead anyway records the reason. These are counts of recorded work, not hours or payroll.
Evidence from where the work happens
Notes, photos previewed before they are sent, files, measurements with their units, quantities and checklists — and, only with the worker’s consent, the current location. The task shows which required proof is attached and which is still missing, and cannot be completed until it is all there; the supervisor then reviews it beside the original instructions.
When the signal drops
Task actions and evidence, photos included, wait on the device and are sent when the connection returns — even after the tab is closed, if the browser keeps its storage. Each item reads saved on this device, waiting to sync, sent or needs attention, and sent is never confused with verified. It covers work pages already opened, not every map and report, and acceptance on real handsets in the field is still pending.
Notifications that lead to the work
An in-app inbox for twelve kinds of notice: a task assigned, due soon, overdue, blocked, awaiting review or reopened; a shift changed; an attention item assigned; severe weather, a plant decline, a new satellite pass or a gap in imagery. Each opens the record it is about, unread notices stand out, and you can mark one or all as read. Notices stay in the app; farm alerts are not sent by SMS or WhatsApp.
What to keep in mind
Working without signal
Task changes and evidence are saved on the device and sent when the connection returns. Acceptance on real handsets in the field has not been completed yet, and this page will say so until it has.
Questions
A useful tool should be clear about what it can do, and where your judgement still matters.
What happens without a connection?
Task updates and evidence can queue on the device until connectivity returns, where supported. They remain labelled as waiting to sync. Real-handset field acceptance is still pending; confirm the workflow on your devices before relying on it.
Who can see my fields and tasks?
Access follows workspace membership, role and assignment. Supervisors see their assigned fields, and workers see the tasks assigned to them. Organization access is configured with your team.
Does Mothmr diagnose pests or disease?
No. A falling reading, a zone lower than the rest of the field or a low probe value is a reason to inspect, shown with the dates and figures behind it. Mothmr does not diagnose pests or disease, prescribe a product or a dose, or calculate an irrigation amount — the person in the field decides.
See it on your own fields
Tell us about your farm and the work you want to coordinate, and we will plan a demonstration around your fields and roles.
Request a demo