SPACE scoring

SPACE scores appear in monitoring sidebars, person detail charts, and reports when scoring is enabled for your organization. Scores run on a rolling window (typically the last 30 days) and refresh on a schedule after new events land.

See the SPACE scoring feature page for visuals and role-weight examples.

• S — Satisfaction — well-being proxies from sustainable pace, break patterns, and related signals. Human workers only.
• P — Performance — delivery outcomes relative to role expectations (merged work, completed issues, etc.).
• A — Activity — breadth and consistency of contribution across enabled statistics.
• C — Communication — collaboration cadence (metadata-only Slack signals when connected).
• E — Efficiency — throughput relative to active time and context switches.

Each dimension is scored 0–10 with underlying metrics listed in the confidence popover. Disable dimensions org-wide under Organization → Scoring if a dimension is not meaningful for your culture.

Every dimension ships with a confidence band: high, medium, low, or insufficient. Confidence reflects data coverage — how many days had signal, which integrations contributed, and whether peer baselines exist.

Team averages aggregate only scored workers and downgrade when too few dimensions have usable data. Never treat an insufficient score as zero performance.

Each worker carries a role profile (Developer, Designer, Manager, Product Manager, Data Analyst, DevOps, etc.) that sets default dimension weights. A designer legitimately weights Communication differently from a DevOps engineer.

Organization → Scoring lets admins tune benchmarks and optionally override role weight tables. Weights change how dimensions blend into the displayed overall score for that role — they do not create a cross-role league table.

Workers tagged AI agent use the AI Agent role weight profile and skip Satisfaction entirely — well-being dimensions do not apply to non-human actors.

Agents still score on Performance, Activity, Communication, and Efficiency where statistics exist (e.g. commits from a coding agent). They appear on the same monitoring timeline and reports human/AI split as humans.

AI agents require a Pro (or Enterprise) plan once the feature is enabled for your org. Hobby stays human-only on the public price sheet.

Configure scoring under Organization → Scoring:

• Master toggle to enable or pause org-wide scoring.
• Per-dimension enable/disable.
• Benchmark targets per dimension.
• Optional alert threshold when overall score drops below a line.

Statistics must be enabled for scoring under Organization → Statistics to feed a dimension. Dashboard-only statistics affect tiles but not SPACE math.

• “Overall score ranks the team.” WePeople deliberately avoids stack ranks and composite “top performer” badges. Sort by score in monitoring is a convenience, not HR instrumentation.
• “Low Satisfaction means unhappy.” It reflects signal sparsity or pace patterns in metadata — not a survey. Pair with conversation, not labels.
• “Agents should have Satisfaction.” The composer skips that dimension for AI_AGENT workers by design.