Target Score Report
Route: /dashboard/bsc-target
Audience: Employees (self) and managers (one employee at a time)
The Target Score Report answers: What do I need on each KPI to reach my next remark?
It complements the other BSC dashboards:
| Page | Time lens | Question |
|---|---|---|
| Balanced Scorecard | One month | What happened this month? |
| Target Score — Month | One month | What do I need this month on each KPI? |
| Target Score — Cycle | Full fiscal cycle (planning) | What do I need in remaining months to finish the cycle at a remark? |
| Bonus qualification | One month | Who is bonus-ready, and which gate failed? |
| Monthly performance | Full cycle (history) | How did scores move through the cycle? |
Controls
- Month | Cycle — Toggle next to the page title. Default is Month (existing bookmarks without
lensstay on Month). - Scope — One employee at a time. Filters match Balanced Scorecard: employee, cluster, department, and site when applicable.
- Month scope — Month picker in the float panel (same as Balanced Scorecard month).
- Cycle scope — BSC cycle picker in the float panel (same cycles as Monthly performance).
- URL state —
lens=month&year=&month=orlens=cycle&cycle_id=plus scope params.
Month scope
Plans for the selected calendar month:
- Current Total BSC and remark band
- Target remark (Goal / Expectation / Standard) — defaults to the next band above current
- Gap to target and per-KPI required scores
- Improvement table with scorecard action hints
- What-if sliders and multi-KPI path when one KPI cannot close the gap alone
API: Month snapshot + employee KPI breakdowns (same as Balanced Scorecard).
Cycle scope
Plans for the rest of the fiscal cycle (Jul–Jun):
Running Score
Average Total BSC from cycle start through last completed month (not including the current calendar month).
Example: In June 2026, Running Score = average of Jul 2025 … May 2026.
Remaining months
The banner shows the monthly Total BSC needed in each remaining month (uniform assumption) to finish the cycle at the selected target remark.
Example: “Aim for 92.4% in June 2026” when only June remains.
Unreachable targets
Monthly scores cannot exceed 100%. If the math requires more (e.g. 287% in one month), the page shows:
- The target remark is not reachable in the time left
- Best possible cycle finish if every remaining month is 100%
- Nearest achievable — highest Goal / Expectation / Standard still possible, with a Use X as target action
KPI table (Cycle)
| Column | Meaning |
|---|---|
| Running avg | Mean KPI score over completed months in the running window |
| Needed | KPI score required in each remaining month (from lever math) |
| Plan [month] | Opens Month scope for that KPI’s weakest month in the running window |
Other sections
- Timeline strip — 12 cycle months; past scores vs future planning window
- What-if — Hypothetical KPI scores in remaining months → projected cycle average
- Data health — Warns when some completed months lack scorecard data in the running window
API: GET /v1/dashboard/bsc/performance?cycle_id= + configurations for the cycle. No separate cycle-target endpoint in v1.
Links from other dashboards
When exactly one employee is in scope:
- Balanced Scorecard — “Cycle target score report” link (active BSC cycle for the selected month)
- Monthly performance — Same link for the selected cycle
Both open Target Score with lens=cycle and the shared employee filter.
Related
- Total score goals — band thresholds
- Fiscal cycles — cycle boundaries
- Dashboard overview — how all five pages relate
- Bonus qualification — manager gate matrix for one month
