📋 Relationship Dashboard

Spec map

Home: All V2 Specs · Foundation: Data System (UVP) Mode(s): Relationship Mode Related specs: A2P, Contacts, Data System (UVP), Email Engine, Tribes

🎯 Goals

Purpose & Strategic Frame

Serve as the daily-driver insight surface that tells users what is changing, what to do, and how prepared they are. Core Architectural Principles
Govern the dashboard as an insight-driven, action-oriented, mode-aware control surface with persistent AI and visible data flywheel. The Five-Tab Architecture
Organize the dashboard into five tabs that form a complete observe-understand-act-analyze-plan loop. Tab 1: Pulse
Show daily momentum, what is moving, and what to act on today, reorienting to voter contact in Campaign Mode. Tab 2: Network
Present the network as an owned asset with size, verification, completeness, sources, and growth, overlaid on the universe in Campaign Mode. Tab 3: Relationships
Surface named individuals to act on today through AI-curated ranked queues with one-click actions. Tab 4: Demographics
Reveal network composition and gaps, summarizing demographic intelligence and handing off deep analysis to Battleground. Tab 5: Opportunities
Turn data into ranked, actionable AI recommendations and a readiness/activation score that drives Next Moves. The AI Layer
Weave a persistent, attributed, confidence-aware AI presence through every tab via the Insight Bar, annotations, and Strategic Analyst. The Mode Shift
Reorient the same five tabs between Relationship and Campaign Mode while preserving data continuity across modes. Influencer vs. Campaign Adaptation
Flex labels, emphasis, and AI tone by account type over an identical data model. Integration with Other VRM Systems
Act as the surface layer over UVPs, Next Moves, polling, field activity, petitions, donations, and future social data. Data Sources and Refresh Logic
Feed the dashboard from defined sources on a predictable, mostly-daily refresh cadence with on-demand recompute. UI Surface Conventions
Establish consistent, accessible, action-oriented presentation conventions across the dashboard. Tier Gating, Permissions, and Monetization
Keep the dashboard uniform in MVP while honoring role permissions and deferring tier gating to the account layer.

Status: Conceptual draft for review Author: Ben Edtl with Claude Date: May 14, 2026 Scope: The main dashboard experience for Politogy VRM Relationship Mode, including its transformation when Campaign Mode activates.

1. Purpose & Strategic Frame

The Relationship Mode dashboard is the daily-driver surface of VRM. It is the first thing a customer sees when they open the application and the screen they return to throughout the day. Its job is not to report on what happened — it is to tell the user what is changing, what they should do about it, and how prepared they are for the moment ahead.

Relationship Mode exists to do two things across the political cycle:

Off-season: Build the network of support — recruit, deepen, retain, and verify.
Campaign season: Mobilize that network into action — volunteers, donors, hosts, persuasion contacts, GOTV.

The dashboard must serve both jobs, and it must shift its orientation when Campaign Mode activates. The same data and the same five tabs persist across modes; what changes is what is emphasized, what is overlaid, and what the AI recommends.

A previous tabbed structure (Engagement / Reach / Demographics) reported metrics. This spec replaces that structure with an insight-driven, AI-augmented operational control surface organized around the questions a candidate or influencer actually wakes up asking:

Is my network growing or shrinking, and why?
Who is heating up and who is cooling off?
What should I do today that I am not doing?
Where am I weak — geographically, demographically, message-wise?
What is working that I should double down on?

The dashboard answers those questions on every screen. AI is not a separate destination; it is woven through every tab as a persistent insight layer.

2. Core Architectural Principles

These principles govern every design decision in this spec.

1. Insight over reporting. Every metric on the dashboard is paired with context (trend, baseline, comparison, AI annotation). A number with no narrative is removed.

2. Action over observation. Every actionable surface — an opportunity, a person, a segment, an insight — has a one-click conversion to a Next Move with a contract. The dashboard is not a destination; it is the launch point for work.

3. The dashboard is mode-aware. Relationship Mode and Campaign Mode are not separate dashboards. They are different orientations of the same five tabs. The user always knows which mode they are operating in via a persistent mode indicator in the dashboard header.

4. AI is a persistent layer, not a tab. AI insights appear at the top of every tab (Insight Bar), inline on individual metrics (annotations), and on demand via the Strategic Analyst chat affordance. The user is never asked to “go check what the AI thinks.”

