Jarvis Analytics — Implementation Playbook (DSO)

Jarvis Analytics Implementation Playbook

Analytics & Business Intelligence for Dental Service Organizations

---

1. Executive Summary

What Jarvis Analytics Does

Jarvis Analytics is a cloud-based business intelligence platform that aggregates data from practice management systems across all locations, transforming raw operational data into actionable insights through automated dashboards, KPI tracking, and predictive analytics for production, collections, scheduling efficiency, and provider performance.

Why DSOs Benefit from AI-Powered Analytics

At scale, DSOs face a fundamental data challenge: critical operational intelligence is trapped in dozens of disconnected PMS databases, making cross-location comparison nearly impossible without manual data aggregation. Jarvis Analytics solves this by:

• Standardizing metrics across locations regardless of which PMS each office uses
• Automating reporting that would otherwise require analyst headcount to compile
• Enabling pattern recognition across your portfolio—identifying which locations are underperforming relative to peers, which providers are outperforming, and which operational practices should be replicated
• Accelerating decision cycles from monthly or quarterly reviews to near-real-time intervention

For a 30-location DSO, the difference between monthly Excel reports and daily automated dashboards represents roughly 40-60 hours/month of analyst time recovered, plus the compounding value of faster operational decisions.

Expected Timeline: Decision to Full Deployment

DSO Size	Pilot Phase	Full Rollout	Total Timeline
15-25 locations	4-6 weeks	6-8 weeks	10-14 weeks
26-40 locations	4-6 weeks	8-12 weeks	12-18 weeks
41-50 locations	4-6 weeks	12-16 weeks	16-22 weeks

Timeline assumes standard integrations. Complex multi-PMS environments or custom reporting requirements may extend by 2-4 weeks.

---

2. Pre-Implementation Checklist (Weeks 1–2)

Technical Requirements

Network & Infrastructure

☐ Minimum 25 Mbps upload/download speed at each location (test with speedtest.net during peak hours)
☐ Verify firewall allows outbound HTTPS (port 443) to Jarvis Analytics cloud endpoints
☐ Document current network topology—identify locations with VPN dependencies or restricted internet access
☐ Confirm workstation browser compatibility (Chrome 90+, Edge 90+, Firefox 85+ recommended)

Practice Management System Requirements

☐ Document PMS vendor and version at each location:

• Dentrix: Version 16.1 or higher
• Eaglesoft: Version 19 or higher
• Open Dental: Version 19.4 or higher
• Other PMS: Confirm API availability with Jarvis 🔵

☐ Verify PMS database access credentials exist for integration (not individual user logins)
☐ Confirm database server accessibility—local server vs. cloud-hosted

Hardware

