Overview

Team performance snapshot
Idle

Team scoreboard

ranked by overall score · click a row to open the report
Loading…
How it works. Each stage runs the underlying script and streams its output to the console on the right. Run stages individually, or use Run full pipeline to chain them. Narrative analysis is authored separately by AI and is consumed by the “Build reports” stage — it is not re-run here.

Pipeline stages

pipeline · idle
No runs yet. Trigger a stage to see live output here.
AI analysis — edit before building reports
Generate or select an analysis to edit.
Generated reports
Preview
Select a report on the left to preview it here.

Save current reports as a snapshot

a full copy you can restore any time

Each snapshot keeps that run's HTML reports, PDFs, the evaluation workbook and the underlying data (metrics, AI analysis, attendance, period). A snapshot is also saved automatically before every pipeline run, so a failed or empty fetch can never make your reports disappear.

Saved snapshots

—

Company evaluation workbook

—

A department-aware, three-pillar measure (one sheet per active employee). Pick each employee's department below to load its craft criteria; auto-filled cells (blue) come from Jira / your time report / AI, craft & 360 are manager-entered. All totals are live Excel formulas. Bonus is separate (not in the score).

PillarWeightWhat it measures
Delivery & Execution30auto Working Time, Task Output, Deadlines (Jira) + Attendance (time report)
Department Craft45department-specific quality rubric — manager-entered
Collaboration & Growth25Manager / Peers / Self + Skill Dev / Ideas (AI)
Bonus (separate)—eligibility gate (Monthly ≥ 80) + achievement points → level

Grading scale

≥ 90Excellent ≥ 80Very Good ≥ 70Good ≥ 60Satisfactory < 60Unsatisfactory
Monthly Total = weighted blend: 75% Performance (Delivery + Department craft) + 25% Collaboration & Growth.

Fill / edit evaluation

Select an employee to fill in their evaluation.

Evaluation archive

—

Save the current evaluation — the filled scores, departments & bonus plus the generated workbook — as a named version you can restore any time. Independent of the report Archive.

Attendance vs Jira. For each employee per month, enter the Required hours and the actual present hours (from the fingerprint report) and optionally upload that month’s file. The files are attached to the employee’s report email; the present hours are compared with the hours they logged in Jira, and the AI analysis flags any mismatch (coverage = Jira logged ÷ actual present). Accepts .xlsx, .csv, .pdf or images.

Attendance by employee

one file per person

Recipients

each employee gets their own PDF report
email · idle
Send activity will appear here.

Team members

—

Roles & permissions

what each role can access
CapabilityAdminDept leadViewer
View reports & analysisAllOwn deptAll (read)
Fill / edit evaluation✓ all✓ own dept✕
Run the pipeline (fetch/build)✓✕✕
System settings & connections✓✕✕
Email reports · Archives✓✕✕
Manage users✓✕✕

Reporting period

controls every report; re-run the pipeline to apply
Resulting period
—
Used for the metrics window, the “expected hours” baselines, the report headers and the evaluation workbook. After saving, run Rebuild on the Pipeline page.

Email (SMTP)

used to send reports to employees —
The password is stored locally in .studio_smtp.json (owner-only) and never leaves this machine except to your SMTP server.

AI analysis

writes each report's analysis —
The key is stored locally in .studio_ai.json (owner-only) and is only sent to Anthropic when you run the analysis. Generate one at console.anthropic.com.

Jira connection

Environment

Data freshness

last modified time of each pipeline artifact