BROWSER ADMINISTRATION · REVIEWED FOR UI 08
Manage checklist records
Keep delayed or unwanted work out of the active list without erasing evidence
Record, template and Task are different
A checklist type is a reusable published template. A standalone record is one job's checklist with its saved results. A Task-owned checklist belongs to its Task and is managed with it. Removing or retaining a record does not remove the template, and publishing another template revision does not rewrite existing records.
The browser checklist catalogue offers a collapsed Templates, retained records & work rules panel. Administrators can open Record management there; the main Administration route remains available. Template authoring is in Administration → Templates & routines.
Postpone work that will continue later
- Sign in as a current project administrator with the applicable access; do not use a restricted guest account.
- Open Administration → Record management, select checklist records, then choose the exact saved record.
- Review its current state and available actions. For unfinished work that is delayed, choose Postpone.
- Review the effect, enter the reason and exact record title requested by the form, and confirm. Opening the record or the confirmation form does not save anything.
The record leaves normal active selection without being marked completed. Saved answers, readings, evidence and history remain. It cannot accept new work or synchronisation while retained. This is not an automatic resume schedule.
Cancel, archive and restore deliberately
Cancel retains unfinished work that is no longer required. Archive retains a finalised record out of normal selection. Only actions permitted for the current record appear; fully finalised stages are not unlocked by these visibility changes.
Use the retained-record view in Record management, select the intended checklist and choose Restore when appropriate. Restoring retained unfinished work makes that same record available again and preserves its prior answers. Restoration refreshes its versions; previously queued device entries must be reviewed, not blindly replayed. Restoring an archived finalised checklist changes visibility, not finalisation.
Task postponement and reopening have different rules. Use General-purpose Tasks for the current Task workflow, not standalone checklist restoration as a substitute.
Protect unsent work and traceability
Tell the team before postponing or cancelling an active checklist. A disconnected phone cannot learn about the change until it reconnects. Preserve its unsent work. After restore, review conflicting queued entries; do not clear browser data to remove a warning.
Record management actions require the existing permission, saved-revision, reason, typed-name and confirmation checks. A concurrent change requires a fresh review. History and original evidence are retained; the browser does not offer unrestricted permanent deletion of every record.
See Manage unfinished and retained work for the shared management screen, and Complete a checklist for the working record. Hosted and vessel projects do not synchronise automatically.