Powered by Temper

User Incident Activity Report

STOP: Is the Incident module enabled for your organization?


This Report gives you the details of your team's activity. You can see who is contributing a lot and who could be more engaged.



Working with the Report

  • Only information about items people have authored is included by default, but selecting or deselecting "Author," "Responsible," "Assigner," and/or "Collaborator" will add or remove the relevant data from the Report.

  • The date range options are listed along the top of the page. Choose between 1 week, 1 month, 3 months, 6 months, 9 months, 12 months, all time, or a custom range by clicking on the corresponding option.

  • Beneath the date ranges are three additional options:

    • Click "All" to include all Incidents that meet the rest of the filter requirements.

    • Click "Project-Based" to include only Incidents that meet the rest of the requirements and are nested under a Project.

    • Click "Stand-Alone" to include only Incidents that meet the rest of the requirements and are not nested under a Project.

  • The Network diagram can be found along the left side of the page. Use this to filter the Report by Location - only items tied to the selected Locations will be included in the Report.

You can also:

  • Click any of the data points or status bars on this Report to open the list of Incidents it is counting. If you don't have the adequate permissions to view them, some items will be excluded from the list.

  • Export the Report to an Excel spreadsheet by clicking 2018-04-25_1238.png near the bottom left corner of the page. 


Things to look out for:

  • People who submit lots of Incidents which result in no change. They might need coaching on what continuous improvement is and how to come up with implementable ideas.

  • People who submit lots of Incidents that result in changes - give these employees a shout out!

  • Leaders in locations with low change rates are having a hard time finding ways to implement some aspect of an Incident. Try to understand why implementation rates are so low.

Bottleneck Alert:
Leaders responsible for lots of Incidents aren’t delegating work properly; they may get overwhelmed, and improvement will peter out.


  • Make sure leaders are encouraged to delegate work.


Have more questions? Submit a request