Project Assessments

Evaluate client accounts and delivery quality with management and technical frameworks, Overview analytics, and TRACK cross-links.

Project Assessments help delivery and account teams evaluate client accounts and projects using structured frameworks — not individual people.

ModuleWhat it evaluates
Performance assessmentsPeople (self, manager, peer, 360) — optional project scope for context
Project assessmentsDelivery units / accounts (management & technical quality)

These are separate workflows. A project-scoped performance assessment evaluates a person in the context of a project. A project assessment run evaluates the account/project health (MU/TU frameworks). On Manager → Projects → [project], both panels may appear side by side for visibility — they do not share a lifecycle or schema link.

Where to find it

  1. Open the Delivery workspace (if you have delivery permissions).
  2. In the sidebar under Account management, go to Project Assessments.

You can also start from Manager → Accounts, open a client, Delivery tab → Project Assessments. Creating a run from an account pre-fills that client.

Overview tab: Your organization must have Project Assessments Overview enabled in admin settings. If you only see Runs, ask an admin to turn on the Overview feature for your tenant.

Assessment types

  1. Management Unit (MU) — Delivery process, planning, governance, stakeholder communication.
  2. Technical Unit (TU) — Engineering quality, security posture, reliability, technical readiness.

Each run uses one framework type and moves through workflow stages (draft → submit → calibrate → publish, depending on your role).

Overview dashboard

When Overview is enabled, you get two tabs: Overview and Runs.

Overview tab

Use Overview for tenant-wide trends (all runs you can access):

  • KPI row — Total runs, average score, lead time, status breakdown.
  • Timeline — Runs per week, stacked by status.
  • Comparisons — Scores grouped by client, project, framework type, or coverage dimension.
  • Distribution — Heatmap and scatter of normalized scores.
  • Observability — Data-quality issues (missing evidence, incomplete scores, stale drafts).
  • Filters — Date range, framework type, status, coverage group, TRACK status (with/without TRACK data). Filters sync to the URL so you can share a view.

Runs tab

  • Start new runs (MU or TU).
  • Open recent runs, continue scoring, attach evidence, and advance workflow.

Typical run workflow

  1. Create a draft run (MU or TU).
  2. Open the run from Recent runs.
  3. Score indicators and add notes.
  4. Update title, period, client, and project as needed.
  5. Attach evidence (links, notes).
  6. Move through statuses (submit / calibrate / publish) when your role allows.

When a run’s client also has TRACK data (goals, routes, plays):

  • On the run detail page, see Related TRACK entities with counts and links to the account TRACK view.
  • From TRACK, open linked assessments with a back breadcrumb.
  • On Overview, filter by TRACK status (all / with TRACK / without TRACK).

See also TRACK: Account Strategy.

What you can do (by role)

ActionWho typically can
View runs and OverviewDelivery leads, account owners, admins with assessment access
Create and edit draftsSame, plus assigned contributors
Submit / calibrate / publishLeads and admins per your org policy
Configure frameworksAdmins (see Assessment frameworks)

If a menu item is missing, your admin can adjust roles in Roles & permissions.