5. VRM Verified is a first-class dashboard citizen. The match rate, enrichment depth, and data flywheel momentum are visible on the dashboard. This reinforces the core value proposition on every login and gives the user an obvious lever to pull (improve match rate → unlock more capability).

6. Aggregate Intelligence is visible and attributed. When the AI surfaces a cross-account insight (“accounts similar to yours saw X work well”), it is shown with attribution (e.g., “based on 47 similar accounts”). Attribution builds trust and reinforces the data moat. Tier-gating may be applied later; in MVP, expose it.

7. Adapt to context (campaign vs. influencer). The data model is identical; the labels, emphasis, and AI tone flex by account type. A campaign sees “voter universe”; an influencer sees “audience.” The five tabs do not change.

8. Forward-design for downstream features. This spec anticipates the social media management feature, the donation portal, and the WinRed/Anedot integrations. The dashboard reserves real estate and data slots for those feeds so they plug in without redesign.

3. The Five-Tab Architecture

The dashboard is organized into five tabs:

#	Tab	Question Answered	Primary Audience Activity
1	Pulse	What is happening right now?	Daily check-in, anomaly response
2	Network	What do I have?	Asset assessment, growth tracking
3	Relationships	Who needs my attention?	Individual-level action
4	Demographics	What is my network shape?	Composition analysis, gap awareness
5	Opportunities	What should I do next?	Strategic planning

Each tab serves a distinct cognitive task. Together they form a complete loop: observe (Pulse) → understand the asset (Network) → act on individuals (Relationships) → analyze composition (Demographics) → plan strategy (Opportunities) → return to Pulse the next day.

4. Tab 1: Pulse

Purpose. The “open the app in the morning” view. Daily momentum, what is moving, what to act on today.

4.1 Relationship Mode Orientation

The Pulse tab in Relationship Mode shows:

Network Momentum Strip. Five high-level numbers across the top, each with a 7/30/90-day trend sparkline: total network size, verified contacts, super-supporters, recent additions, weekly engagement rate.
Heating Up / Cooling Off. Two parallel lists of named individuals. Heating Up = engagement velocity rising, ready for next touch or ask. Cooling Off = touched-too-long-ago or engagement velocity falling, at risk of churn. Each entry is one-click → Next Move.
Today’s Anomalies. AI-flagged unusual events: a demographic cohort dropped engagement sharply, a geographic cluster went quiet, a content type spiked. Each anomaly explains itself in one sentence and offers an action.
Content & Engagement Pulse. Recent content performance, recent inbound responses, sentiment direction. Once the social media feature ships, this surface absorbs cross-platform reach and post-level engagement.
Donation Pulse (when donation data is connected). Weekly giving total, donor count, average gift, trend direction. Source-agnostic — surfaces data from the Politogy donation portal, WinRed, Anedot, or manual imports uniformly.

4.2 Campaign Mode Orientation

When Campaign Mode is active, Pulse reorients:

Voter Contact Velocity replaces general network momentum: doors per day, calls per day, IDs collected, persuasion conversations.
Universe Coverage replaces network size: percent of target universe contacted, percent IDed, persuadable pool remaining.
New Opt-Ins from Campaign Activity. People who entered the network via campaign-mode touches (door knocks, calls, petitions, events). These are the highest-quality recruits — already engaged at real cost.
GOTV Readiness Score appears as election day approaches: composite of contactability, identified support, ballot return rate, persuadable conversion.
Volunteer / Donor / Host Recruitment Pipelines. Three parallel pipelines surfaced as primary metrics, each one-click → Next Move.

4.3 Refresh Cadence

Pulse refreshes daily with on-demand recompute available. Daily cadence gives the AI a stable window for trend detection and anomaly scoring; on-demand recompute lets the user force a refresh after a known event (a campaign launch, a media hit, a content drop).

5. Tab 2: Network

Purpose. The asset view. What do I have, where did it come from, how strong is it, and how is it growing?

5.1 Relationship Mode Orientation

The Network tab shows the user’s network of support as an asset they own and grow:

