If you’re fighting patchy pit Wi‑Fi, I’ve bundled an offline-first data capture setup (ODK Collect with a lightweight Postgres sync) we rolled at our Saskatchewan UG site last month that timestamps loads, delays, and equipment status and auto-syncs when trucks hit the yard. I can share the form, table schema, and a one-page setup guide — anyone want the package or have ideas for better shift-level validation rules?
We ran a similar setup at our Labrador pit — turn on ODK Collect’s “Auto-send with Wi‑Fi” and whitelist it from Android battery optimizations, otherwise syncs nap until someone taps the screen. Small caveat: our tablets drifted a few minutes over a week, so we logged both UTC and local time and nudged NTP sync when trucks hit the yard. If you can share the form, I’m especially curious how you map status codes vs delays; barcode truck IDs killed most of our typos.
Agree with @matthew8450 on the battery whitelist — +1. For ODK Collect, we’ve cut downtime by provisioning devices with the built‑in QR code and printing it on the one‑page guide; also flip on “Auto-delete sent forms” so storage doesn’t creep and the yard auto‑sync doesn’t choke, . If you can share the form and table schema, I’ll try it on our night shift this week.
Our sync when trucks hit the yard stopped stalling once we set the ODK app’s image size to Medium and turned on ‘Delete after send’ — big photos were clogging the queue, . If you share the package, maybe include a no‑photos variant for routine loads; settings refs: Using Collect Settings - ODK Docs.