What Works Offline During a Rental Property Visit

Weak cellular service should not turn a property visit into a memory exercise. The useful offline boundary is narrower and more practical: capture the facts locally, review them on the device, and make the pending state visible until cloud work can resume.

Core visit work can continue without a connection while sync, backup, billing, and provider processing remain visibly pending or unavailable.

Prepare before you lose service

Open the correct property and tax-year workspace while you still have a reliable connection. Confirm that the current account has a verified local copy. If the app cannot establish that safe account-scoped copy, continuing offline should not expose old or another user’s data.

For the visit itself, note the tasks you expect to inspect, but do not create completed records in advance. Bring an independent way to preserve essential source material when the visit is critical. A local-first app reduces reconstruction; it does not replace an appropriate backup plan for the property.

The core visit can stay local

HostHours supports these activities locally:

• manual record capture;
• review of records already in the local workspace;
• navigation between available workspaces;
• the activity timer;
• typed or local Voice input before provider processing;
• local CSV parsing and mapping;
• part of the attachment lifecycle;
• pending changes waiting for synchronization.

A simple visit routine is enough. Start the timer when the work begins. Pause it when the task stops. Finish when the work is done, then review the detailed entry draft. The timer does not create a record automatically.

Before saving, confirm the property, date, person, category, duration, and factual result. If the owner inspected a water heater while a contractor replaced a valve, keep the two people and their work distinct. Attach a photo when it adds context, but do not treat the file as cloud-backed until the upload status confirms it.

The timer uses timestamps

The timer uses timestamps rather than an on-screen counter. It can survive the screen being locked and return to the running or paused state. Home can also direct the user back to an active timer.

Finish still leads to review. If an unusually long timer would exceed the 23-hour limit for one ActivityEntry, HostHours splits it into several records, with no more than 31 records from one save. That safeguard is not an invitation to run a timer across several unrelated days. Stop and review each distinct task when practical.

Do not assume that the app will finish syncing while it is closed. Pending sync is retried when the app returns to the active state and periodically while active. Check the state after service returns.

Some work still needs the network

The following depend on a connection:

• Supabase synchronization;
• cloud backup for attachments;
• entitlement reconciliation;
• provider-backed Voice draft processing;
• checkout and subscription operations;
• remote report-history resolution;
• provider-backed Recall or Readiness work.

Keep those boundaries visible during the visit. A locally selected photo may still be uploading. Typed Voice input may be safe as a local draft even though structured processing cannot run. A manual entry can be complete on the device while its cloud revision is pending.

Clear language is better than an optimistic spinner. “Saved locally, sync pending” tells the user what is safe and what remains open.

Reconnect without silent overwrites

HostHours uses a revision number for the workspace snapshot. A cloud save compares the revision it started from with the revision currently stored. If they differ, the app does not choose a winner silently.

The recovery view lets the user retry, reload the cloud copy, or continue offline with pending sync when the local copy is safe for that account. Each option carries a different consequence. Reloading discards the local conflicting view in favor of the cloud state. Continuing offline preserves local work but leaves synchronization unresolved.

Read the conflict before choosing. If another device changed the same property, compare the recent entries and revision context rather than repeatedly pressing retry.

One downgrade edge case deserves attention

History remains readable after a downgrade, but a property created only on the device creates a verification problem. If it never reached the server before the entitlement changed, the server cannot confirm that it predates the downgrade.

That case fails closed. The local workspace is not silently grandfathered. The documented recovery is to restore the previous plan or export the local workspace rather than forcing an uncertain sync.

End the visit with a sync check

After service returns, bring the app to the foreground. Check pending records, attachment status, and any conflict message. Open the day’s entries and make sure each task is assigned to the correct person and property. Resolve missing uploads while the original files are still on the device.

Local-first design is useful when its boundaries are explicit. The work can continue at the property. Cloud actions wait, and HostHours shows their pending state.

HostHours organizes factual records. It does not guarantee connectivity, cloud backup before upload confirmation, or a tax outcome for any recorded activity.