Offline submissions remain on your device for a limited retention period, giving you time to review, fix, and synchronize them before they expire. The app also provides reminders for submissions that are approaching expiration, while failed items remain available for manual action until they are successfully synchronized, deleted, or permanently removed after the retention period ends.

During synchronization, each queued submission is processed securely to prevent duplicate records and preserve your work, even if the connection becomes unstable or the application is closed. Once synchronization is successful, the visitation is automatically moved to your visitation history, while failed submissions remain in the queue so they can be synchronized again after the issue has been resolved.

The synchronization process automatically determines whether your locally saved data is ready to be submitted or requires additional action. If synchronization succeeds, the visitation is completed and appears directly in your visitation history. If synchronization cannot be completed due to connectivity or data validation issues, the app provides the appropriate recovery flow so your progress is preserved and can be completed without losing previously entered information.

When a visit is completed in Offline Mode, your data is safely stored on the device until it can be synchronized after the connection is restored. Previously saved drafts remain available, allowing you to continue from where you left off, while completed visitations are automatically moved to your visitation history once synchronization is successful. This ensures your work remains consistent even when connectivity is unreliable.

When working offline, the app follows the downloaded visitation policy, including selfie, geofence, and form validation requirements. All completed visitations and submitted data are stored securely on the device until they can be synchronized later, while offline submissions remain identifiable for reporting and audit purposes. This ensures your work can continue uninterrupted without compromising data consistency.

Auto Download adapts to your current network connection, Offline Mode settings, available device storage, and existing downloaded data. Depending on these conditions, the app may download new data, reuse an existing download, or continue without creating an offline bundle. All successful downloads are recorded alongside manually downloaded data, making it easy to keep track of the reference data available for future visitations.

The app protects downloaded data that is still being used for active visitations or pending offline submissions, preventing accidental data loss. Downloaded data is only updated through an intentional re-download and may be removed automatically or during specific sign-out scenarios based on its usage status. This approach helps preserve data integrity while keeping offline storage organized and reliable.

Downloads are processed in the background, allowing you to continue using the app while monitoring their progress from the Download Center. The app also indicates when a channel's offline data was last updated, making it easy to verify that your data is ready before your visit. If a download cannot be completed, it remains recorded as a failed attempt so you can download it again after resolving the issue.

Each setting takes effect immediately and works independently, allowing you to customize the app to match your connectivity needs without affecting other options. The selected configuration remains available throughout your current login session but returns to its default state after you sign out and sign back in.

What Is This Article About?

When a field employee completes a visitation using Offline Mode (Mode Luring), the submitted data follows a different path to the server compared to a standard online submission. Instead of being recorded in real time, the visitation is saved locally on the device, queued in Perlu Dikirim, and synchronized to the server later — sometimes minutes, sometimes hours after the visit actually happened.

To give Client Portal administrators full visibility into how each visitation was performed, the system adds specific metadata columns to exported reports. These columns tell you whether a check-in or check-out was performed online or offline, when the offline data was actually synced to the server, and where the device was at the time of sync. This information is essential for auditing field activity, understanding data freshness, and identifying patterns in your team’s connectivity conditions.

This article explains every offline-related column across the Visitation Report and Task Report exports, what each value means, and how to interpret the different scenarios you’ll encounter in your data.

Who Is This Article For?

This article is written for Client Portal administrators, operations managers, and business stakeholders who export and analyze visitation or task report data. It does not cover the mobile employee’s experience — for that, refer to the Offline Mode knowledge center articles on the mobile visitation flow.

Visitation Report: New Offline-Related Columns

The Visitation Report export now includes four new columns alongside all existing report columns. These columns appear on every exported row — both online and offline visitations.

Check-in Mode and Check-out Mode

These two columns identify whether each action was performed through the standard online flow or through Mode Luring (Offline Mode).

Each column operates independently. A single visitation can have different modes for check-in and check-out — for example, an employee might check in online but lose connection mid-visit and check out offline, resulting in an ONLINE check-in and an OFFLINE check-out. This mixed-mode pattern is common for employees working in areas with intermittent connectivity.

Possible values:

Common combinations you’ll see in practice:

OFFLINE MODE SYNC TIME

This column records the timestamp when offline visitation data was successfully synchronized to the server. For fully online visitations, this column is empty.

Possible values:

The gap between the check-in/check-out timestamps and the OFFLINE MODE SYNC TIME tells you how long the employee was without connectivity. A check-out at 10:00 AM and a sync time at 3:00 PM means the data sat on the device for approximately five hours before reaching the server.

OFFLINE MODE SYNC LOCATION

This column captures the device’s location at the moment the offline data was synchronized — not the location where the visitation was performed. This is a separate data point from the check-in or check-out location.