Network Size & Growth. Total contacts, growth rate, growth source breakdown (organic opt-in, event, referral, content, paid). Trend over selectable horizon.
VRM Verified Match Rate. The percent of contacts matched to a UVP via the voter roll. This is the data flywheel exposed. Sub-metrics: total verified, total unverified, top reasons for non-match, suggested actions to improve match rate.
UVP Completeness. For verified contacts, the average completeness of the UVP across the nine data layers. Surfaces enrichment gaps that the user could action (e.g., “23% of your verified contacts are missing phone numbers — request enrichment”).
Source Attribution. Where contacts came from. This becomes the input to the Opportunities tab’s “what’s working” analysis.
Geographic Footprint. A map view showing network density. Heatmap by precinct, county, or district depending on account scope.
Data Flywheel Momentum. A composite metric showing how the network is becoming more valuable over time: verified contacts × UVP completeness × interaction recency. The AI explains what is driving the trend.

5.2 Campaign Mode Orientation

In Campaign Mode, the Network tab adds a universe overlay:

Voter Universe Coverage. The total target universe, what percent of it is in the network, and what the gap looks like.
Contactability. Percent of universe with verified phone, email, address, or in-person path.
ID Progress. Percent of universe with a confirmed support/oppose/undecided classification.
Network as Subset of Universe. A clear visual representation of “your network” inside “the universe you’re trying to reach” — the gap is the campaign job.

5.3 Influencer Adaptation

For influencer accounts, “voter universe” becomes “audience” and “contactability” becomes “reach surface” (which platforms can I touch them on). The data model is the same; the language flexes.

6. Tab 3: Relationships

Purpose. Individual-level intelligence. The dashboard surfaces named people the user should act on today.

6.1 The Six Relationship Surfaces

The Relationships tab is organized into six AI-curated lists. Each list is a named, ranked queue of individuals.

Surface	Definition	Action
Heating Up	Engagement velocity rising sharply over baseline	Make an ask, deepen the relationship
Cooling Off	Engagement velocity falling, or untouched-too-long	Re-engage, send check-in, reassign
Super-Supporters	Top tier of relationship score: high engagement, high giving, high referral, or high amplification	Cultivate, special access, host recruitment
Untouched Too Long	High-value contacts with no recorded touch in N days (user-configurable, default 60)	Schedule a touch
Ready for Ask	High relationship score + low recent ask frequency + AI-scored receptivity	Volunteer ask, donor ask, host ask, content amplification ask
At Risk	Negative sentiment signal, declining engagement, or explicit churn indicator	Recovery touch, leadership escalation

Each surface returns a ranked list of named individuals with a one-line AI rationale (“Why is this person here?”) and a one-click → Next Move conversion.

6.2 Campaign Mode Additional Surfaces

When Campaign Mode is active, four pipelines are added:

Volunteer Pipeline. Network members AI-scored as likely-to-volunteer, segmented by status (asked / committed / scheduled / active / lapsed).
Donor Pipeline. Network members AI-scored as likely-to-give-now, segmented by giving capacity and recency.
Host Pipeline. Network members AI-scored as likely-to-host-an-event, segmented by network reach and geographic value.
New Opt-Ins from Campaign Activity. Fresh recruits from doors, calls, petition, events — these are the highest-quality entry points and need fast follow-up.

6.3 Individual Drill-Down

Clicking any individual surfaces the full UVP view (respecting customer-tier exposure controls). This is the bridge from dashboard to the underlying record. Relationship history, contact log, sentiment, demographic profile, AI-suggested next action — all visible on one record screen.

6.4 Influencer Adaptation

Donor pipeline becomes “sponsorship pipeline” or “monetization pipeline.” Volunteer pipeline becomes “advocate pipeline” (people who amplify content). Host pipeline becomes “collaboration pipeline” (creators who would collab, locations that would feature). Same model, different labels.

7. Tab 4: Demographics

Purpose. Composition deep-dive. What is the shape of the network, and where is the shape wrong?

7.1 Relationship Mode Orientation

The Demographics tab in Relationship Mode shows the network’s composition across selectable axes:

Age, gender, party registration, household composition, occupation, income proxy, ethnicity proxy, geographic distribution, voter propensity tier.
Cross-sliced views. Age × geography. Party × engagement. Occupation × giving. The user picks any two axes; the AI surfaces the most informative cross-slice automatically.
AI Composition Insights. The AI flags imbalances and overconcentrations: “Your network is 73% women age 45+ in three ZIP codes. Three notable gaps relative to your stated audience.” Each insight is one-click → Opportunity.

7.2 Campaign Mode Orientation

When Campaign Mode activates, Demographics becomes a summary surface for demographic intelligence. It surfaces the top three to five demographic insights with an explicit handoff:

