Report what was observed
Choose the crop season, farm, field or zone, issue type, observed time, description, photo, and immediate action taken.
MOBILE IRRIGATION ISSUE REPORT
Report an irrigation problem without losing the field context
Capture the field or zone, observed condition, photo, immediate action, severity, and crop-impact risk—then route triage, response, return, and verified resolution.
The reporter describes what they observed and any immediate action. The designated owner decides priority and response. Jodoo does not control irrigation equipment or provide engineering or agronomic advice.
Free for up to five users. No credit card required.
Adapt fields, workflows, and dashboards without code. Explore 1,000+ app templates and use cases
Sign in to inspect fictional sample records. Install a copy before adding production data, crew access, agronomic guidance, or your own operating rules.
Observedfield facts come from the reporter
Triagedseverity and ownership are reviewed
Verifieda submitted repair may still reopen
Keep the first observation separate from the final decision
This prevents the person reporting a leak or pressure problem from having to decide technical priority, ownership, or closure.
Triage the response
Review severity and crop-impact risk, choose whether to monitor, schedule, respond now, or isolate the area, and assign an owner and target.
Submit the resolution
The response owner records what was repaired or changed, adds the relevant evidence, and submits the issue for verification.
Verify or return
A reviewer accepts the field condition or returns the record with a precise reason. The earlier response remains visible in the issue history.
Give each person the part of the issue they can genuinely decide
This keeps the report easy for crews and the response accountable for managers.
| Role | Records | Does not decide | Finish condition |
|---|---|---|---|
| Reporter | Location, observation, photo, immediate action | Priority, owner, technical acceptance | Report submitted with usable context |
| Triage owner | Severity, crop-impact risk, response, owner, target | Final repair acceptance without supporting evidence | Issue assigned or monitored deliberately |
| Response owner | Work performed, evidence, submitted resolution | Their own final approval | Resolution ready for review |
| Reviewer | Verification or return reason | Agronomic or engineering advice outside their role | Verified result or clear correction request |
Ask for observable facts before technical conclusions
Clear prompts improve the report without turning a phone form into a long inspection.
Location
Use the farm, field or zone, and crop-season relationship so the responder knows where the issue belongs.
Observed condition
Offer plain issue types such as leak, low pressure, blocked line, flooding, missed irrigation, or pump/controller fault plus a free description.
Immediate action
Record whether the reporter closed a valve, isolated an area, marked a hazard, notified a supervisor, or took no action.
Evidence
Allow a photo or reading when it helps the response, but do not force the reporter to invent unavailable measurements.
Use issue history to improve response and prevention
The dashboard should show where the same kind of problem returns, how long it remains open, and why resolutions are rejected.
Overdue response
Surface target response times that have passed, especially urgent or isolated areas, with the current assigned owner.
Returned resolution
Review missing readings, incomplete evidence, unsuccessful repairs, or unresolved field conditions that caused reopening.
Repeated location or type
Group issues by field, zone, issue type, equipment reference, and resolution so the farm can decide whether a deeper maintenance action is needed.
CHANGE THE WORKSPACE AS THE FARM CHANGES
Change issue categories and escalation without coding
Operations owners can fit the report and review path to the irrigation system and response team.
Build an issue-response app in hours and adjust triage rules or evidence prompts in minutes.- 01Add a zone, issue type, condition, or immediate-action choice.
- 02Show a measurement or photo prompt only for the issue types that need it.
- 03Change the owner, reviewer, target, or urgent queue as responsibilities move.
- 04Create a repeat-issue view by field, type, age, or returned resolution.
This workflow coordinates response; it does not control irrigation
This focused workflow makes it easier to judge whether the template fits the farm’s irrigation-response process.
Included
Mobile reporting, field and crop context, triage, ownership, target response, resolution, review, return, verification, and repeat-issue visibility.
Connect to maintenance when appropriate
Create or link a maintenance work order when the issue points to a repair that needs parts, labor, downtime, and equipment history.
Keep technical authority external
Do not treat the template as engineering, irrigation-design, agronomic, chemical, safety, or compliance advice.
Questions to settle before crews start reporting
What should an irrigation issue report include?
Include the field or zone, crop-season context, issue type, observed time, plain description, photo if useful, immediate action, and reporter. Triage can then add severity, risk, owner, response target, and decision.
Should the reporter choose urgency?
The reporter can flag observable danger or impact, but a designated triage role should own the operational priority, response route, and assigned owner. This reduces inconsistent or self-approved closure.
Can a repair be returned for correction?
Yes. The native review path keeps a submitted resolution pending until a reviewer verifies it. A return reason remains attached so the responder can correct and resubmit the same issue.
Does this connect to farm maintenance?
It can retain an equipment reference or related work order and link the issue to a maintenance tracker. Use the maintenance system for parts, downtime, preventive schedules, and full equipment history.
INSPECT THE WORKING FARM SYSTEM
Report a problem from a phone, then inspect the returned resolution
Use the fictional sample to see how a clear field report becomes triaged work and remains open until the response is accepted.
Open the irrigation report