Skip to main content
Reliability Guide

Tea Garden Attendance Without Internet

What the field app does in dead zones, how pending and failed records are handled, and what happens when connectivity returns.

By Sarbani Associates Updated September 2026 6 min read

1. Why connectivity decides everything in the field

Most estate software fails at the same point: it assumes the internet is there. Out-garden divisions, valley lines, and weighing sheds often have none. A cloud app that cannot reach its server either stops the line or pushes staff back to paper registers, and then the records have to be re-entered later.

GardenSuite takes the opposite approach. The device holds what the field needs, and the network is only used when it happens to be available.

2. Before the day: data moves to the device

Before workers arrive, the tablet is refreshed with what the field needs:

  • Workers and their face templates for the sections assigned to the device.
  • Sections, work codes, and tasks for the day.
  • Estate rules: tare, rainfall deduction slabs, fine leaf settings, task norms.
  • Configuration updates from the office.

Once this is on the device, the section is self-sufficient for the whole day.

3. During the day: records save locally

Every capture writes straight to the tablet's local storage: attendance, punch work, harvest weights, session details, GPS context. The record immediately shows a state:

  • Pending. Saved on the device, waiting for connectivity.
  • Synced. Uploaded to the office system.
  • Failed. The upload was rejected or interrupted. The record stays on the device with its error state so it can be retried.

The supervisor can open the sync view at any point in the day and know exactly where the estate stands. Nothing is lost because a signal dropped at noon.

4. When internet returns: sync and retry

When the device reaches office Wi-Fi or a coverage area, pending records upload. The supervisor then reviews what came back:

  1. Check which records uploaded and which were rejected or failed.
  2. Retry failed records where the cause is clear.
  3. Confirm recent records and session summaries on the device.
  4. Leave anything unresolved visible to the office rather than deleting it.

The office side shows the same truth from the other direction: sync status, recent activity, and every record's source and status. Nothing disappears quietly.

5. What this changes for the estate

Office staff stop reconciling paper against spreadsheets. Managers stop waiting for slips from out-divisions. And coverage stops being a reason for a section to run blind, because the day's records are already sitting on the tablet the whole time.

Common questions

Short answers to what estate owners and managers ask most

General

Yes. The field app saves every record on the tablet itself. Verification, weighing, and session work all continue offline. Records upload when the device reaches office Wi-Fi or a network area.

The field app shows pending, synced, and failed states for each record. The supervisor can open the sync view at any point and see what is waiting and what failed.

Failed records stay on the device with their error state. The supervisor can retry, and if a record is rejected, the office can see the reason through the sync status views.

No. Tare, rainfall slabs, tasks, and work codes are stored on the device, so the same rules apply whether or not the garden has signal.

Records saved but not yet synced stay only on that device, which is why end-of-day sync is part of the routine. Face template backups can be exported in a password-protected encrypted file for authorized restore.

Can't find what you're looking for? contact our team

Software that works where your sections are

Book a free demo. Sarbani Associates sets up the field app, smart scale, and office review around your garden's actual coverage. Demo, on-site setup, and staff training are free.

Built and supported by Sarbani Associates, Bagdogra, Siliguri. Many estates keep software details private. We respect confidentiality and share region-level experience.