Built for dead zones
Your cleaner is standing in the basement of a lake house with no bars. In most apps that is where the workflow stops. In FieldStay it is a normal Tuesday.
Checklists, photos, inventory counts and turnover completion all work offline. Everything syncs itself the moment the phone finds a bar — no sync button, nothing lost.
FieldStay installs to the home screen as a PWA with a service worker that caches the app shell. Screens your crew has opened on that phone come straight back from the device — not a spinner, not a dinosaur, the actual screen. Static assets are content-hashed and cached permanently.
Not a read-only cache. The full job, start to finish, on a phone in airplane mode.
The full board for every property assigned to that crew member, with times and same-day flags.
Room by room, including photo requirements and notes, cached before they lose signal.
Addresses and the property record for each assignment.
What should be stocked, and the asset ledger for the unit they are standing in.
The maintenance items attached to that property.
Every item, with its completion timestamp — the timestamps duration tracking is built on.
Including the final confirmation. The completion posts its owner-ledger expense once it reaches the server.
Photos go to their own upload queue on the device and upload on their own schedule with retries, so a 40-photo turnover in a basement is not blocked on a single failed request.
A full count session, submitted when the phone finds a bar of signal.
Report a problem against a work order, or add a property asset with its photo.
Sending queues offline. Reading the thread back needs a connection — see below.
Plenty of apps store data on the phone. The question that matters is what happens to a change made in a basement when the app gets killed, the battery dies, or the upload fails. Three guarantees:
The on-screen change and its queued upload commit in a single IndexedDB transaction. A phone killed by the OS mid-tap either has both or neither — never a checkbox that looks ticked but was never queued to send.
The queue drains oldest-first and stops on the first failure rather than skipping ahead, so two changes to the same turnover can never land out of order.
Anything that cannot sync surfaces in the app with a retry button. Work done in a dead zone is never quietly thrown away, and never sits invisibly in a queue nobody can see.
You would find these in a day of trialling, so here they are now.
Availability is an online-only screen. Crew can view their schedule offline; changing it needs signal.
Sending queues offline, but scrolling the thread back is server-rendered.
Offline support is built for the crew app on a phone. The PM side assumes a desk and a connection.
FieldStay is built offline-first for exactly this. The crew app installs to the phone and stores the day's turnovers, checklists, property details and inventory on the device, so it opens and works with no bars at all. Cleaners tick items, take photos and complete turnovers normally; everything queues locally and uploads the moment the phone finds signal again — usually before they have driven back to the main road.
Yes. The entire checklist — every room and item, including photo requirements — is cached on the phone before the crew arrives. Ticking items, adding notes and attaching photos all work with the phone in airplane mode. Completion timestamps are recorded on the device at the moment of the tap, not when it syncs, so job duration stays accurate even if the upload happens an hour later.
They are stored on the device in their own upload queue and sent independently of everything else, with automatic retries. A 40-photo turnover in a basement is not held up by one failed request, and a photo that ultimately cannot upload shows in the app with a retry button rather than disappearing.
No. Each change and its pending upload are written to the phone in a single transaction, so a phone killed mid-tap either has the change and the queued upload or neither — never a checkbox that looks ticked but was never queued. Reopening the app picks up exactly where the crew left off.
Three things need a connection: requesting time off, scrolling back through message history (sending a message queues offline fine), and the manager dashboard, which assumes a desk. Offline support is built for the crew app on a phone at the property.
No. There is no sync button to forget. The app uploads in the background whenever it has a connection, replaying changes in the order they were made. The only time a crew member sees anything about syncing is if something genuinely failed, which surfaces with a retry button.
That is the case it was designed around. Cabins, lake houses and mountain properties routinely have no usable signal inside the building even when the driveway has a bar. Because FieldStay caches everything the crew needs before they arrive and queues everything they do, the crew never has to stand outside to load a checklist or upload a photo.
Offline-first. The crew app reads from local device storage as its normal mode of operation and syncs in the background — it is not an online app with a cache bolted on. There is no separate "offline mode" to switch into, because there is no online mode to switch out of.
Genuinely — that is the test. Install it, put the phone in airplane mode, and run a turnover. Fourteen days free, no credit card.
Start free trialAlready using OwnerRez or Hospitable? OwnerRez · Hospitable