Accountability officer workflow

Accountability Officers can provide status on behalf of other users during or after an accountability event, and can generate accountability event reports.

Accountability Officers can be designated to serve as reporters based on location, job function, or team membership. The Accountability Officer role can be added to any user with operator permissions, or as a standalone role.

System administrators should include Accountability Officer messages with appropriate targeting as part of their accountability templates. This enables administrators to quickly include Accountability Officers as part of their emergency accountability process. When creating a template, administrators can include an initial message, tailored to Accountability Officers, that informs them that an event has started and requests that the Accountability Officers begin accounting for their users. Administrators can also configure an Accountability Officer ending message, informing their Accountability Officers when an event has ended, or when all users that the Accountability Officer is responsible for have a reported status.

Out of the box accountability templates include standard response options for the Accountability Officer initial message. Accountability Officers can select from "I'm available to update user status" or "I'm not available to update user status."

When an event begins, the system administrator selects an accountability template with accountability officer messages already predefined in the system. During the publishing flow, the system administrator has the option to add additional Accountability Officers prior to publishing the accountability event.

Once the event is published, the Accountability Officer receives a notification that an accountability event has started. The notification can contain instructions for the Accountability Officer about how to report status on behalf of other affected users for the event. The notification also includes response options that the Accountability Officer can use to indicate their availability to update their users' statuses. Accountability Officers can select a response option using Self Service, mobile devices, email, or text messaging.

Notifications can be sent on any of the devices targeted when the event was published. Devices are system based and can include one or more of the following: email, phone, SMS, and mobile app. Email notifications can contain a link which takes the Accountability Officer to the login screen of the

BlackBerry AtHoc

management system. The severity of the notification email is the same as the severity set for the accountability event.

After logging in, the Accountability Officer is sent directly to the Users tab of the live accountability event for the specific organization or provider. The Users tab displays only the users with no reported status that the Accountability Officer is responsible for reporting status for. The Accountability Officer can then select a single user, or multiple affected users, and update status on their behalf.

Accountability Officers can view and export reports of the status of their users as the event progresses.

The Accountability Officer receives a notification in an email that the accountability event has ended. The notification contains a link which takes the Accountability Officer to the login screen of the

BlackBerry AtHoc

management system. After logging in, the Accountability Officers is sent directly to the Users tab of the live accountability event for the specific organization or provider. On the event dashboard, the Accountability Officer can view and export reports of their users after an event has ended.

These reports detail the time each user reported status, what the status was, and how many users reported their own status or had their status reported by an Accountability Officer.