Tracker 4 Managers

From SymbiantWiki

The managerial role within Tracker is a key and potentially very powerful role. Managers are generally responsible for users (auditees) who are in the same divisions, identified when adding the accounts. Managers are able to view all recommendations, actions and reports relating to issues within their division or that have been assigned to auditees within their division.

Managers can be granted permissions which allow them little more than view only rights to almost administrational privileges, including creating and archiving issues, responding and monitoring comments and managing user accounts (all within their division) etc.

Responsibilities

As a manager the main responsibility in Tracker is the same as in the workplace. The managing of users under them. “Users under them” in Tracker are those in the same division but given an Auditee role in accounts.

Assuming that the relevant permissions have been granted a normal managerial scenario in Tracker would include, issue actions being assigned to users within a managers division or to the manager themselves to be re-assigned as they see fit. The manager would accept responsibility for keeping tracks on the users progress, prompting them for action if the action status has not been updated, reviewing any status updates and ensuring that the actions are meeting the requirements of the recommendation.

Again, depending on the permissions granted to the manager they could even mark the action as implemented and change the status of the issue, implementing it in its entirety.

It is possible to introduce a normal work hierarchy within Tracker. Where by higher up managers can be given more responsibility. For example, one low down manager could be responsible for communicating with the users and ensuring the actions are done. A middle manager could be responsible for checking over what has been done and implementing the actions adding a final confirmation comment that they have checked and signed it off. A senior manager could then be responsible for changing the status on the issue and finally saying, “yes this issue has been implemented” (or not).

The point is, whatever the business structure Tracker can accommodate it with its hugely powerful account roles.