DeskGate reporting help

User Statistics Summary

Interpret a user summary before comparing people or distributing results.

Current report example

Actual Management Summary comparison interface.
Actual Management Summary comparison interface. Open for original size. Example records are demonstration data.
1

Top: match two periods

Select Week A, Week B, Group and Users. Verify comparable week coverage and the same population before interpreting a change.

2

Summary: separate observation from cause

A change in active interaction or recorded events is an observation. Check classification and collection coverage before proposing an explanation.

3

Comparison rows: inspect the baseline

Follow the user-level comparison. An empty previous period is an unavailable baseline, not proof of an improvement.

Start with a bounded question

Choose the people, period and recorded activity you need to review. A user summary describes the data available to that report; it is not a complete record of attendance, work quality or duties away from the computer.

Check scope before comparing totals

For the current Management Summary workflow shown below, compare Week A and Week B with consistent group and user selections. Check incomplete periods and collection coverage. Use the underlying report when a summary needs explanation.

Keep the result traceable

Record the two periods, filters and observation. Check the available PDF export against the displayed scope. Avoid turning a missing baseline into a percentage improvement or treating activity time as a performance rating.