Offline & Mobile Features

EQMS includes a suite of mobile and offline capabilities that allow field personnel to capture data, complete forms, record signatures, and maintain audit trails even when network connectivity is unavailable. Data is stored locally and synced to the server when connectivity is restored.

Mobile Device Features

The Mobile Features panel detects and utilizes native device capabilities.

Device Capabilities

On load, the system detects available hardware:

• Camera — for photo capture and barcode scanning
• GPS — for location capture and continuous tracking
• Vibration/Haptics — for tactile feedback on actions
• Notifications — for local push notifications

The capabilities panel shows green/red indicators for each feature along with platform, model, and OS version information.

Camera

• Take Photo — capture a photo using the device camera (saved to gallery)
• Pick from Gallery — select an existing image from the device photo library
• Recent photos are displayed in a thumbnail strip (last 5 photos retained)

Location

• Capture Location — get a one-time GPS fix with coordinates, accuracy, and altitude
• Start/Stop Tracking — continuously monitor position changes
• Accuracy is rated as Excellent (<10m), Good (<50m), Fair (<100m), or Poor (>100m)
• Copy coordinates to clipboard or share via the device share sheet

Barcode Scanner

• Scan barcodes using the device camera
• Supports multiple barcode formats
• Recent scans are listed with format, raw value, and display value
• Copy or share scanned values directly

Offline Forms

The Offline Form Manager lets you create, save, and submit quality forms without network access.

Creating Forms

Select a form type from the dropdown:

Form Type	Fields
Document Form	Title, Description, Category (SOP/Policy/Procedure/Form), Version, Effective Date
Training Form	Course Name, Instructor, Duration, Training Date, Participants
Deviation Report	Title, Description, Severity (Low/Medium/High/Critical), Date Discovered, Discovered By
Generic Form	Name, Email, Message

You can also add custom fields to any form using the Add Field button.

Form Lifecycle

Forms move through the following statuses:

1. Draft — saved locally, not yet queued for submission
2. Pending — queued and ready to submit when online
3. Submitted — successfully sent to the server
4. Failed — submission attempted but unsuccessful (can be retried)

Batch Upload

When connectivity is restored, use Upload All to submit all pending and failed forms in a single batch operation. The status dashboard at the top shows counts for each status.

Caution

Forms cannot be submitted while offline. They are stored locally in IndexedDB and queued for submission when the device goes online.

Offline Data Manager

The Offline Data Manager handles arbitrary data types that need to be stored locally and synced.

Data Types

• Document — document metadata and content
• Form — form submission data
• Audit Trail — audit log entries
• Signature — electronic signatures

Conflict Resolution

When syncing, conflicts can occur if the same data was modified both locally and on the server. Each data item has a conflict resolution strategy:

Strategy	Behavior
Server Wins	Server version overwrites local changes
Client Wins	Local version overwrites server data
Manual Resolution	User is prompted to choose which version to keep

Storage Monitoring

The manager displays storage usage (used vs. available) and individual item sizes. Use Clear Synced to free up local storage by removing successfully synced items.

Sync Operations

The Sync Operations panel manages data synchronization between the device and server.

Sync Types

Type	Description
Upload	Push local data to the server
Download	Pull server data to the device
Bidirectional	Two-way sync with conflict detection

Operation Lifecycle

Each sync operation progresses through:

1. Pending — created but not yet started
2. In Progress — actively syncing
3. Completed — finished successfully
4. Failed — encountered an error (can be retried)

Use Sync All to execute all pending operations at once. Click the eye icon on any operation to view detailed status, timing, and error information.

Conflict Detection

Bidirectional sync may detect conflicts. When conflicts are found, they appear in the operation details with options to resolve each one by choosing either the server or client version.

Tip

Use the “Retry Failed” button to re-queue any failed sync operations without having to recreate them.

Offline Audit Trail

The Offline Audit Trail maintains a tamper-evident record of all actions performed while offline.

Audit Trail Entries

Each entry records:

• Action — Create, Update, Delete, Approve, Reject, Review
• Entity type — Document, Training, Deviation, Audit, Signature
• Entity ID — the specific record affected
• Location — GPS coordinates (if captured)
• Device info — platform, model, OS
• SHA-256 hash — cryptographic hash for integrity verification
• Timestamp — when the action occurred

Mobile Signatures

Capture electronic signatures on a touch-enabled canvas:

1. Click Sign to open the signature capture modal
2. Draw your signature on the canvas
3. Optionally associate the signature with a document ID
4. Click Save Signature to store it locally

Signatures include GPS location (if captured), device information, and a SHA-256 integrity hash.

Syncing Audit Data

Click Sync to push all pending audit trail entries and signatures to the server. This ensures offline activities are recorded in the central audit log.

Note

All offline audit trail entries and signatures are hashed using SHA-256 to ensure data integrity. The hash can be verified to confirm that records have not been tampered with since creation.