For full district-level gap analysis, geographic targeting, and precinct-level battleground intelligence, open Battleground.

The dashboard’s Demographics tab is the executive summary; the Battleground feature is the operating tool. This is deliberate — the dashboard says “here is what is interesting”; Battleground is where you operate on it. No duplication.

In Campaign Mode, the network’s demographic shape is overlaid on the district’s demographic shape by default. The gap is the most important visual on the screen — it is the campaign job stated in pictures.

7.3 Influencer Adaptation

District overlay becomes “audience benchmark overlay” — the influencer’s audience laid against the category benchmark (their niche, their platform’s overall demographic, their stated target audience). Same gap-analysis logic.

8. Tab 5: Opportunities

Purpose. The AI’s strategic recommendation surface. The dashboard’s most important tab in many ways — this is where data becomes action.

8.1 Opportunity Categories

Opportunities are AI-generated, ranked, and grouped into categories:

Category	Example
Network Growth	”Three high-density precincts in your district have <2% of residents in your network. Top three gap precincts shown.”
Network Depth	”47 contacts have engaged 3+ times but you have no phone or email for them. Capture push recommended.”
Message Lane Underuse	”You haven’t sent a REINFORCE message in 45 days. Three persuaded segments are at risk of cooling.”
Content Pattern Detection	”Your last 4 posts on ‘election integrity’ got 3x baseline engagement. Cadence opportunity.”
Verification Push	”112 unverified contacts have enough data to attempt voter roll matching. Estimated +8 percentage points to verified rate.”
Cross-Account Pattern (Aggregate Intelligence)	“Based on 47 similar accounts, hosting one in-person meet-and-greet per month increased super-supporter conversion by ~31%. You have not hosted one in 90 days.”
Donation Activation	”12 contacts in your network match the giving profile of recent first-time donors and have not been asked.”
Recruitment Opportunity	”Eight contacts have indicated availability and high engagement but have not been formally recruited as volunteers.”

8.2 Campaign Readiness Score (Relationship Mode only)

A single composite score, prominently displayed on the Opportunities tab, that tells the user how prepared their network is to activate when Campaign Mode flips on.

Components (all displayed, all clickable for drill-down):

Network Size vs. Target Goal (user-set target, with default suggestions by office level).
Verified Match Rate.
Super-Supporter Count.
Geographic Coverage (percent of target geography represented).
Contact Recency (percent of network touched in last 90 days).
Contactability (percent with verified phone or email).
Volunteer / Donor / Host Pre-Identification (counts AI-scored as likely-to-convert when asked).

The score is presented as a single 0–100 number with a letter grade and a trend line. Below it, the components are ranked by “biggest gap” — telling the user where the next improvement will move the score the most. Every component drives an Opportunity card that converts to a Next Move.

The Campaign Readiness Score is the single most important off-season metric in VRM. It gives a candidate a clear target and a measurable path. It also serves as the upgrade and engagement hook — the score visibly moves as the user does the work.

8.3 Campaign Mode Equivalent: Activation Score

When Campaign Mode is active, Campaign Readiness Score is replaced by an Activation Score with different components: voter contact pace vs. plan, ID progress, persuasion velocity, GOTV readiness, fundraising pace vs. goal. Same UI pattern, different inputs.

8.4 Opportunity → Next Move Bridge

Every Opportunity card has a one-click “Make this a Next Move” button. This creates a Next Move using the substrate from the voter-contact spec: owner, deadline, channel, closeout condition. The dashboard is operational, not informational.

Opportunities that are dismissed are tracked. Repeated dismissals teach the AI which categories the user does not care about and the ranking adjusts. Dismissed opportunities can be restored.

9. The AI Layer

AI presence is persistent and takes three forms across the entire dashboard.

9.1 The Insight Bar

A horizontal strip at the top of every tab. Rotating high-priority insights, each one sentence, each with an action:

“Your 35–44 demo dropped engagement 22% this week. View segment → Make this a Next Move → Dismiss”

The Insight Bar is the AI’s voice in the room. It is always present, always relevant to the current tab, always actionable.

9.2 Inline Annotations

Small AI callouts on individual metrics throughout the dashboard:

“This is 3x your 90-day baseline.” “Below district average by 14 points.” “First time this metric has crossed 50%.”

Inline annotations give context without leaving the chart. They are concise, factual, and never decorative.

9.3 The Strategic Analyst

A chat-style “ask your dashboard” affordance, accessible from any tab. The user types a natural-language question:

