Trouble spots

A trouble spot is a GPS-pinned report of something in the field that needs attention. A diseased vine, a broken dripper, a fallen post, a missed irrigation — anything worth coming back to. Trouble spots are short-lived: you report them, you work on them, you mark them complete, and they go away.

📷 Screenshot: Mobile map view with several trouble spot pins shown over blocks.

The lifecycle

1. Reported — someone in the field drops a pin, picks a type ("Disease → Powdery mildew", "Irrigation → Leaking dripper", etc.), and saves.
2. Pending — the spot sits on the list, waiting for someone to do something about it.
3. Completed — whoever does the work marks it complete. The pin is archived (you can still see it in the history).

Categories and types

Trouble spots use the same two-level taxonomy as field features: a category (for example, "Disease") and a type within that category (for example, "Powdery mildew"). The list is partly managed at the platform level and partly by your organisation — so you might see some standard entries plus any your team has added.

Where trouble spots are reported and worked

• Reporting happens in the field, from the mobile app. There's a work mode for when you're doing a walk-through and reporting many spots of the same type in quick succession — see Reporting a trouble spot.
• Viewing and triaging happens on both the mobile app and the portal. Field staff use the mobile "Near me" view to find the closest spots to work on; office staff use the portal to see everything across all sites.
• Completing is usually done from the mobile app, in the field, by whoever has resolved the issue.

Pages in this section

• Reporting a trouble spot — mobile
• Viewing trouble spots — mobile and portal
• Completing trouble spots — mobile
• Managing trouble spot work — (coming soon)