J2R Solutions · Internal Brief

Training Dashboard — Project Brief

A phased plan to give the team a single source of truth for training and compliance — from "where are we right now" to "which partners will fall out of compliance in 90 days."

Status

Proposal · Awaiting approval

Author

Jonathan Spigler

Date

Apr 28, 2026

TL;DR

Build a Training & Compliance dashboard in Salesforce as the team's home base for "where are we, what's overdue, who's at risk." We have the data — Training__c with 23 fields and live records — but we're missing the structure to compute partner-level compliance %. Ship in three phases over ~6 weeks:

Phase 1 · 3–5 days

Day-One View

Overdue, expiring, throughput, framework breakdown.

Phase 2 · 1–2 weeks

Training Catalog

Deduplicate the program list. New Training_Program__c.

Phase 3 · 2–3 weeks

Compliance & Risk

Per-partner % · tier-aware rules · 90d forecast.

Why now

Compliance is operational, not occasional. ISO 9001/27001, CMMC, and HR cyber awareness are all recurring. Tracking by spreadsheet (or by memory) doesn't scale as we grow partners and tiers.
Partner training is high-stakes. Losing a tier with Palo Alto / F5 / Forescout because a few certs lapsed is a revenue and reputation hit. We need to see it coming 90 days out.
The data is already there. Training__c has 1,400+ records with dates, vendors, contacts. We're sitting on the inputs — we just haven't connected them to the right outputs.
Phasing limits risk. Phase 1 gives immediate value with minimal org changes. Each phase compounds on the previous without locking us into the full design upfront.

What we have today

Training__c object

23 fields including Contact, Category, Type, Vendor, Program Name, Due/Start/Completion/Expiry dates, Score, Credential link
Credential_Issued__c = "training completed"
Reports + Activities + Field History enabled

Account + Contact

Partners identified by Account.Type = "OEM Partner"
Tier captured (Premier / Innovator / Core)
Trainings link to Contacts — partner roll-up requires Contact → Account hop

What's missing to compute "compliance":

No framework grouping (CMMC vs ISO vs HR), no "required" flag (vendor cert vs mandatory), and no per-partner requirement definitions (Palo Alto Premier needs 4 sales + 2 tech, etc.). Phases below add each missing piece.

Phase 1

Day-One View

Estimate

3–5 days

Ship the dashboard with what we already track plus two new fields. Immediate value: every overdue item, every expiring cert, training throughput trend, and where the gaps are by category — visible to anyone in the team.

Org changes

• Add Framework__c picklist on Training__c
• Add Required__c checkbox on Training__c
• Add Account__c formula = Contact__r.AccountId
• Backfill Framework on existing rows (script or Flow)

Build

• 8 source reports (overdue, expiring, throughput, etc.)
• 1 dashboard with 8 components
• Folder permissions for the team
• Subscriptions for weekly digest

Deliverable

A live "Training Home Base" dashboard. Mockup: phase-1.html

Phase 2

Training Catalog

Estimate

1–2 weeks

Decouple "the catalog of training programs" from "someone took a training." Today, free-text Program_Name__c means "ISO 9001:2015 Awareness Training" and "ISO 9001 :2015 Training" look like two different things. A real catalog object kills duplicates and is the foundation for Phase 3 compliance rules.

Org changes

• Create Training_Program__c object (Vendor, Framework, Cert Level, Validity Days)
• Add Program__c Lookup on Training__c
• Migrate distinct Program_Name__c values into catalog rows
• Auto-link historical Training__c records (fuzzy match + manual cleanup queue)

Build

• Catalog view (list + by-vendor + by-framework breakdown)
• Cleanup queue dashboard for unmatched names
• Validation rule preventing new Training__c without a Program lookup
• Lightning Record Page for Training_Program__c

Deliverable

A reusable training catalog + cleanup tooling. Mockup: phase-2.html

Phase 3

Compliance & Risk

Estimate

2–3 weeks

Define "what does each partner need" as data, then compute compliance % automatically. Universal requirements (ISO 9001, HR cyber — every employee) and tier-specific requirements (Palo Alto Premier needs 4 sales + 2 tech) coexist in a single rules object. A nightly Flow rolls up scores onto Account so reports stay simple.

Org changes

• Create Compliance_Requirement__c object
(Program lookup, Account lookup, Tier filter, Required Count, Scope)
• Seed universal rules (ISO 9001, ISO 27001, Cyber, Code of Conduct)
• Seed per-partner-tier rules with vendor managers (Palo Alto, F5, Forescout, etc.)
• Add Compliance_Pct__c + Compliance_Status__c on Account
• Scheduled Flow / Apex computes scores nightly

Build

• Org compliance KPI banner
• Universal requirements coverage card
• Partner Red List (sortable, tier-aware)
• Per-partner drilldown (recommended actions)
• 90-day forecast (expiring certs → projected drop)
• Compliance trend (12-month line)

Deliverable

"Compliance & Risk" dashboard with proactive forecasting. Mockup: phase-3.html

Decisions needed

1. Approve Phase 1 to start

Two field additions, no schema changes. Low risk, high signal. Recommendation: green-light immediately.

2. Owner for the Compliance Requirements model

Phase 3 needs someone who can answer "what exactly does a Premier-tier Palo Alto partner need?" — a partner ops or compliance lead. Without this owner, Phase 3 stalls regardless of how clean the data model is.

3. CRM Analytics or stay native?

All three phases assume native Salesforce reports + a nightly Flow. If we have CRMA licenses already, Phase 3 forecasting gets cleaner. Default: native.

4. Compliance threshold

When is a partner "compliant"? 100% of requirements? 90%? The threshold drives the red-list cutoff and the 90-day forecast. Recommendation: 100% required, with "At Risk" = 80–99% and "Non-Compliant" = <80%.

Risks & mitigations

Risk	Mitigation
Data quality on existing Training__c rows	Phase 2 cleanup queue. Treat unmatched rows as a known backlog, not a blocker.
Per-partner rules grow unbounded	Compliance_Requirement__c supports tier filters — define rules once per tier, not per partner.
Nightly Flow timing / governor limits	Batchable Apex if Flow can't handle volume. Monitor with debug logs first 2 weeks.
Vendor cert taxonomies change yearly	Catalog is editable; rules have `Active__c`. Quarterly review with each vendor manager.
Dashboard drift / fatigue	Subscriptions to weekly digest. Dashboard owner reviews component relevance quarterly.

Indicative timeline

Week 1

Phase 1 — Day-One View

Weeks 2–3

Phase 2 — Training Catalog

Weeks 4–6

Phase 3 — Compliance & Risk

Assumes one admin/dev allocated and decisions on requirement rules made in week 3.