“Why is engagement dropping in Multnomah County?”

The Strategic Analyst answers from live data, citing specific metrics and surfacing relevant Opportunities. This is the same Strategic Analyst pattern from the Polling Engine spec — one consistent AI interlocutor across VRM, surfaced in context.

9.4 AI Output Tiering & Attribution

Own-account insights require no attribution beyond data lineage.
Aggregate Intelligence insights are always attributed: “Based on N similar accounts.” This builds trust, reinforces the data moat as a value proposition, and creates upgrade narrative.
Confidence levels are surfaced when low. The AI does not hedge unnecessarily, but does not present a low-confidence pattern as a fact.
Tier gating. In MVP, Aggregate Intelligence insights are exposed to all customer-tier users. Later monetization may gate this to Premium/Enterprise; the spec does not require it now.

9.5 AI Refresh Cadence

Pulse insights: daily.
Network and Demographics insights: daily.
Relationship surfaces (Heating Up, etc.): daily, with event-driven updates when major signals fire (new contact, new donation, new survey response).
Opportunities: daily, with major recompute weekly.
Strategic Analyst: real-time on query.

10. The Mode Shift

Relationship Mode and Campaign Mode share the same five tabs. The shift is in orientation, emphasis, and layering — not structure.

10.1 The Mode Indicator

A persistent header element on every dashboard screen indicates current mode. Switching modes is an account-level action, not a dashboard toggle — it reflects the customer’s actual operational reality.

10.2 What Changes When Campaign Mode Activates

Tab	Relationship Mode	Campaign Mode
Pulse	Network momentum, content engagement	+ Voter contact velocity, universe coverage, GOTV readiness, recruitment pipelines
Network	Network size, verified match, UVP completeness, sources, geography	+ Voter universe overlay, ID progress, contactability against universe
Relationships	Heating Up, Cooling Off, Super-Supporters, Untouched, Ready for Ask, At Risk	+ Volunteer Pipeline, Donor Pipeline, Host Pipeline, New Opt-Ins from Campaign Activity
Demographics	Network shape, gap insights	Network vs. district overlay by default; summary view with handoff to Battleground
Opportunities	Network growth, depth, engagement; Campaign Readiness Score	Persuasion, mobilization, fundraising; Activation Score replaces Readiness Score

10.3 Data Continuity

Relationship data does not disappear in Campaign Mode. The network remains the network — it is now a subset of the larger universe the campaign is contacting. Both data sets coexist. The dashboard makes the relationship between them visible.

When the cycle ends and the user returns to Relationship Mode, Campaign Mode data is preserved on the UVPs (in the Campaign Data layer) and continues to inform Relationship Mode analysis. New opt-ins acquired during the campaign carry forward as network members.

11. Influencer vs. Campaign Adaptation

The dashboard adapts contextually based on account type. The data model is the same; the labels and emphasis flex.

Concept	Campaign Account	Influencer Account
Voter universe	Voter universe within district	Audience
Persuadable	Persuadable voter	Engaged but not converted
GOTV moment	Election day	Activation moment (launch, drop, fundraising push)
District demographics	District demographics	Audience benchmark (niche/platform)
Volunteer pipeline	Volunteer pipeline	Advocate pipeline
Donor pipeline	Donor pipeline	Sponsorship / monetization pipeline
Host pipeline	Event host pipeline	Collaboration pipeline
Voter roll match	Voter roll match (VRM Verified)	Verified contact (email-validated, phone-validated, platform-matched)

The Strategic Analyst tone also flexes — slightly more strategic for campaigns, slightly more growth-oriented for influencers. Both tones are direct, data-grounded, and unsentimental.

12. Integration with Other VRM Systems

The dashboard does not stand alone. It is the surface layer over the rest of VRM.

12.1 The UVP

Every metric on the dashboard derives from UVPs. Every individual surfaced links to a UVP. Every Opportunity is grounded in patterns across UVPs. Dashboard performance depends on UVP data quality; the dashboard exposes that dependency via the VRM Verified match rate and UVP completeness metrics.

12.2 Next Moves Substrate

The dashboard is a Next Moves producer. Every Insight Bar item, every Opportunity card, every individual in a relationship surface, every demographic gap can be converted to a Next Move with one click. Next Moves are owned by users, scheduled, and closed out per the voter-contact substrate. The dashboard is not the to-do list; it is the source of the to-do list.