☐ No dedicated hardware required (cloud-based SaaS)
☐ Identify 1-2 dedicated workstations per location for primary dashboard access
☐ Optional: Recommend large-format displays (32"+) for real-time dashboard visibility in manager offices

Vendor Onboarding Steps

Step	Owner	Timeline	Deliverable
🔵 Execute MSA and BAA	Legal + Jarvis	Days 1-3	Signed agreements
🔵 Kick-off call	VP Ops + Jarvis CSM	Day 4	Project plan, timeline
🔵 Technical discovery call	IT Lead + Jarvis Integration	Days 5-7	Integration requirements doc
Assign internal project manager	VP Ops	Day 5	Named PM with bandwidth
🔵 Receive API credentials/documentation	IT Lead	Days 7-10	Integration credentials

Key Contacts to Establish

☐ Jarvis Customer Success Manager (CSM): ______________________
☐ Jarvis Technical Integration Lead: ______________________
☐ Jarvis Support Escalation Contact: ______________________
☐ Support portal access and ticket submission process confirmed

Data & Access Prerequisites

☐ PMS database credentials (read-only access minimum) for each location
☐ API keys generated (if using API-based integration vs. direct database connection)
☐ Historical data scope defined—recommend minimum 24 months for trend analysis
☐ Data dictionary review: Map your internal terminology to Jarvis standard fields 🔵
☐ User provisioning plan: List all users needing access with role assignments

User Role Matrix

Role	Access Level	Typical Users
Executive	Full portfolio view, all locations	CEO, CFO, VP Ops, CDO
Regional	Multi-location view (assigned region)	Regional Managers
Location Admin	Single location, all metrics	Office Managers
Provider	Single location, own metrics + team	Dentists, Hygienists
Read-Only	Limited dashboards	Board members, investors

Enterprise-Level Requirements

Centralized vs. Location-Level Architecture

🟣 Decision Required: Hosting model selection

• Recommended: Centralized cloud instance with location-level data partitioning
• Single tenant vs. multi-tenant considerations based on data isolation requirements
• Jarvis standard deployment is multi-tenant SaaS with logical data separation

Identity & Access Management

☐ SSO integration requirements documented (SAML 2.0, OAuth 2.0 supported)
☐ SSO provider identified: Okta / Azure AD / Google Workspace / Other: ______
☐ 🔵 SSO configuration call scheduled with Jarvis
☐ Role-based access control (RBAC) structure defined
☐ User provisioning/deprovisioning workflow established (manual vs. SCIM)

Network Standards

☐ Document any locations with non-standard network configurations
☐ Identify locations requiring VPN or proxy exceptions
☐ Whitelist Jarvis IP ranges/domains in corporate firewall (obtain from Jarvis) 🔵

Stakeholder Alignment Map

Board/Investors

• Inform: AI/analytics investment rationale, expected ROI, timeline
• Approve: 🟣 Budget allocation, data governance policies
• Frequency: Quarterly updates post-deployment

C-Suite

Role	Alignment Need
CEO	Strategic alignment, investment approval 🟣
CFO	Budget approval, ROI expectations, financial metrics definition 🟣
CDO	Clinical metrics validation, provider adoption strategy 🟣
VP Operations	Project ownership, rollout strategy, success metrics 🟣
CIO/IT Director	Technical requirements, security review, integration ownership

Regional Managers

• Inform: Rollout timeline, expectations for their locations
• Engage: Input on pilot location selection, local context
• Responsibility: Cascading communication, local champion support

Location-Level

• Office Managers: Operational leads, primary dashboard users
• Providers: Data subjects and consumers—critical for buy-in
• Staff: Limited direct interaction, but affected by new workflows

Baseline Metrics to Capture

⚠️ Critical: Capture these BEFORE go-live to measure ROI accurately

Standardized Metric Definitions

Apply these definitions uniformly across all locations for valid cross-location comparison

Metric Category	Specific Metrics	Definition	Collection Method
Production	Gross Production	Total value of services rendered at UCR fees	PMS report
	Net Production	Gross production minus adjustments/write-offs	PMS report
	Production per Visit	Net production ÷ patient visits	Calculated
	Production per Provider Hour	Net production ÷ clinical hours worked	PMS + scheduling
Collections	Collection Rate	Collections ÷ Net Production (trailing 90 days)	PMS + accounting
	Days in A/R	Average age of outstanding receivables	PMS report
	A/R over 90 days	% of A/R aged 90+ days	PMS report
Scheduling	Chair Utilization	Scheduled chair hours ÷ available chair hours	PMS scheduling
	Broken Appointment Rate	No-shows + same-day cancellations ÷ total scheduled	PMS report
	Reappointment Rate	Patients leaving with next appointment ÷ total visits	PMS report
Clinical	Case Acceptance Rate	Accepted treatment ÷ presented treatment (by $)	PMS treatment plans
	Hygiene to Doctor Conversion	Hygiene visits with doctor exam or treatment ÷ total hygiene	PMS report
	Treatment Plan Aging	Average days from diagnosis to treatment	PMS report
Operational	New Patients/Month	Unique new patient visits	PMS report
	Patient Retention	Active patients (seen in 18 mo) ÷ total patient base	PMS report
	Revenue per Operatory	Net production ÷ number of ops	Calculated

Baseline Data Collection Protocol

☐ Export 6-month trailing data for each metric above
☐ Use consistent date range across all locations (recommend: last 6 completed months)
☐ Document any known data quality issues by location
☐ Store baseline in centralized spreadsheet/database for post-implementation comparison
☐ Assign ownership for baseline collection: ______________________ (Name/Role)
☐ Deadline for baseline completion: ______________________ (Date)

Estimated Time: 2-4 hours per location for data extraction; 4-8 hours central for consolidation

---

3. Location Readiness Assessment

Scoring Framework

Score each factor 1-5 for every location, then calculate the composite score.

Factor 1: IT Infrastructure Maturity (Weight: 25%)

Score	Criteria
5	Fiber internet 100+ Mbps, hardware <3 years old, current PMS version, cloud backup
4	Reliable internet 50+ Mbps, hardware <5 years old, PMS within 2 versions of current
3	Standard internet 25+ Mbps, hardware functional, PMS supported version
2	Inconsistent internet, aging hardware, PMS version approaching end-of-life
1	Unreliable internet, hardware failures common, outdated PMS requiring upgrade

Factor 2: Staff Tenure & Adaptability (Weight: 20%)

Score	Criteria
5	<10% annual turnover, prior successful tech adoption, staff requests new tools
4	10-20% turnover, generally positive tech adoption history
3	20-30% turnover, mixed tech adoption results
2	30-40% turnover, staff resistance to recent changes
1	>40% turnover, multiple failed technology implementations

Factor 3: Patient Volume (Weight: 20%)

Higher volume = higher impact but also higher risk during transition

Score	Criteria
5	Moderate-high volume (60-80th percentile for your portfolio)—optimal balance
4	Moderate volume (40-60th percentile)—manageable risk, meaningful data
3	High volume (top 20%)—highest impact but highest risk
2	Lower volume (20-40th percentile)—lower risk but less representative
1	Very low or very high volume outlier—not representative for pilot

Factor 4: Tech Stack Compatibility (Weight: 20%)

Score	Criteria
5	PMS with native Jarvis integration, imaging with API access, modern auxiliary systems
4	PMS with tested Jarvis integration, standard imaging setup
3	PMS with available but untested integration, some legacy systems
2	PMS requires custom integration work, multiple disparate systems
1	Unsupported PMS version, significant custom development required

Factor 5: Local Champion Availability (Weight: 15%)

Score	Criteria
5	Enthusiastic tech-forward provider + capable office manager both identified and committed
4	Strong office manager champion with provider support
3	Willing champion identified but limited bandwidth
2	No natural champion, but no active resistance
1	No champion available, key staff resistant to change

Composite Score Calculation

Readiness Score = (IT × 0.25) + (Staff × 0.20) + (Volume × 0.20) + (Tech × 0.20) + (Champion × 0.15)

Composite Score	Readiness Tier	Rollout Recommendation
4.0 - 5.0	Tier 1: High Readiness	Wave 1 pilot candidate
3.0 - 3.9	Tier 2: Moderate Readiness	Wave 2 deployment
2.0 - 2.9	Tier 3: Low Readiness	Wave 3, with remediation
Below 2.0	Tier 4: Not Ready	Remediation required before deployment

Location Assessment Template

Location	IT Infra (1-5)	Staff (1-5)	Volume (1-5)	Tech Stack (1-5)	Champion (1-5)	Composite	Tier
Location 1
Location 2
...

Rollout Sequence Recommendation

Based on composite scores, recommend:

Wave 1 (Pilot): Select 2-3 locations from Tier 1 that also represent diversity in:

• Geographic region (if regionally distributed)
• PMS type (if multiple PMS across portfolio)
• Practice type (GP, specialty mix)

Wave 2: All remaining Tier 1 and Tier 2 locations

Wave 3: Tier 3 locations after remediation items addressed

Defer: Tier 4 locations until infrastructure or staffing issues resolved

---

4. Rollout Strategy

Wave Structure Recommendation

Wave 1: Pilot (2-3 locations)

Duration: 4-6 weeks
Purpose: Validate integration, refine training, establish baseline for success metrics

Wave 2: Expansion (5-8 locations)

Duration: 4-6 weeks
Purpose: Scale learnings, stress-test support model, build momentum

Wave 3: Broad Deployment (remaining locations)

Duration: 6-12 weeks depending on portfolio size
Purpose: Complete rollout with optimized playbook

Wave 4 (if applicable): Remediation locations

Duration: As needed
Purpose: Deploy to locations requiring infrastructure upgrades

Wave 1 Pilot Location Selection Criteria

Select locations that are:

☐ High readiness (Tier 1 composite score 4.0+)
☐ Manageable risk (not your highest-revenue location)
☐ Representative (reflects common PMS, practice type, patient mix)
☐ Accessible (regional manager or central team can be on-site easily)
☐ Champion-led (enthusiastic local owner of success)

🟣 Executive Decision: Final pilot location selection requires VP Ops and CDO approval

Recommended Pilot Selection

Selection Criteria	Location A	Location B	Location C
Readiness Score
PMS Type
Practice Type
Revenue Risk Level
Champion Name
Regional Manager

Timeline Per Wave

Wave 1 Detailed Timeline

Week	Activities
Week 1	Integration setup, data connection validation, test environment
Week 2	Configuration, dashboard customization, training prep
Week 3	Champion training, soft launch, parallel operations
Week 4	Full go-live, daily monitoring, issue resolution
Week 5-6	Optimization, document learnings, prepare Wave 2 playbook

Buffer Between Waves

Minimum 1-week buffer between waves to:

• Document lessons learned
• Update training materials
• Address any systemic issues
• Brief next wave's regional managers and champions

Go/No-Go Criteria

Wave 1 → Wave 2 Go/No-Go Checklist

Criteria	Target	Actual	Status
Data integration accuracy	>98% data matching PMS		☐ Go / ☐ No-Go
Dashboard uptime	>99% during business hours		☐ Go / ☐ No-Go
Staff training completion	100% role-required training		☐ Go / ☐ No-Go
Critical bugs resolved	Zero P1/P2 open issues		☐ Go / ☐ No-Go
Champion confidence score	4+ (1-5 scale)		☐ Go / ☐ No-Go
User adoption rate	>80% daily active users		☐ Go / ☐ No-Go

🟣 Executive Decision: Go/No-Go determination at each wave gate

Wave 2 → Wave 3 Additional Criteria

Criteria	Target	Actual	Status
Support ticket volume	<2 tickets/location/week		☐ Go / ☐ No-Go
Mean time to resolution	<4 hours for P1 issues		☐ Go / ☐ No-Go
Cross-location data consistency	Dashboard metrics match PMS within 2%		☐ Go / ☐ No-Go
Regional manager confidence	4+ (1-5 scale)		☐ Go / ☐ No-Go

Rollback Plan

Rollback Triggers

• Data integrity issues affecting >5% of records
• System downtime >4 hours during business hours
• Critical security vulnerability identified
• Staff unable to perform core job functions
• Provider refusal to continue using system

Rollback Procedure

Level 1: Soft Rollback (Location-Specific)

1. Disable Jarvis dashboards at affected location(s)
2. Revert to previous reporting methods
3. Disconnect data integration (read-only, no operational impact)
4. Document issues with screenshots, logs
5. Engage Jarvis support for resolution 🔵
6. Resume deployment when issues resolved

Level 2: Wave Pause

1. Halt deployment of current wave
2. Complete rollback for affected locations
3. Continue operation at successfully deployed locations
4. Conduct root cause analysis
5. 🟣 Brief executive team on status
6. Define resolution timeline before resuming

Level 3: Full Program Pause

1. Pause all deployment activities
2. Maintain existing successful integrations (no new locations)
3. Escalate to Jarvis executive sponsor 🔵
4. 🟣 Executive decision on program continuation
5. Define go-forward criteria

Rollback Communication Template

"Due to [specific issue], we are temporarily pausing Jarvis Analytics deployment at [location(s)]. This does not affect patient care or core operations. Our team is working with Jarvis to resolve [issue]. We expect to resume deployment on [date]. Please continue using [previous method] for reporting needs. Questions? Contact [name]."

---

5. Configuration & Integration (Weeks 2–3)

PMS Integration: Step-by-Step

Dentrix Integration

Pre-requisites: ☐ Dentrix version 16.1 or higher confirmed
☐ SQL Server access credentials obtained
☐ Dentrix server IP/hostname documented
☐ Firewall rules configured for Jarvis connector

Integration Steps:

1. ☐ 🔵 Receive Jarvis Dentrix Connector installer from Jarvis support
2. ☐ Schedule installation window (recommend after-hours; 30-minute downtime)
3. ☐ Install connector on Dentrix server or designated integration server
4. ☐ Configure SQL connection string with read-only credentials
5. ☐ 🔵 Run initial connection test with Jarvis support on call
6. ☐ Initiate historical data sync (24-48 hours depending on database size)
7. ☐ ⚠️ Validate data accuracy: Compare 10 random patient records between Dentrix and Jarvis
8. ☐ Configure real-time sync schedule (recommended: every 15 minutes)
9. ☐ Document connector version and configuration for future reference

Estimated Time: 2-3 hours active setup; 24-48 hours background sync

Eaglesoft Integration

Pre-requisites: ☐ Eaglesoft version 19 or higher confirmed
☐ Eaglesoft API access enabled (Patterson support may be required)
☐ API credentials generated
☐ Network access from Eaglesoft server to internet confirmed

Integration Steps:

1. ☐ ⚠️ Contact Patterson to enable API access if not already active (can take 3-5 business days)
2. ☐ 🔵 Provide Eaglesoft API credentials to Jarvis via secure portal
3. ☐ 🔵 Jarvis configures cloud-to-cloud integration
4. ☐ Verify firewall allows outbound connection from Eaglesoft server
5. ☐ 🔵 Run connection test with Jarvis support
6. ☐ Initiate historical data sync
7. ☐ Validate data accuracy: Compare 10 random patient records
8. ☐ Confirm real-time sync operational

Estimated Time: 1-2 hours active setup (plus Patterson lead time); 24-48 hours background sync

Open Dental Integration

Pre-requisites: ☐ Open Dental version 19.4 or higher confirmed
☐ Open Dental API key generated (Setup → Miscellaneous → API)
☐ Open Dental Service (eConnector) running

Integration Steps:

1. ☐ Generate Open Dental API key from Setup menu
2. ☐ 🔵 Provide API key to Jarvis via secure portal
3. ☐ Verify eConnector service is running and accessible
4. ☐ 🔵 Jarvis configures API integration
5. ☐ Run connection test
6. ☐ Initiate historical data sync
7. ☐ Validate data accuracy: Compare 10 random patient records
8. ☐ Confirm real-time sync operational

Estimated Time: 1-2 hours active setup; 12-36 hours background sync

Multi-PMS Environment Considerations

If your DSO uses multiple PMS platforms:

☐ 🔵 Discuss data normalization approach with Jarvis (how are fields mapped across systems?)
☐ Define location-to-PMS mapping table
☐ Establish consistent naming conventions (e.g., procedure codes, provider names)
☐ ⚠️ Plan additional QA time for cross-PMS data validation
☐ 🟣 Decide: uniform KPI definitions or PMS-specific variations?

Test Environment Setup

Centralized Test Environment (Recommended for DSO)

☐ 🔵 Request Jarvis sandbox/staging environment
☐ Configure sandbox with representative data from 2-3 locations
☐ Mirror production SSO configuration in sandbox
☐ Test all user roles in sandbox before production deployment
☐ Use sandbox for train-the-trainer sessions

Validation Checklist

Test Case	Expected Result	Actual Result	Pass/Fail
User login via SSO	Successful authentication
Dashboard loads <5 seconds	All widgets render
Production data matches PMS	<2% variance
Collection data matches PMS	<2% variance
Scheduling data accurate	Appointments match
Role permissions correct	Users see only permitted data
Date filters working	Data adjusts appropriately
Export to Excel/PDF	Clean, accurate exports
Mobile access (if applicable)	Responsive design functional

Data Migration / Historical Data Ingestion

☐ Define historical data scope: ______ months (recommend 24+ for trend analysis)
☐ 🔵 Confirm Jarvis can ingest historical data from your PMS version
☐ Schedule initial data load during off-hours (can impact PMS performance)
☐ Monitor sync progress via Jarvis admin dashboard
☐ ⚠️ Validate historical data integrity before using for baseline comparisons

Data Quality Remediation

Common issues to check: ☐ Duplicate patient records
☐ Incomplete provider assignments
☐ Orphaned transactions
☐ Inconsistent procedure codes
☐ Missing appointment statuses

Security & HIPAA Compliance

Enterprise-Level HIPAA Checklist

Requirement	Status	Documentation
☐ BAA executed with Jarvis		Signed copy on file
☐ Data encryption in transit (TLS 1.2+)		Jarvis security documentation
☐ Data encryption at rest (AES-256)		Jarvis security documentation
☐ Access controls configured		RBAC matrix documented
☐ Audit logging enabled		Jarvis confirms logging active
☐ User access reviews scheduled		Quarterly review process defined
☐ Breach notification procedures confirmed		In BAA
☐ Data retention policy aligned		Jarvis retention = your policy
☐ Minimum necessary standard applied		Role permissions documented
☐ SSO enforced (no shared passwords)		SSO configuration confirmed

🔵 Request Jarvis SOC 2 Type II report and HIPAA compliance documentation

Standardized vs. Location-Specific Configuration

Standardize Centrally

Configuration Element	Standard Setting	Rationale
KPI definitions	Per baseline metrics section	Cross-location comparison validity
Dashboard layouts (core)	Unified executive views	Consistent reporting
User role permissions	RBAC matrix	Security consistency
Data refresh frequency	15-minute sync	Timely data across portfolio
Alert thresholds	Portfolio-wide targets	Unified performance standards
Fiscal calendar	Aligned periods	Financial reporting accuracy
Provider productivity benchmarks	Specialty-adjusted standards	Fair comparison

Allow Local Discretion

Configuration Element	Local Authority	Guidelines
Custom dashboard widgets	Office Manager	Must not replace core dashboards
Provider-level views	Provider preference	Within role permissions
Alert notification recipients	Office Manager	Must include standard escalation
Report distribution lists	Office Manager	Regional manager always included
Operational goal targets	Regional Manager	Within corporate range

---

6. Team Training Plan

Train-the-Trainer Model

Champion Selection Criteria

Each location needs ONE primary champion. Ideal candidates:

☐ Office manager or lead provider (has influence and daily presence)
☐ Tech-comfortable (uses software confidently, troubleshoots independently)
☐ Strong communicator (can teach others clearly)
☐ Committed tenure (not leaving in next 6+ months)
☐ Available for 4-6 hours of champion training + ongoing support role
☐ Positive attitude toward change (not just compliant—enthusiastic)

Champion Responsibilities

Responsibility	Time Commitment
Complete champion certification training	4-6 hours (one-time)
Train location staff (all roles)	4-8 hours (during rollout)
Serve as first-line support for team questions	Ongoing (15-30 min/day initially)
Escalate technical issues to regional/central	As needed
Participate in weekly champion sync calls	30 min/week
Provide feedback on training materials	As needed
Monitor adoption at their location	15 min/day (check dashboard usage)

Champion Certification Training

Format: 🔵 Live virtual training led by Jarvis + central team
Duration: Two 2-hour sessions or one 4-hour session
Attendees: All location champions + central implementation team

Session 1: Platform Mastery (2 hours)

• Platform navigation and core dashboards
• KPI definitions and data sources
• Filtering, date ranges, location switching
• Export and sharing features
• Common troubleshooting

Session 2: Training Delivery (2 hours)

• How to train each role (role-specific modules)
• Handling resistance and questions
• Using training materials effectively
• Certification quiz
• Q&A and practice scenarios

☐ Champions must pass certification quiz (80% minimum) to proceed
☐ Certification tracked in central training log

Role-Specific Training Outlines

Champions deliver these trainings at their locations using standardized materials.

Providers (Dentists, Specialists, Hygienists with Dashboard Access)

Training Time: 30-45 minutes
Format: Live demo (in-person or screen share) + self-guided exploration
Delivered by: Location champion

Learning Objectives:

1. Access and navigate personal productivity dashboard
2. Understand key metrics: production, case acceptance, schedule utilization
3. Compare personal metrics to location/portfolio benchmarks
4. Use filters to analyze performance by time period, procedure type
5. Know when and how to request support

Training Outline:

• 5 min: Why we're using Jarvis (corporate vision, benefits)
• 10 min: Logging in, navigation, basic filters
• 15 min: Provider dashboard walkthrough—YOUR metrics
• 5 min: Comparing to benchmarks—what this means
• 5 min: Common questions, where to get help
• 5 min: Hands-on exploration

Common Resistance Points & Responses:

Resistance	Response
"I don't want to be micromanaged"	"This tool gives YOU visibility into your own performance. You see it first. It's about self-improvement, not surveillance."
"I don't trust the data"	"The data comes directly from your PMS—what you enter is what you see. If something looks wrong, let's troubleshoot together."
"I don't have time for this"	"Initial training is 30 minutes. After that, 2 minutes daily glance at your dashboard. It actually saves time vs. manual tracking."

Day 1 Cheat Sheet: Providers

┌─────────────────────────────────────────────────────────────┐
│ JARVIS ANALYTICS - PROVIDER QUICK REFERENCE                │
├─────────────────────────────────────────────────────────────┤
│ LOGIN: yourcompany.jarvisanalytics.com (SSO with email)    │
│                                                             │
│ YOUR DASHBOARD: Click "Provider View" → Select your name   │
│                                                             │
│ KEY METRICS:                                                │
│ • Production/Day - Your revenue contribution                │
│ • Case Acceptance - % of treatment accepted (goal: >85%)   │
│ • Chair Utilization - Time seeing patients vs. available   │
│                                                             │
│ DATE FILTERS: Top right corner. Default = current month    │
│                                                             │
│ COMPARE TO PEERS: Click benchmark toggle (shows portfolio  │
│ average)                                                    │
│                                                             │
│ NEED HELP? Ask [Champion Name] or email help@company.com