Possible values:

Selfie Proof Columns

When the visitation policy requires selfie capture, the check-in and check-out proof columns interact with offline submissions in the following ways:

When a selfie proof column shows DELETED BY USER, the related face recognition and liveness validation columns follow the visitation policy behavior — typically showing Not Relevant when those validation features are not applicable.

Geofence Columns

When the visitation policy requires geofence validation, the location and geofence verification columns for offline visitations reflect the location data that was captured during the offline check-in or check-out process. The employee’s device uses the latest available or cached location while in Mode Luring.

Device and App Version

The Check-in Version, Device, OS and Check-out Version, Device, OS columns remain available for offline submissions. The values reflect the app version, device model, and operating system used during the offline action — not at sync time.

Task Report: New Offline-Related Columns

Three task report exports now include two new columns that identify whether each task submission originated from online or offline processing. These columns are added to:

• Export Task Report Raw Data
• Export Compound Report Raw Data
• Export Nested Compound Report Raw Data

Submitted Mode

This column identifies whether the task submission was performed through the standard online flow or through Mode Luring.

Offline Mode Sync At

This column records the timestamp when the offline task submission was received by the server.

Compound and Nested Compound Rows

For compound and nested compound report exports, every child row inherits the parent task submission’s mode. If a task was submitted offline, all compound rows and nested compound rows related to that task show OFFLINE as the Submitted Mode and the same synchronization timestamp in the Offline Mode Sync At column.

The existing compound row mapping, metadata, parent-child relationship, and answer columns remain unchanged.

Important Notes

Only Synced Data Appears in Exports

Submissions that are still pending in the Perlu Dikirim queue — not yet synchronized to the server — are not included in any export. A task submission or visitation only becomes available in the exported report after successful synchronization. Once synchronized, the row appears with Submitted Mode as OFFLINE and the Offline Mode Sync At column populated with the synchronization timestamp.

This means that if you export a report for today and an employee still has unsynced submissions from today sitting in Perlu Dikirim, those records will be missing from the export. They will appear in future exports after they are synced.

Existing Report Behavior Is Unchanged

All existing report columns, filters, export initiation behavior, and file formats remain unchanged. The new offline-related columns are additive — they do not remove, replace, or modify any existing data. The exported file remains readable in the same spreadsheet format used by the current Visitation Report and Task Report exports.

What This Means for You

For operations managers reviewing daily field activity: the Check-in Mode and Check-out Mode columns give you instant visibility into which visits were performed online versus offline. If you see a high proportion of OFFLINE visits for a particular region or team, this may indicate persistent connectivity challenges in those areas.

For data analysts comparing timestamps: the OFFLINE MODE SYNC TIME column explains gaps between when a visit happened (check-in/check-out timestamps) and when the data appeared on the server. A large gap is normal for offline submissions — it reflects the time the employee was in the field without connectivity, not a system delay.

For audit and compliance teams: the OFFLINE MODE SYNC LOCATION column tells you where the device was when the data was synced — this is different from where the visit was performed. The DELETED BY USER value in selfie proof columns flags cases where offline-captured photos were removed from the device before sync, which may warrant follow-up.

Quick Reference: All New Columns at a Glance

Visitation Report

Task Report / Compound Report / Nested Compound Report

This article covers the Client Portal export perspective only. For information on how field employees use Offline Mode during visitations, refer to the Offline Mode knowledge center articles for the mobile experience.

The table view maintains the submitted data exactly as recorded, including complex input types and nested compound entries. Long values can be expanded for easier reading, while nested compound data can be viewed in a separate read-only window without affecting the original report. This structure provides a clear and reliable way to review detailed submissions while preserving the context of every recorded item.

The Submission Detail page preserves the report exactly as it was submitted, including skipped pages, media attachments, compound responses, and long-form answers. Rich content such as images and lengthy values can be viewed through dedicated preview windows without changing the original submission, ensuring a reliable reference for reporting and compliance.

The map stays synchronized with the visitation list, allowing you to seamlessly switch between route visualization and detailed visitation information. It also provides clear visual indicators for channels, check-in and check-out locations, route paths, and compliance details while remaining accessible even if route data cannot be fully generated.

Each exported file includes both report data and export metadata, allowing you to identify when the report was generated, who initiated it, and which filters were applied. If the exported data exceeds the supported file size, the system automatically splits the output into multiple files without changing the report structure. Once an export is completed, you can download the file from the Export Result page and use it for reporting or further analysis.

Each export request is processed asynchronously and recorded on the Export Result page, where you can monitor its progress, review the applied filters, and download the completed file within the available retention period. Export limits and expiration policies help ensure reliable system performance while maintaining a complete audit trail of every export activity.