12.3 Polling Engine

Poll findings and survey responses feed Demographics, Relationships, and Opportunities tabs. A finding from a poll (“intensity dropped 18 points on issue X among segment Y”) becomes an Insight Bar item and an Opportunity card. The Methodology Agent’s confidence scoring carries through to dashboard insights derived from polling data.

12.4 Field Canvassing and Phone Banking

Contact logs from canvassing and phone banking flow into the network’s engagement signal, which feeds Heating Up / Cooling Off / Untouched surfaces. New opt-ins captured in the field appear in the Relationships tab the next day (or sooner via event-driven update).

12.5 Petition Mode

Petition signers, when matched to UVPs and where consent permits, flow into the network as new contacts with provenance. They appear on the Pulse tab as “new opt-ins from petition activity.” Petition contacts are particularly high-quality recruits — they have already taken a meaningful civic action.

12.6 Donation Integration Layer

Donation data is sourced in priority order:

Politogy donation portal (forthcoming, deep native integration).
WinRed API (read-only ingestion).
Anedot API (read-only ingestion).
Manual CSV import (fallback for any other processor).

The dashboard treats donation data as cross-cutting and source-agnostic. Pulse shows donation momentum. Relationships shows donor pipeline and giving recency. Demographics shows giving by segment. Opportunities shows fundraising gaps and timing. The user cannot tell from the dashboard which source the data came from — that is the integration layer’s job.

The forthcoming social media management feature will feed the dashboard. The dashboard reserves real estate and data slots so the feature plugs in without redesign:

Pulse — cross-platform reach, follower velocity, post-level engagement summary.
Network — followers as a network layer, cross-platform identity resolution feeding VRM Verified match rate.
Relationships — who engaged with which post, advocate identification.
Opportunities — content pattern detection, cadence optimization, post-type performance.

This spec does not define the social media feature itself. It defines the hooks.

13. Data Sources and Refresh Logic

13.1 Data Sources Feeding the Dashboard

Source	Feeds	Refresh
UVP layers (Identity, Contact, Geographic, Vote History)	All tabs	Voter file import cadence (typically weekly to monthly)
Relationship Data layer (tags, notes, contact log, relationship score)	Pulse, Relationships, Demographics	Real-time
Campaign Data layer (when in Campaign Mode)	All tabs	Real-time
Petition Data layer	Pulse, Network, Relationships	Real-time
Enrichment data	Network, Demographics	Vendor cadence (varies by vendor)
Aggregate Intelligence layer	Insight Bar, Opportunities	Politogy-controlled recompute
Donation integration	Pulse, Relationships, Demographics, Opportunities	API polling cadence (target: hourly for WinRed/Anedot; real-time for Politogy portal)
Social media data (future)	Pulse, Network, Relationships, Opportunities	Platform-dependent

13.2 Refresh Cadence Summary

Real-time: Individual record updates, contact log entries, donations from native portal, Strategic Analyst queries.
Daily: Pulse insights, Network metrics, Relationship surfaces, Demographics, Opportunities.
On-demand: User-triggered recompute on any tab.
Weekly: Major Opportunity recompute, Campaign Readiness Score components.

13.3 Computational Cost & Performance

Daily recompute is chosen deliberately over real-time for AI-derived insights. It produces stable, comparable trend signals, allows batched cross-account computation for Aggregate Intelligence, and keeps customer-tier API costs predictable. The user perceives the dashboard as “fresh today” — which is exactly what political and creator decision cycles require.

14. UI Surface Conventions

This section establishes presentation conventions; final visual design follows the politogy-vrm-brand standard.

14.1 Layout Skeleton

Header: Mode indicator, account name, search, notifications, user menu.
Tab bar: Pulse / Network / Relationships / Demographics / Opportunities.
Insight Bar: Below tab bar, persistent across all tabs.
Tab content: The active tab’s surfaces.
Strategic Analyst affordance: Persistent button or pinned input, accessible from any tab.

14.2 Card Conventions

Most dashboard content lives in cards. Every actionable card includes:

A title.
A primary metric or content.
AI annotation (where applicable).
A primary action (“Make this a Next Move,” “View details,” “Dismiss”).
A timestamp or freshness indicator.

14.3 Visual Hierarchy

Mode indicator is the most prominent header element.
Insight Bar is high-contrast and persistent — the user cannot scroll past the AI’s voice.
Numbers are large, supporting context is medium, drill-down options are subtle.
Trend direction is communicated visually (color, arrow) before numerically.

