OfficerFlow: historical user guide

Roles described in the original guide

• Administrators managed users, officers, locations, tasks, events and review records.
• Officers assigned work, monitored schedules and reviewed submissions.
• Staff viewed assigned tasks, supplied progress and attachments, and responded to rework instructions.

The task and review workflow

• Create a task with a title, description, priority, owner, assigned staff and due date.
• Connect the task to its relevant event or location where appropriate.
• Submit a progress update with a description, percentage and supporting attachment.
• An authorised reviewer approves, notes or returns the submission for rework.
• Track the task through pending, in progress, review, rework, on hold and completion states.

Planning and repeated work

The historical dashboard summarised pending, overdue and reviewed work. Review Inbox brought submissions and rework together. Schedule Board displayed events, task due dates and possible conflicts. Templates provided a starting point for repeated tasks.

Attachments, reminders and reporting

The guide described attachments on tasks, events and progress updates; in-app reminders; task, event and officer exports; and printable reports. Email notifications depended on a configured sending service and valid recipient details. These are descriptions of the captured version, not a test of a current installation.

Read with the current product scope

The original guide distinguished workflow assistance from statutory reporting, signed paper records and legal or financial registers. Current access, organisation setup and functionality belong to the maintained OfficerFlow product. This archive does not provide access to task records, account administration or internal listings.