Prepare the phone before you need offline access
Offline readiness begins while a connection still works. A phone cannot use customer data it has never received, and a new login may require internet access. Before a shift, sign in to the correct account, open the intended workspace and check that the day's customers and relevant products are available. Do this on the actual phone that will be used in the field.
Give the check a named owner. For a rep leaving a depot in Abeokuta, that may be a personal start-of-day routine followed by a quick supervisor spot check. Avoid treating 'the app opens' as proof that everything is prepared. Open a customer record and a relevant product list so missing information is discovered while someone can still help resolve it.
Run a practical start-of-shift checklist
Check the device as well as the data. Offline capture still relies on permissions and phone resources. A location-based check-in needs location access, and a site photo needs the camera and storage. A charged battery matters for the whole shift, not only the first visit. Follow your organisation's device policy for any backup power or shared equipment.
- Confirm the right user, workspace, customers and product information.
- Check battery level, available storage and access to a suitable charger.
- Confirm location and camera permissions for the required field tasks.
- Review any entries already waiting to sync or needing attention.
- Know the support contact and the agreed process for an urgent exception.
Capture work once and confirm it is saved
At each outlet, select the correct customer and record the visit or sale using the normal workflow. Check for confirmation that the entry was saved before moving on. A form still open on the screen is not the same thing as a saved record. Keep quantities and units explicit, especially if the rep will not be able to ask the office for clarification immediately.
Do not add a second copy of the same sale just because the manager cannot see it yet. While the phone is offline, a saved record has not necessarily reached the server. Use the app's status information to distinguish local capture from successful upload. If an entry cannot be saved, follow the agreed temporary recording process and reconcile it carefully when normal capture becomes available.
Handle exceptions with a clear escalation path
Consider this illustrative situation: a rep reaches an outlet and discovers that the correct product is missing from the prepared list. The rep should not select a similar item solely to make the form submit. Record the customer request through the team's agreed exception process, tell the responsible office contact and clarify how the final entry will be completed without duplication.
Another common exception is a device change partway through the day. Before signing out, reinstalling the app or moving to a different phone, check whether pending work is still stored only on the original device. Do not assume a new device contains unsynced records. Ask support how to preserve the existing entries and keep the business record tied to the original activity.
Reconnect with an end-of-shift reconciliation
When a reliable connection returns, open or resume the app and review the pending queue. Wait for the status to show what was accepted and what still needs attention. Phone operating systems can limit background work, so merely seeing signal bars is not proof that every item uploaded. Read any error or validation message before deciding what action to take.
Reconcile the number of saved visits and sales with the records received by the office. Identify missing items by their customer, time and reference rather than guessing from a total. An access or product validation issue needs a different response from a temporary connection failure. Escalate unresolved entries with enough detail for support, while avoiding unnecessary copies of customer information in open group chats.
Agree what supervisors can conclude from incomplete data
Set a reporting cutoff that recognises the difference between field activity and upload time. A quiet dashboard may mean there was little activity, but it may also mean records are still pending. Ask for sync status before drawing a conclusion about a rep's day. Keep late-arriving entries attached to their actual activity context rather than silently treating them as new work tomorrow.
Trurep supports offline mobile check-ins and sales after the workspace is prepared online. Managers receive those records after successful sync. This does not provide a live connection during an outage, offline navigation maps or guaranteed immediate background uploads. A dependable team routine combines preparation, confirmation at capture and reconciliation after reconnecting, with a clear owner for anything still unresolved.