14.4 Accessibility & Density

The dashboard supports density toggles (comfortable vs. compact) and is fully keyboard navigable. AI annotations are screen-reader accessible. Color is never the sole carrier of meaning for trend direction or status.

15. Tier Gating, Permissions, and Monetization

15.1 Tier Gating in MVP

In MVP, the dashboard is uniform across tiers. All five tabs, all AI surfaces, all Aggregate Intelligence insights are available to all customer-tier accounts. This maximizes engagement and data generation in early adoption.

15.2 Future Tier Gating Candidates

The following may be tier-gated in future releases:

Aggregate Intelligence insights (Premium and above).
Cross-district benchmarking (Enterprise).
Custom AI-defined segments (Premium and above).
Historical comparison horizon depth (longer horizons for higher tiers).
Strategic Analyst query volume (rate-limited at lower tiers).

These are noted, not built. Tier gating is an account-layer concern that overlays the dashboard; the dashboard does not contain tier logic.

15.3 Customer-Tier Permissions

Per the VRM data system permissions table:

Account Admin: Full dashboard access for their account, all tabs, all insights within exposure controls.
Account Manager: Same, scoped to assigned geography.
Field User: Limited dashboard view — primarily Relationships tab restricted to assigned individuals.
Viewer: Read-only across permitted scope, no Next Move conversion.

15.4 Politogy-Tier Visibility

Politogy admins see the customer-tier dashboard plus internal overlays: data exposure controls, account health metrics, cross-account aggregates the customer cannot see, and the source provenance for every dashboard metric.

16. Open Questions for the Build Team

These are the implementation-level questions to resolve before development begins.

Anomaly detection thresholds. What change magnitude triggers an Insight Bar anomaly? Static thresholds (e.g., 20% week-over-week) vs. statistical (vs. account’s own variance) vs. AI-learned over time? Recommendation: start with statistical thresholds against rolling 90-day variance, with AI tuning over time.
Strategic Analyst scope. Does the Analyst query only the current account’s data, or can it surface aggregate insights when relevant? Recommendation: account data by default, aggregate insights when the user asks comparative questions, always attributed.
Insight Bar capacity. How many insights rotate? How quickly? How does the user pin a specific insight? Recommendation: 3–5 active insights, manual advance with auto-rotate option, pin via right-click or long-press.
Campaign Readiness Score weighting. Are component weights fixed, user-configurable, or AI-tuned by office level (school board vs. state house vs. federal)? Recommendation: AI-tuned default weights by office level, user override available.
Mode switch UX. What happens to in-flight Next Moves when the user flips from Relationship Mode to Campaign Mode? Recommendation: preserve all Next Moves, re-categorize automatically into Campaign Mode buckets where possible, surface a reconciliation screen for ambiguous cases.
Dashboard customization. Can users hide tabs, reorder cards, set personal defaults? Recommendation: card-level visibility toggles in MVP, no full reorder; full customization deferred to a later release.
Influencer account type detection. Is this a setting at account creation, or detected from behavior? Recommendation: setting at account creation, changeable in account settings.
Donation source unification. When a contact has donations recorded in WinRed and Anedot, how are they merged and displayed? Recommendation: merge by UVP match; display unified total with hover-revealed source breakdown.
Heating Up / Cooling Off velocity calculation. What signals contribute, with what weights? Recommendation: AI-learned weights with sane defaults (engagement events, contact recency, sentiment direction, ask response, content interaction).
Untouched-too-long threshold default. 30 days? 60 days? 90 days? Recommendation: 60 days for Relationship Mode default; 14 days for Campaign Mode active universe.
Aggregate Intelligence privacy floor. Minimum number of similar accounts required before a cross-account insight is surfaced (to prevent de-identification)? Recommendation: minimum 10 similar accounts; do not surface below that threshold.
Strategic Analyst conversation persistence. Does the conversation persist across sessions or reset? Recommendation: persist within a configurable retention window (default 30 days), with explicit “start fresh” option.

End of Specification

This document defines the conceptual architecture for the VRM Relationship Mode Dashboard. It is the source of truth for product, design, and engineering decisions about the dashboard surface. Detailed UI specifications, data contracts, and engineering implementation details follow in subsequent documents.

🗳️ Politogy VRM — V2 Specs

Explorer