The Android app for site teams
What the field app does, how offline sync behaves, and how to roll it out to supervisors so the data actually arrives.
The web app is for the office. The Android app is for the people whose hands are dirty and whose signal is unreliable, and it is deliberately smaller.
What is on the app
- Attendance for the crews on your assigned projects.
- Progress against BOQ lines, with photos.
- Site visit logs and daily notes.
- Material receipts, with the docket photographed at the gate.
- Read access to the BOQ lines relevant to the work.
Finance, payroll and company settings are not on the app. That is a deliberate scope decision: the field app should be usable in thirty seconds, and every screen added makes the important ones harder to find.
Offline behaviour
- 1
Entries save locally first
Recording never waits for the network. The entry is on the device the moment it is saved.
- 2
Sync happens automatically
When a connection returns, pending entries upload in the background, oldest first.
- 3
Pending items are visible
The supervisor can see what has not yet synced, so nothing is silently stuck.
- 4
Photos upload last
Data first, then images, so the record is complete even on a slow connection.
Ask supervisors to open the app once inside coverage at the end of each day. Entries queued for weeks on a device are entries at risk of a lost or broken phone.
Rolling it out
- 1Install it on the supervisor phone yourself, and log in with them present.
- 2Assign them to exactly one project for the first week.
- 3Ask for attendance only, every day, for five days.
- 4Review the week together and add progress logging in week two.
- 5Only then add photos and line coding.
If a supervisor stops using it, the reason is almost always a specific friction: a slow screen, a login that expires, or a required field they do not have. Ask what took too long rather than reminding them of the policy.