Contract Portfolio Dashboard Metrics Guide

Definitions

Practical workflow

1. Set the portfolio population

   Document which agreement types, entities, counterparties, categories, amendments, statements of work, renewals, and terminated or superseded records are included or excluded from each metric.

2. Publish metric definitions

   Write the numerator, denominator, date basis, status precedence, currency and value treatment, time-zone rule, refresh timestamp, source fields, and treatment of unknown or duplicate records for every dashboard tile.

3. Validate agreement status and dates

   Reconcile effective, expiry, termination, notice, and renewal dates against executed documents and related records before classifying agreements as active, expiring, auto-renewing, expired, or unknown.

4. Track obligations and approvals

   Separate obligations due, completed, overdue, waived, canceled, not applicable, and unknown; report approval requests by pending, approved, rejected, returned, canceled, and incomplete states with owner and aging context.

5. Normalize value and risk data

   Label each amount by value type, period, currency, source, and confidence. Apply the same risk and deviation taxonomy, then show count-based and value-weighted distributions separately.

6. Measure cycle and queue time

   Capture workflow event timestamps and distinguish active work from waiting. Report medians, percentiles, counts, and missing-event rates by comparable cohort rather than presenting a single average as a universal baseline.

7. Segment and reconcile the dashboard

   Allow filtering by entity, counterparty, category, owner, business unit, jurisdiction, agreement type, risk tier, and data-quality status. Reconcile segment subtotals to the declared population and explain intentional overlaps.

8. Add drill-through and review routines

   Link each metric to its source agreements, obligations, tasks, approvals, evidence, and exceptions. Assign owners to investigate stale records, unexplained changes, missing data, and threshold breaches on a defined cadence.

Comparison

Limitations and exceptions

• A dashboard cannot repair incomplete, duplicated, stale, or incorrectly interpreted contract data; data-quality exceptions should be reported beside the metric.
• Value exposure is not a single universal financial concept. Different value fields answer different questions and should not be summed without an explicit business rule.
• Risk tiers and deviations depend on the selected taxonomy, baseline, reviewer judgment, and available evidence; a label does not establish legal or commercial loss.
• Cycle and queue times are not comparable when event definitions, pauses, business hours, populations, or timestamp completeness differ.
• Counts can overlap when agreements have multiple entities, counterparties, categories, owners, risks, or obligations, so segment totals may not add to the portfolio total.
• A current status can become stale when source systems, documents, renewals, notices, approvals, or obligation outcomes are not reconciled on schedule.
• External frameworks can inform governance and measurement design, but they do not supply a universal contract portfolio benchmark or guarantee a dashboard outcome.

Primary sources

Methodology

Design the dashboard from decisions and source records rather than from available chart types. Formula: active_agreement_count = count of distinct eligible agreement IDs whose governed lifecycle status is active at the snapshot date; renewal_due_rate = eligible active agreements with a valid renewal or notice deadline inside the reporting horizon / eligible active agreements with a known current term and applicable renewal rule; obligation_on_time_rate = eligible obligations completed, evidenced, and recorded by the due date / eligible obligations due in the reporting period; approval_target_attainment = eligible completed approval cases meeting the segment target / eligible completed approval cases; value_exposure_s = sum of eligible agreement values in original currency s for the declared population; required_field_completeness = populated and valid required field instances / required field instances expected for eligible records. Inputs: snapshot or reporting period, agreement and obligation IDs, lifecycle and decision statuses, effective, expiry, notice, renewal, and due dates, approval timestamps, segment target, value, currency, required-field rules, source and review status, duplicate keys, and data-quality flags. Eligible population: the declared agreement, obligation, approval, or field population for the tile after applying the tile-specific status, date, entity, and relationship rules. Exclusions: drafts, duplicates, superseded or terminated records when the tile is current-state, canceled or waived obligations, not-applicable items, invalid or missing dates, unknown statuses, unknown currencies, and records outside the declared scope; keep excluded and unknown counts visible and never silently place them in the denominator. Output and unit: counts are records or distinct IDs, rates are percentages from 0 to 100, time tiles are declared calendar or business seconds, hours, or days, completeness is a percentage, and value exposure is an amount reported separately for each original currency. Interpretation: each tile is a decision signal for its declared population and snapshot, not a universal benchmark; show the denominator, source freshness, data-quality gap, and drill-through evidence beside the value. Reconcile segment subtotals to the declared population, preserve count-based and value-weighted risk views separately, and never convert external framework guidance into an invented benchmark or guaranteed result.

FAQs

Related CaseDocker capabilities

Related guides and resources

• Contract management
• Playbooks
• Document eSigner and execution
• Compliance management