Skip to main content
Version: v2 (current)

Key Indicators

This section describes the main indicators displayed on the dashboard, helping you assess efficiency and work dynamics.

Activity Time​

Activity Time is the total work activity time recorded by the system. The indicator can display data for an entire team or for a specific engineer. This is a comprehensive metric that includes all types of work activity, not just coding.

What is tracked​

  • Coding — writing and editing code in the IDE (typing, navigation, refactoring).
  • Browsing — working with the browser: reading documentation, searching for solutions, studying resources.
  • Database — interacting with databases through built-in IDE tools or external clients.
  • Terminal — terminal activity: running commands, working with git, executing scripts.
  • AI — using AI assistants (Copilot, ChatGPT, Claude, etc.) for code generation or getting answers.

Idle time is automatically excluded — only active interaction with tools is counted.

Displayed data​

  • Format: Hours:Minutes (e.g., 181:09).
  • Trend: Percentage change compared to the previous period (e.g., ↓ 11.8%).
  • Breakdown: Below the main value, a detailed breakdown by activity category is shown with time for each.

Focus Time​

Focus Time measures the ability to concentrate on tasks without distractions. The higher the focus time percentage, the fewer task switches and external interruptions.

Concentration levels​

  • Focus — continuous work on a task without distractions for a certain period.
  • DeepFocus — even deeper concentration: long sessions without any switching. Shows the ability to immerse in complex tasks.

Displayed data​

  • Percentage: The share of focus time relative to total activity time (e.g., 65.5%).
  • Absolute Value: Focus time in hours and minutes (e.g., 118:42).
  • Trend: Dynamics compared to the previous period.
  • Breakdown: DeepFocus and Focus time shown separately for analyzing concentration depth.

Planning Accuracy​

Planning Accuracy shows the difference between time planned in the task tracker and actual time recorded from activity.

  • Coefficient:
    • 1.0 — Ideal planning.
    • < 1.0 — Underestimation (task took longer than planned).
    • > 1.0 — Overestimation (task was completed faster than planned).
  • Visual Scale: A bar showing the deviation from the ideal value.
  • Breakdown: Shows planned hours (Plan) vs actual hours spent (Fact).

Productivity​

Productivity shows how close an engineer is to the target pure coding activity time. The baseline target is 4 hours of pure coding per day.

  • Index: Percentage value relative to the target 4 hours (e.g., 132.1% means the engineer exceeded the target).
  • Graph: A sparkline graph showing the dynamics over the selected period.
  • Trend: Change compared to the previous period (e.g., ↑ 5.4%).
  • Productivity Time: Actual productive time in hours.