These original planning resources use synthetic examples. They contain no customer results or personal records. Confirm product behavior and acceptance criteria in your proposed deployment.
Separate capture from confirmation
Offline capability is not a single yes-or-no property. A device may save a survey record locally while payment initiation, provider confirmation or receipt verification still requires a connection. Ask the supplier to identify the boundary for each task.
This is an evaluation method, not a claim that every workflow is available offline in CountyERP. Confirm the device, application version and supported operations in your proposed deployment.
| Activity | Question to resolve | Evidence to request |
|---|---|---|
| Asset survey | Can the assigned fields be saved without a connection? | Local record with a visible pending-sync state |
| Payment initiation | Which service must be reachable? | Observed behavior when the request cannot be sent |
| Payment confirmation | What establishes a successful payment? | Provider confirmation distinguished from queued capture |
| Receipt verification | Is the result current or cached? | Timestamp and limitation of the displayed status |
| Reconciliation | Which checks occur after synchronization? | Server record, financial effect and unresolved items |
Run a controlled disconnection exercise
Use a synthetic officer account assigned to Area A, a test device and an illustrative asset DEMO-ASSET-001. Verify the assignment while connected, then disconnect the device and attempt only the operations agreed for the test.
Record what the officer sees at every stage: pending, confirmed, rejected or requiring review. A pending record should not look like proof of confirmed payment. Reconnect and follow the record into the back office.
| Step | Test | Expected observation to agree |
|---|---|---|
| 1 | Capture a record in the assigned area | Identifier and pending state remain visible |
| 2 | Attempt an external payment request offline | Clear unavailable or pending state; no false confirmation |
| 3 | Reconnect and submit the queue | Accepted records linked to their original local identifiers |
| 4 | Retry the same queued record | No duplicate financial effect |
| 5 | Change the server record before replay | Conflict visible for the agreed resolution process |
| 6 | Attempt an action outside Area A | Action denied or held under the agreed authorization policy |
Test stale permissions and device loss
An officer’s permissions can change while a device is disconnected. Ask how long cached access remains valid and what happens when the device reconnects after revocation. Do not assume that a locally stored token immediately reflects a new assignment.
Agree the procedure for a lost device, the protection of locally stored data, and the treatment of unsynchronized work. Document any limits rather than promising immediate remote control of a device with no connectivity.
Close the shift and record the limits
Compare locally captured work, accepted server records, rejected items and payment confirmations. Give each unresolved item an owner. A successful sync count alone does not establish that every payment has settled or every obligation has been cleared.
Repeat the exercise with the actual proposed device and connectivity conditions before acceptance. Record observed results, timestamps, version and limitations in the downloadable checklist. Do not turn a controlled demonstration into an uptime claim or a promise that offline operation has no constraints.
Worksheets and next steps
Open the CSV files in a spreadsheet application and adapt the blank fields to your evaluation. Preserve the synthetic labels when sharing example rows. No registration is required.
Prepared as CountyERP editorial guidance. The examples explain review methods and do not certify compliance, prove a live integration or replace an agreed implementation specification.
Use the evaluation workbook to record observations, evidence and unresolved questions.