Bounded typed queue
Supports current DPR, attendance, material, expense, task and document mutation kinds only.
Offline sync and notifications
Know what is saved, what is syncing and what needs attention.
NIYAM mobile queues specifically supported field mutations, shows pending, synced, failed and conflict states, and keeps project notifications actionable for authorised users.
The connectivity gap
Field records become unreliable when a failed sync looks like success.
Site connectivity can change during the day. Teams need honest state and a clear recovery action, not a broad promise that every screen and action works offline.
A clear path from capture to responsible action.
Each step keeps the record, its context and the next responsibility visible.
- 01
Perform a supported field action
Queue only mutation kinds included in the current typed offline-safe contract.
- 02
See the local state
Keep pending, syncing, synced, failed or conflict state visible.
- 03
Replay when connected
Retry supported items in order while preserving identity and dependencies where required.
- 04
Resolve exceptions
Review failed or conflicting work instead of silently overwriting a changed record.
What sync and notifications covers.
Focused capabilities for the complete workflow, described within their supported operating boundaries.
Honest sync states
Distinguish pending, syncing, synced, failed and conflict outcomes.
Permission-scoped notifications
List actionable project notifications and mark one or all as read.
Clear recovery
Keep invalid, deleted, changed or unauthorised records from being treated as synced.
Evidence boundary
Current visuals prove the responsive workflow—not an entire offline product.
Approved evidence shows the Today and task experiences across desktop and responsive web. The shared contract proves the bounded queue and status vocabulary; it does not prove every NIYAM feature works offline.
- Only named mutation families
- Visible failure and conflict states
- Online-only consequential decisions remain online
A useful record has a responsible next person.
The feature supports the handoff without blurring who records, reviews or receives the information.
Field worker
See whether a supported mobile action is pending, synced or needs recovery.
Supervisor
Resume the day and retry supported field records when connectivity returns.
Project manager
Receive permission-scoped notifications and open the record that needs action.
Resilience boundary
Offline support is specific, visible and intentionally limited.
Supported queued mutations currently cover DPR create, update and submit; attendance marking; material received and used; expense creation; task updates and comments; and document upload. Approvals, payments, billing and support changes remain online-only.
- No whole-product offline claim
- No silent conflict overwrite
- No notification delivery-time promise
Questions about sync and notifications.
Straight answers about scope, review and responsibility.
Does every NIYAM feature work offline?
No. Only the mutation kinds named in the current typed offline-safe contract are supported for queued replay.
What happens when a queued record conflicts?
The item remains visible as a conflict with a recovery message; NIYAM does not silently treat it as synced.
Are approvals or payments queued offline?
No. Consequential decisions including approvals, payment recording and subscription changes remain online-only in the current contract.