Test the technician’s job, not just the dashboard
Use the type of phone or tablet your team will carry and the role that a technician will receive. A desktop administrator demonstration can hide limitations that matter on the floor. Start with a representative asset and a routine work order, using non-sensitive test information.
Ask the technician to find the equipment, open the instructions, complete the required checks, record time and parts, attach a photo and close the job. Observe whether the interface makes required fields and unsaved changes clear. Note where the user needs help or must switch to another device.
Establish exactly what offline means
Offline capability should be evaluated as a set of tasks, not one yes-or-no feature. MaintainX’s documentation describes mobile offline work and synchronization when the connection returns. Its mobile and web experiences differ. Confirm the current plan, device, role and configuration that support your required use case.
Prepare the test while connected, then disconnect the device without interrupting real operations. Check which records and attachments are available. Record any preparation the technician must perform before entering a low-connectivity area. Do not assume that a work order visible yesterday will always be cached today.
Use a repeatable test sheet
For each test, keep the starting state, expected result, observed result and unresolved limitation. Use the same sample tasks across shortlisted products so differences are meaningful.
| Scenario | What to verify |
|---|---|
| Open an assigned job offline | The intended instructions and asset details are available. |
| Record work without a connection | Required fields can be completed and local save status is clear. |
| Attach a photo | The app explains whether the file is stored locally or uploaded. |
| Reconnect | Changes reach the server and another authorized user can see them. |
| Edit from two devices | The product explains how conflicting changes are handled. |
| Interrupt synchronization | The user can identify unfinished uploads and recover safely. |
Check devices, identity and shared use
Ask about supported operating systems, app updates, storage requirements and the effect of signing out. For shared devices, demonstrate the change between users and verify whose identity is attached to completed work. Do not share a personal login merely to make a demonstration pass.
Test readability, keyboard behaviour, camera permission handling and barcode scanning with realistic labels. Where your environment requires protective equipment or specialized devices, involve the people responsible for those requirements. A public marketing claim is not a suitability assessment for your specific working conditions.
Make synchronization visible in the acceptance decision
An on-device saved message is not enough to prove that a supervisor has received the work. Verify the server record after reconnecting and compare time, parts, notes and attachments with what the technician entered. Include a deliberate retry to see whether it creates duplicate records.
End with a list of supported tasks, limitations and required operating procedures. If offline work is essential and a critical task remains unproven, keep it open in the evaluation. A smooth demonstration under reliable Wi-Fi should not stand in for the field test.