Klarum

Dashboard and Items Cockpit

Generally available
Supplier and issuer
From free

The command centre at the top of the authenticated app: a dashboard that triages what needs attention today, a cross-workspace items tracker, and a proposals queue every new item has to pass through.

Catalogue id
dashboard-items

Description

What it is

A three-surface "command centre" at the top of the authenticated app: a firm-wide Dashboard that triages what needs attention today, a cross-workspace Timeline that shows work in time and is where items are authored and closed, and a Proposals review surface where pre-creation drafts (AI-extracted tender requirements, template/catalogue picks, agent suggestions) are accepted or dismissed before becoming real items.

  • Dashboard: a scrollable column of self-hiding widgets ordered by urgency - Action Center (overdue / due-today / due-within-7d workspaces, each with a "Run with Agent" CTA), Latent Capabilities card, Profile completeness bar, Scoreboard (open / submitted-30d / win-rate), Quick Actions, Deadlines + Recent activity, and a Featured matches strip (top-3 ML-ranked tenders since last visit).
  • Timeline: one row per stage of the selected axis, workspaces plotted across their dates, and each workspace's checklist authored and completed in place. Items are work units (TODOs, deliverables, submission requirements), standalone or workspace-attached. The separate two-pane cockpit was removed in #2376: it answered "what work exists" while the canvas answered "when is it due", and keeping both meant two places to mark the same item done.
  • Proposals: a review queue of item_proposals (drafts before any item exists), each with an origin badge ("From tender" / "From catalogue" / "From template" / "Manual") and accept/dismiss.

What it helps users do

See in one glance what is on fire (Action Center + Deadlines collapse "which of my 40 workspaces needs me today" into a ranked, calendar-day-accurate list); track all work across every bid in one place; never lose a tender obligation ("Extract from tender" turns the buyer's stated requirements into trackable items); decide before committing (everything that creates work funnels through Proposals first); act on hidden strengths (declare a latent capability in one click, lifting future match scores); and measure outcomes (win-rate overall + by country + by donor).

Capabilities

  • Action Center

    Generally available

    Overdue, due-today and due-within-seven-days workspaces bucketed by calendar day in UTC, each with a Run with Agent hand-off.

  • Self-hiding widgets

    Generally available

    Each dashboard widget disappears when it has no signal, so the page stays calm when the org is calm rather than showing a wall of empty states.

  • Latent capabilities

    Generally available

    A deterministic SQL traversal of the org's capability edges minus what it already declares, banded by rank, with a one-click Declare that lifts future match scores.

  • Proposals-first architecture

    Generally available

    Nothing writes directly to items. All four creation origins stage a proposal first, through one idempotent dedupe gate and one review surface, and items exist only on promotion.

  • The item model

    Generally available

    Typed content slots, directed inter-item links, sub-items, labels and a per-item activity log, with an assessed flag that is a human-judgement marker distinct from completion.

  • Process state buckets

    Generally available

    Per-org process states map onto canonical buckets so filtering by "open" works across every org's custom state names.

Keywords

dashboard, items, proposals, action-center, latent-capabilities, scoreboard

Provenance

This page renders a published artifact. Read the same records as JSON if you would rather check the source than the page.