A mobile work routine should keep urgent tasks moving while preserving a reliable record for the rest of the team. Its purpose is to prevent actions from becoming scattered across notifications, personal messages and unsynchronised drafts.
Before adopting this routine, use the phone-versus-desktop task assessment to decide which actions your business permits on mobile.
Start with the authoritative system
Open the shared task, customer or order system before acting on notifications. Identify the owner and status of the work. A notification may be old, duplicated or already handled by someone else.
For each action, record what changed in the system the team actually uses. A message saying “done” is not a substitute for a completed order or updated task status when others depend on that record.
Separate viewing, drafting and approval
- View: inspect alerts, schedules and records without making an irreversible commitment.
- Draft: prepare a response or document, clearly marked as awaiting review.
- Approve: proceed only when the authorised mobile workflow shows the information and checks required for that decision.
- Escalate: route unfamiliar exceptions, payment-detail changes and complex reconciliations to the agreed reviewer.
For example, an employee could draft a customer refund response on a phone while leaving the actual refund to the authorised approval process. Distinguish the communication from the underlying transaction.
Use a desktop handover record
| Field | Example entry |
|---|---|
| Record | Customer case identifier in the shared system |
| Completed on mobile | Customer acknowledged; supporting document uploaded |
| Pending task | Reconcile the document against the order |
| Owner and deadline | Named reviewer; agreed review time |
| Blocker | Mobile screen does not show the complete comparison |
The entries are illustrative. Use identifiers and links in your authorised system rather than copying sensitive customer details into an unrelated personal app.
Check synchronisation and close the loop
After a connection interruption, confirm that an action reached the server before retrying it. For orders, messages and uploads, look for the accepted record and timestamp. If the state is uncertain, check it from another authorised device or ask the system owner before producing a duplicate.
At the end of the work period, review pending drafts and handovers. Assign an owner to unresolved work and confirm that attachments are accessible to the intended team. Remove temporary local copies according to the organisation’s retention rules.
Prepare for a missing phone
Document how the owner can report a lost device, revoke its access and recover business accounts through the approved process. Keep recovery arrangements available without relying solely on the missing phone. Test that a replacement device can reach the essential systems.
CISA recommends multifactor authentication and timely software updates as basic protections. Combine them with your organisation’s device and data-handling procedures rather than assuming an app’s presence is sufficient.
If the routine exposes a recurring support gap, use the consultant brief checklist to define the fix. Related material is available in the Technology section.
