Frontline networks fail in walk-in freezers, yards, and basements. The honest question is which employee actions still work when they do. A pass-through that keeps no HR data has a short answer: actions that need Workday do not work offline, and they must not pretend to.
Kiweely Leaf (coming next) is that pass-through. “Zero HR data at rest. Read on demand, gone when the request ends.” The phone app can be installed. The layout is configuration, not a cache of balances, payslips, or schedules. When the request cannot reach Workday, the screen has nothing true to show.
What you can promise
The shell can open and say it cannot reach Workday. The worker retries when they have a signal. A submit that did not receive a Workday success is not submitted. Show that. A queue on the phone that sends the request later would hold the worker’s time-off dates or expense lines on the device, which is worker data at rest. The public design does not offer that queue.
You can promise that a published layout is what they will see once the network returns, because the layout is stored as configuration and the data is read again. You cannot promise that yesterday’s balance is still right. Accruals and approvals change on the server.
What Workday already solved for punches
Workday Time Kiosk is built for a shared tablet that must record check-in and check-out during a local outage or Workday downtime. It stores locally encrypted employee data for 30 days. A worker can check in offline only if they checked in on that device while it was online within the previous 30 days. Data transmits when the app reconnects. Workday’s Time Kiosk FAQ says to expect 10 to 20 minutes after reconnect before offline punches appear in Workday. The kiosk is included with Time Tracking, it is a separate app from Workday mobile, and Workday does not recommend it on personal phones.
That is the offline promise for punches. It is not transferable to a Leaf payslip or time-off screen. Different app, different storage rules, shared device rather than a personal phone. If the floor loses network, punches belong on a kiosk that has been online in the last 30 days. Payslips and elections wait.
| Action | Offline |
|---|---|
| ActionSee a cached PTO balance in Leaf | OfflineNo. Leaf does not keep the balance. |
| ActionSubmit time off later from a phone queue | OfflineNo. That queue would store the request. |
| ActionCheck in on Workday Time Kiosk | OfflineYes, within Workday’s 30-day device rule, then sync. |
| ActionTrust a number painted from the last successful load | OfflineNo. Show a failure until a live read succeeds. |
Poor connectivity is the same rule with more frustration. A timeout is a failed read. Retry. Do not fill the card with a stale figure and a small “as of yesterday” footnote. People will use the figure.
Tell us the floor actions you need. If one of them is punch, say you already use Time Kiosk, and keep punch there.