What is Current Score? Project health, factor by factor

Current Score is a 0–100 health number for a project. It starts at 100 and subtracts points for six specific problems it can see in your data — overdue tasks, unassigned work, unscheduled tasks, open PSA sync conflicts, budget burn, and a project that is past its own due date. Nothing else moves it.

It is not AI, and it is not a black box. The score is a fixed arithmetic formula recomputed every time the page loads, and every point it took away is itemized. Click the score chip anywhere in Current and you get a "Why this score" list: each factor, its plain-English detail ("3 open task(s) past their due date"), and the exact points it cost.

The band is derived purely from the number. A project sitting at 79 is "At risk" by one point — meaning one fixable item stands between you and green.

Each factor has a per-item cost and a ceiling, so no single problem can sink the whole score on its own. "Open" always means a task that is not yet done.

Worked example. A project with 3 overdue tasks (−24), 2 unassigned tasks (−6), and 1 unresolved sync conflict (−5) scores 100 − 35 = 65, which lands it in the At risk band. Fix the three overdue dates and the score jumps to 89 — On track — on the next page load.

• ＋Project page — the Current Score tile in the summary panel at the top, showing the band word and the number ("At risk · 65"). Click it for the breakdown.
• ＋Project page — a trend sparkline under the tile, drawn from the nightly snapshots. It appears once there are at least two snapshots and shows the change since the first one.
• ＋Portfolio — a score chip on every project card and row. The default sort is worst score first, so the projects that need attention rise to the top, and the portfolio health gauge is the average score across active projects.
• ＋Reports — the Overview lens shows an "Avg Current Score" tile and a "Needs attention" list of the lowest-scoring projects. The Reports CSV export includes a Current Score column.

Below the summary panel on any project, project managers and admins get the Project Debugger — "Every Current Score deduction, with its fix". It lists the same factors as the popover, worst first, and puts an action button on the factors it can fix (Analyze schedule, Assign owners, Review conflicts, View budget). Project past due carries guidance text instead of a button.

1. 1
   Open the project and scroll to the Project Debugger

   Portfolio → open the project, or pick it from Recent projects in the sidebar. The panel sits just under the summary tiles. If the score is a clean 100 it says "Nothing to fix — full marks."
2. 2
   Work the top row first

   Factors are ordered by how many points they cost, so the top row is always the biggest win available.
3. 3
   Overdue or unscheduled tasks → Analyze schedule, then Recast

   Click Analyze schedule to run the analysis (it reads the full dependency graph, so it runs on demand rather than slowing the page down). It recomputes this project's dates from its dependencies against the working calendar (weekends, holidays, and PTO skipped). If dates should move, the button becomes Recast schedule — it previews every task that will move old date → new date and only writes after you confirm. PSA-linked tasks are pushed back to your PSA after saving; Current-native tasks save in Current only. If the dates already match the dependency schedule, the row says so and nothing is written.
4. 4
   Unassigned work → Assign owners

   Expands the list of ownerless open tasks, with chips showing who has free hours this week. Click a task to open its drawer and pick an assignee.
5. 5
   PSA sync conflicts → Review conflicts

   Jumps to the Sync Health page to resolve them. See "Fix a sync conflict between Current and your PSA".
6. 6
   Budget burn → View budget

   Scrolls to the budget panel. Project past due has no button — adjust the project due date, or complete the project and run its close-out.

The score itself is always live — it is recomputed from current data every time you load a page. What runs on a schedule is the health monitor, daily at 06:00 UTC. It takes a snapshot of each project's score (at most one per project per 12 hours — that snapshot series is what draws the trend sparkline) and alerts the project lead when something turns.

Project managers and admins can also run it on demand with the Health check button in the project header. Health check re-runs the monitor now instead of waiting for 06:00 UTC. It writes a snapshot only if the project has none from the last 12 hours, and it sends only alerts that are not already recent duplicates (an at-risk or score-drop alert is suppressed for 20 hours, a due-soon or over-budget alert for 6 days). It reports how many alerts went out — often zero.

• ＋A project that has never synced to a PSA has no sync conflicts, so that factor sits at zero. The formula does not check sync_mode, though — if a project is switched to Current-native (for example, restored after its PSA project was deleted) any still-unresolved conflicts from its synced era keep costing points until they are resolved on the Sync Health page. See "Project modes: PSA-synced or Current-native".
• ＋A task counts as assigned if it has either a Current assignee or a PSA assignee name — a synced task owned in your PSA does not cost you unassigned points.
• ＋If a project has no budget percentage recorded, budget burn deducts nothing. The percentage comes from the PSA side of a synced project.
• ＋A factor with a zero deduction is not listed at all — the breakdown only shows what actually cost you points.
• ＋Partner viewers and account executives never see Current Score. The score exposes budget burn and internal task counts, so the data layer returns nothing for those roles — the partner portal shows status, progress, and dates only. See "The partner financial firewall".