Skip to main content
This guide covers running EC inspection rounds from the Forager Android app. The flow is built for speed — a practiced inspector clears an item in under 30 seconds.

​
Finding your work

If your company holds an EC Item license, a Rounds card appears on the app home screen. It has two views:
  • Due Queue — every item currently due or overdue, grouped by building then floor, with due-soon and overdue badges. Filter by item kind. This works with no setup — items surface automatically on their cadence.
  • Rounds tab — explicit rounds an admin has assigned to you, with a progress bar. Execution is identical to the due queue.

​
Running a round

  1. Open a floor — the floor plan shows a pin for every due item, and the app suggests the nearest next item so you walk an efficient route.
  2. Scan the item’s barcode or QR label.
  3. Photo — capture the evidence photo (an RF snapshot is recorded automatically in the background).
  4. Checklist — answer the core questions and any facility-added questions. Pass/fail is derived automatically from your answers; you can override the result with a reason.
  5. Move to the suggested next item.
First-touch pin placement. Items imported from CSV start with an automatic pin at the center of their assigned room. The first time you inspect one, the app asks you to tap the item’s true position on the floor plan — pre-centered on the room, one tap. After that, the pin is exact for everyone.

​
Failed items

Failed inspections collect in a failed tray for the session. At the end of your round, review the tray and push failures into a remediation sprint so they get dispatched and tracked.
Inspectors can add failed items only to an existing active sprint. Creating a new sprint is admin-only — if there’s no active sprint to add to, ask an admin to open one.

​
Working offline

Rounds run fully offline. When you enter Rounds mode with connectivity, the app syncs down your due queue, checklists, and floor-plan images. After that:
  • Inspections, photos, and evidence write to a local outbox on the device
  • The outbox syncs automatically when connectivity returns — no action needed
  • Each inspection carries two timestamps: performed-at (when you captured it, from the device clock) and synced-at (when it reached the server)
Compliance credit is based on when you performed the inspection, not when it synced. Nothing about being offline changes the flow — scan, photo, checklist, next.