# Workforce health insights: page brief **Page 3 of 6** in the Solutions set. **URL:** `/solutions/workforce-health-insights/` **Archetype:** Program page, Section ② "data out" **Mock to build from this brief:** `claude-fable/vantage-fit-workforce-health-insights-v1.html` **Menu badge:** `Data out` **Written:** 2026-08-11 This page replaces three retired, low-demand pages: participation analytics, challenge analytics, and activity/health analytics. It must read as one product surface, not three pages stapled together. --- ## 0. The one-line strategy **One admin console, three views, and an honest boundary around what HR can never see.** Everything on the page is subordinate to that. The console is the page. The rest of the sections explain it, qualify it, and tell the reader what leaves the platform. --- ## 1. Research takeaways that decided the structure Sources are cited with the dossier's aliases: `astro/` = `/Users/anjanpathak/work/gitcode/vantagefit-astro/`, `vfit-os/` = `/Users/anjanpathak/work/gitcode/vc-os/vfit-os/`, `dash-design/` = `/Users/anjanpathak/work/gitcode/vc-dashboard-design/`. Dossier files are at `scratchpad/research/`. ### 1.1 The reporting layer is two products stacked, and that changes the whole page The base layer ships to every client: the Overview with four KPI cards, At a Glance, Recommended Actions, and six CSV reports. The premium layer (Org Wellness Score, Wellness Leagues, Health Insights) is **entitlement-gated to annual clients, contract negotiated, and provisioned by the account manager after data indexing. It is not a toggle.** Non-entitled admins see greyed cards with a "Contact Account Manager" overlay. `[vfit-os/specs/product/09-admin-platform/admin-dashboard.md]`, `[research/insights-reports.md §0, §5.2]` **Structural consequence:** the console's third view carries a visible `Annual contract` chip on the three gated cards, and the page says so in plain copy twice (console note, FAQ 3). Pretending everyone gets health-risk prevalence would be the single biggest over-claim available on this page, and it is also unnecessary: the honesty is what answers "is this a vanity dashboard". ### 1.2 There are four data stories, not three, and they must not be blended into a fifth number Adoption, program, behavior, outcome. Each has its own denominator, refresh cadence and entitlement. The dossier is explicit that they must be kept as four independent measures and never rolled into a blended composite. `[research/insights-reports.md §2, §2 "How the four stories should be framed"]` **Structural consequence:** the retired three pages map onto three console tabs, and the fourth story (health signal) rides inside tab 3 rather than becoming a fourth tab. Three tabs, because the merge story is "three pages, one console". A fourth tab would reintroduce the stapled feeling. ### 1.3 The strongest single privacy proof is a product string, not a policy statement When an admin targets a challenge at a health-risk cohort, the system returns a **count only**, plus the literal on-screen disclaimer **"The list of users is not displayed to protect individual privacy."** Any audience filter automatically marks the challenge Private. `[vfit-os/specs/product/03-health-wellness/workforce-health.md]`, `[astro/content/en/help/admin/challenges/admin-how-do-i-set-target-audience.md]` **Structural consequence:** the privacy section renders that screen rather than drawing an abstract data-flow diagram. This is deliberately different in kind from page 2's firewall diagram: page 2 shows the architecture, page 3 shows the moment of use. ### 1.4 The CAN / CANNOT table is quotable verbatim, including the sentence HR says to employees `[astro/content/en/help/admin/settings/admin-data-privacy-security.md]` gives HR this line verbatim: *"Your HR team sees whether you are participating and your challenge rankings, but we cannot see your weight, health assessment results, lab reports, or personal health data."* **Structural consequence:** the privacy section is a two-column ledger, not prose. It is the only place on the page with a strike-through treatment. ### 1.5 The dimension list is shorter than a buyer expects, and saying so is an asset Shipped dashboard-wide dimensions are exactly five: **Date range, Country / Location, Department, Age group, Gender**, served by a real endpoint returning `{countries, departments, genders, ageGroups}`. There is **no business unit dimension** (BU belongs to Vantage Pulse, a different product), **no tenure, no manager or reporting-hierarchy rollup, no saved cohorts, no job level, no site or building beyond Country and City.** `[research/insights-reports.md §4.1, §4.4]`, `[dash-design/docs/filters.md]` **Structural consequence and a correction to the task brief:** the suggested architecture named "business unit" as an existing dimension. It does not exist in Vantage Fit. The segmentation section names the five that exist, names the three extra dimensions available only to challenge and notification audiences (City, Language, Health Risk Code), and then plainly lists what is absent. That list is a credibility instrument, not an apology. ### 1.6 Exports are manual, and there is no scheduled or emailed report Every report has an Export CSV button and the file downloads to the browser. There is **no scheduled or recurring export, no emailed report delivery, no PDF dashboard export, and no BI or warehouse connector**. The help docs' own advice is "set a monthly reminder to export" and "archive exports monthly". `[astro/content/en/help/admin/reports/admin-how-do-i-export-reports.md]`, `[vfit-os/specs/product/09-admin-platform/admin-dashboard.md §08]` **Structural consequence:** section 7 exists and it states the limit out loud. A "board-ready output" section that implied scheduled delivery would fail the claims gate and would fail the buyer at implementation. ### 1.7 Two "participation" metrics exist in the same console and must never reconcile The Overview KPI **Participation Rate** is `round(active ÷ enrolled × 100)`, an app-usage measure. The Wellness Score's **Participation** component is binary daily engagement over a 7-day window. They do not reconcile. `[dash-design/docs/superpowers/specs/2026-07-18-wellness-live-ground-truth.md §4]`, `[research/insights-reports.md §2 Story A]` **Structural consequence:** because both strings appear inside my console, the console carries an explicit disambiguation note in pane 3. Most competitors would hide this. Printing it is the page's proof that this is measurement rather than decoration. ### 1.8 The per-task, per-week score breakdown is the most quotable analytic in the product Verbatim from the help docs: *"The score breakdown per user is one of the most useful tools in the dashboard. It shows exactly which tasks employees are completing and which they are skipping, invaluable for designing better future challenges."* `[astro/content/en/help/admin/reports/admin-what-reports-are-available.md]` (The source sentence contains an em-dash before "invaluable"; the page must not reproduce it. Use the trimmed quote given in the copy deck, section 3, S3.) **Structural consequence:** the Challenges pane's hero element is an expanded leaderboard row showing per-task and per-week decomposition, not a bar chart. It is the one thing on this page a competitor's screenshot will not have. ### 1.9 Conflicts I resolved, and the rule I applied | Conflict | Sources | Ruling used on this page | |---|---|---| | Wellness Score range 0 to 100 vs 0 to ~108 | help docs + code-verified admin spec vs `leagues-wellness-score.md` | **0 to 100.** Settled ruling G3. The console prints `74 / 100`. | | At a Glance metric count: 4 vs 5 | code-verified spec (4) vs production audit (adds Active Calories) | Render **4**: Avg Steps, Active Minutes, Mindful Minutes, Avg Sleep. Safe copy per `research/insights-reports.md §2 Story C`. | | Wellness Score component labels | help-doc names vs production strings | Ruling D3. **Prose uses Baseline, Participation, Activity, Adherence. The admin mock uses Health Baselines (20%), Participation (30%), Activity Levels (30%), Program Adherence (20%).** | | Health-risk insights granularity: org only vs org + department + country | code-verified `workforce-health.md` vs help doc | **Org level only.** Code-verified spec wins on what an admin can do. The health card carries an `Org level only` chip. | | Delta chips across the dashboard | card anatomy specs vs the production audit | **Only the four Overview KPI cards get delta chips.** All other delta chips are disabled backend-side; rendering them would over-claim. At a Glance keeps its sparkline, loses its delta pill. | | Overview KPI card set | code-verified (Enrolled Users, Active Users, Incentivization, Participation Rate) vs help doc (Active Users, Enrollment Rate, Completion Rate, Org Wellness Score) | **Code-verified four.** Settled ruling in `rewards.md` addendum E1. | | "Export respects your filters" | help doc says yes; production audit found the League CSV ignores inline filters and Wellness Score export caps at 10,000 rows | Keep the claim **generic**: "filter, then export". No headline claim about filters carrying through, no uncapped-export claim. | | Recommended Actions count: max 5 vs max 10 | code-verified vs production audit | Say **"a short, priority-ordered list"**. Render two rows in the mock, no count claim. | | Insights Hub | named in the code-verified page list; production audit found blank iframes and commented-out nav | **Do not claim, draw, or link.** Absent from the sidebar mock. | ### 1.10 Proof traps specific to this page - **Brazosport's 4/5 organisational mood score is unusable here.** Mood logs are explicitly on the admins-CANNOT-see list. Quoting a mood score on the page that promises HR never sees mood logs is a direct self-contradiction. Cut, do not soften. `[research/insights-reports.md §3.1]`, `[research/ia-claims-proof.md §3.2]` - **Every figure in `dash-design/vc-data.js` is seeded fiction** for a fake tenant ("Acme", "Priya Sharma", 68% participation, 1,120 assessed, 77% coverage). None may appear, including as mock filler. `[research/insights-reports.md §7.1]` - **Production dummy fixtures are real code paths serving fake data**: the Workforce Health Snapshot's 82% / 18% split and its Vitamin D 32% / Sleep Quality 28% / Stress Levels 22% deficiencies, the Industry Benchmark 74 constant, the challenge participation benchmark 70. None may appear. `[research/insights-reports.md §7.2]` - **The shipped Health Insights screen renders the string "HIPAA Compliant"** in a Compliance card. That string must not be reproduced in copy or in any mock on this page. The Compliance card is simply omitted from my console. `[research/insights-reports.md §3.6]` - **"Participation Report"** appears in production nav but not in the help-doc report table. Do not name it. KPI drill links read `View more →` only. --- ## 2. Strategy ### 2.1 The buyer Primary: **CHRO or VP HR** who has to present a wellness program to an executive committee, and the **HR Director** who will have to produce the numbers. Secondary reader with veto power: **legal / privacy counsel**, and **CFO** on the cost line. They arrive from a "prove it" search: corporate wellness dashboard, employee wellness ROI tracking. This is a conversion page, not a volume page. ### 2.2 The one thing this page must land > **You will leave your next leadership review with a number you can defend, and you will be able to say exactly where it came from and what it does not include.** Not "we have analytics". Not "insights that drive action". The promise is defensibility. ### 2.3 The defining objection and how the page answers it **Objection:** "Is this real measurement or a vanity dashboard, and can we defend it to legal and to the board?" Four answers, in this order: 1. **Real report names, real locations, real column sets.** The console renders `Reports → Employee Report`, `Challenges → Manage → Leaderboard`, the four code-verified KPI labels, the real filter chips, and the real empty-state select labels. Nothing invented. 2. **A number that decomposes.** The console's most distinctive element is an expanded leaderboard row showing per-task and per-week contribution that sums exactly to the row total. Vanity dashboards do not decompose. 3. **Named limits.** No business unit dimension. No scheduled reports. No warehouse connector. Org-level only for health risk. Two participation metrics that do not reconcile. Stating limits is the cheapest, strongest credibility available. 4. **A privacy boundary with a product string behind it.** Not a promise: a count-only cohort screen carrying the literal disclaimer, plus the verbatim CAN / CANNOT ledger. ### 2.4 Why this section order - The **console comes third, not first**, because a console with no question attached is wallpaper. Section 2 hands the reader three questions in their own language, and the console's three tabs answer them one to one. The tab labels are the answer keys to the question cards. That is the merge, expressed structurally. - **Segmentation follows the console** because a filter bar is meaningless until you have seen what it filters. - **Privacy sits in the upper middle, not the footer.** For a legal-sensitive purchase, burying the boundary reads as hiding it. It is also the natural pivot: everything before it is "what you can see", everything after is "what you do with it". - **Action, then exports** because the buyer's mental order is "what do I do about it" before "what do I hand upward". - **Proof late and small.** The page's credibility is built from product truth, not logos. The customer strip is three cards and one quote, and it exists mainly to demonstrate the labelling discipline in public. ### 2.5 What I deliberately left out, and why | Left out | Why | |---|---| | **Insights Hub** | Nav commented out in production, all five sub-pages blank iframes. Settled ruling: do not claim, draw, or link. | | **A blended "wellness index" hero number** | The four stories have different denominators and different entitlements. A composite would be exactly the vanity dashboard the buyer is worried about. | | **The Workforce Health Snapshot card** (Normal / Needs Attention bar, Top Deficiencies) | It is served from a Redis key with no writer and silently renders dummy fixtures in production on a cache miss. Drawing it would draw fiction. | | **The Compliance card from the Health Insights screen** | It ships the banned string "HIPAA Compliant". | | **Scheduled reports, emailed reports, PDF dashboard export, BI connector, cohort analysis, audit log** | None shipped. Two of them are roadmap. The page names the absence instead. | | **n = 5 cohort suppression, versioned consent, 30-day erasure SLA, minimum audience of 20** | All design intent, all parked. The shipped suppression story is count-only cohort targeting plus org-level-only health data. | | **Brazosport's 4/5 mood score** | Contradicts the page's own privacy claim. | | **Department-level health risk breakdown** | Code-verified spec says org level only. | | **A second product mock in the hero and a phone mock anywhere** | The subject is the admin console. A phone dilutes the page's one idea. The hero carries a compact `.dash` and one floating export chip, then the full console gets the width it needs. | | **A formats explorer, a leaderboard-integrity band, a "how teams form" section** | Owned by the challenge pages. This page links to them; it does not rebuild them. | | **The 20% HRA completion figure** | Real, documented, and a sales liability. Not an approved marketing stat. | ### 2.6 How this page is structurally different from its five siblings | Sibling | Its signature | This page | |---|---|---| | Wellness challenges (library) | Browse-and-filter catalogue of 21 challenges | No catalogue | | Health Risk Assessment | The data-in flow and a privacy firewall diagram | Privacy expressed as a **ledger plus a live screen**, never a flow diagram | | Step challenges / Multi-activity / Remote & hybrid / Virtual marathon | Format explorers, task explorers, run books | No formats, no tasks | | **Workforce health insights** | **One 1,100px admin console with three switchable views, real report names, real chart shapes, real axis labels** | This is the only page in the set with a console at this scale | No other page in the set may use `.console`. That is the point. --- ## 3. Section-by-section copy deck Voice rules that bind every string below: sentence case headings, terminal periods on H1 and H2, verb-led CTAs, no em-dashes, no banned words, numerals for measurable quantities, Oxford comma, US spelling in new copy, quotes verbatim. Ground alternation, in order: cream gradient, `#fff`, `--canvas`, `#fff`, `--canvas` with a dark inset, `#fff`, `--canvas`, `#f6f7f4`, dark, `#fff`, `--canvas`, dark. --- ### S1. Hero `
` **Kicker pill** (`.kicker` with lime dot): `Data out · Workforce health & rewards` **H1** (`` wraps the second clause for the coral gradient fill): `The participation number your board asks for, and the report behind it.` **Lead** (`.lead`): `Participation, challenge and activity analytics live in one admin console. Every number is aggregate by design, and every report leaves as a CSV you can hand to leadership.` **Buttons** (`.btn-row`): - Primary: `Book a demo` → `https://www.vantagefit.io/request-demo/` - Outline: `See pricing` → `https://www.vantagefit.io/pricing/` **Text link** below the buttons: `See what HR can and cannot see →` → `#privacy` **Hero note** (`.hero-note`, lime dot): `Aggregate by design. Admins never see HRA answers or lab results.` **Hero visual:** the `.dash` mock, described in section 4.1. **Logo band** (pinned to the bottom of the fold, `.logo-band`): - `.logos-label`: `Trusted by 100+ organizations worldwide` - `.logo-word` items, in this order: `Tata Motors` · `Wipro` · `IBS Software` · `Brazosport ISD` · `Landmark Group` · `POSOCO` --- ### S2. The three questions `
` ground `#fff` **Eyebrow:** `The merge` **H2:** `Three questions HR has to answer, in one place.` **Lead:** `These were three separate pages. They are three views of one console now, because they run on the same workforce, the same date range and the same filters.` **Three cards** (`.format-card` shape with a 74×44 `.format-glyph`, `.best-for` footer relabelled): | Card | H3 (the question) | One-line body | Footer label / value | |---|---|---|---| | 1 | `"Is anyone actually using it?"` | `Enrolled, active and participation rate, plus a named list of who has gone quiet.` | `Console view` / `Participation` | | 2 | `"Did the program land?"` | `Participation per challenge, three leaderboards, and the per task breakdown of what people skipped.` | `Console view` / `Challenges` | | 3 | `"Is behavior actually changing?"` | `Average steps, active minutes and sleep, league tiers, and the org wellness score.` | `Console view` / `Activity & health` | **Trailing note** (`.format-note`, `.8rem`, muted): `One workforce, one date range, three answers. Nothing has to be reconciled by hand afterwards.` --- ### S3. The console (page-defining section) `
` ground `--canvas` **Eyebrow:** `The console` **H2:** `One console, switched three ways.` **Lead:** `Real screens, real report names, real columns. Switch the view, keep the filters.` **The console mock:** full spec in section 4.2. Every string inside it is listed there. **Trailing quote block** under the console (a single `.problem-quote`-style card with a 4px coral left rule, not a section of its own): > `"The score breakdown per user is one of the most useful tools in the dashboard. It shows exactly which tasks employees are completing and which they are skipping."` `` attribution: `Vantage Fit Help Center, admin reports guide` (US spelling, and it matches the Resources menu label) **Trailing note** (`.format-note`): `Wellness Score, Wellness Leagues and Health Insights are included on annual contracts and set up with your account manager. Participation and challenge analytics ship with every plan.` --- ### S4. Segments `
` ground `#fff` **Eyebrow:** `Segments` **H2:** `Slice it the way your organization is actually shaped.` **Lead:** `Five dimensions apply across the console and across every report. The values come from the employee data you already load, so departments and countries match your own records.` **Dimension chips** (`.dim-row`, five `.dim-chip` items, each a label plus a one-line value string): | Chip label | Sub-line | |---|---| | `Date range` | `This Month, Last Quarter, Last 90 Days, This Year, Custom, Lifetime` | | `Country` | `From your employee data` | | `Department` | `From your employee data` | | `Age group` | `Bucketed ranges` | | `Gender` | `Male, female, other` | **Two "what a segment view changes" cards** (`.seg-case`, 2-up): | Card | H3 | Body (one line each, both documented) | |---|---|---| | 1 | `A department is lagging.` | `Filter the leaderboard by department, then send that department a targeted announcement.` (Do not name a "Community" section here: the console sidebar in 4.2.3 renders the group as `Engage`, and naming both on one page contradicts itself.) | | 2 | `A department is 80% Bronze.` | `That group may need its own challenge or a walking group, not another company-wide announcement.` | **Honest-limits note** (`.format-note`, and it should be visually a touch heavier than a normal trailing note, ink at 75% rather than muted): `Vantage Fit does not carry a business unit, tenure, job level or manager hierarchy dimension, and filters are applied ad hoc rather than saved as cohorts. Challenge and notification audiences add three more: City, Language and Health Risk Code.` --- ### S5. Privacy `
` ground `--canvas`, containing one dark `.fairband` inset. **Inside the fairband, left column:** **Eyebrow** (lime on dark): `Privacy` **H2** (`.fairband h2`, white): `HR sees who is participating. Never what the assessment said.` **Lead:** `The boundary is set in the product, not in a policy document.` **The ledger** (page-local `.ledger`, two sub-columns): Left sub-column header: `HR can see` - `Company and department enrollment rates` - `Active user percentages and last active date` - `Challenge participation, leaderboard rankings, team scores` - `Wellness scores, where the feature is enabled` Right sub-column header: `HR can never see` - `Individual health data: weight, BMI, body measurements` - `Health Risk Assessment answers and risk categories` - `Lab report results and biomarker values` - `Mood logs, food diary and sleep patterns` Right-column items render with a strike glyph, not strike-through on the text itself (strike-through on 8-word lines is hard to read at `.86rem`). **One-line precision note under the ledger** (`.ledger-note`): `One nuance worth stating out loud: where wellness scores are enabled, an admin sees a score derived from the assessment, never the assessment. The help docs are explicit that individual scores are for program design, not for decisions about specific employees.` **`.fair-fine`** (the verbatim line, in quotes, with attribution): `"Your HR team sees whether you are participating and your challenge rankings, but we cannot see your weight, health assessment results, lab reports, or personal health data."` `` attribution: `The sentence Vantage Fit gives HR to tell employees, from the admin privacy guide` **Inside the fairband, right column:** the count-only cohort mock, spec in section 4.3. --- ### S6. From insight to action `
` ground `#fff` **Eyebrow:** `Insight to action` **H2:** `The loop closes inside the same console.` **Lead:** `Every number on this page has a next step attached to it, and the next step runs against the same segment you were just looking at.` **Layout:** `.employee-cols` (`1.04fr .96fr`, gap 56px). Left: four `.join-point` rows. Right: the Recommended Actions mock, spec in section 4.4. **Left column, four `.join-point` rows** (each `` title plus one line): | # | Title (``) | Line | |---|---|---| | 1 | `Spot the gap` | `The Overview flags who has gone quiet. The Employee Report names them, with department and last active date.` | | 2 | `Target the exact segment` | `Audience rules enroll matching employees automatically. Any filter marks the challenge private, so nobody outside the group sees it.` | | 3 | `Pick the format that fixes the weak component` | `A Streak lifts adherence, a Race lifts activity, and a content-led Custom challenge lifts participation.` | | 4 | `Measure it the same way next quarter` | `Same reports, same denominators, so the before and after actually compare.` | **Chain row** under the two columns (three `.text-link` items on one line, this is where the data in, data out, action chain is made explicit): - `Where the data comes from: Health Risk Assessment →` → `/solutions/health-risk-assessment/` - `What you run against it: Wellness challenges →` → `/solutions/wellness-challenges/` - `What keeps people coming back: Wellness rewards program →` → `/solutions/wellness-rewards-program/` --- ### S7. What leaves the platform `
` ground `--canvas` **Eyebrow:** `Exports` **H2:** `Six reports, and an honest account of what they do not do.` **Lead:** `Filter first, then export. The CSV downloads straight to your browser with the columns you were looking at.` **Layout:** two columns, `1.05fr .95fr`, gap 48px. **Left column: the six reports** (`.report-list`, each row is a name plus its exact location string, and two rows carry an `Annual contract` chip): | Report name | Location string | Chip | |---|---|---| | `Employee Report` | `Reports → Employee Report` | | | `Transaction Report` | `Reports → Transaction Report` | | | `Redemption Report` | `Reports → Redemption Report` | | | `Challenge Leaderboard` | `Challenges → Manage → Leaderboard` | | | `League Report` | `Reports → League Report` | `Annual contract` | | `Wellness Score Report` | `Workforce Health → Employee report` | `Annual contract` | **Right column: four `.limit-row` items** (each `` title plus one line): | Title | Line | |---|---| | `Exports are manual` | `There is no scheduled report and no emailed delivery today. The documented practice is a monthly reminder and a monthly archive.` | | `Wait out the buffer` | `Export a Race challenge after the 3-day buffer so late-syncing wearable data is included.` | | `CSV, not a data warehouse` | `Reports leave as CSV files. There is no warehouse connector today.` | | `Reconcile two reports, not one` | `Cross-reference the Employee Report against the Transaction Report to find people who enrolled and then went quiet.` | **Trailing note** (`.format-note`): `Export rights are a role permission. Admins without them see the export button disabled.` --- ### S8. Proof `
` ground `#f6f7f4` **Eyebrow:** `Proof` **H2:** `What one program looked like when it was measured over time.` **Lead:** `Wipro ran three challenges between April and August 2025. These are the numbers the program left behind, each labelled with what it measured.` **Results grid, three `.result-card` items** (`repeat(3,1fr)`, gap 14px): | `.stat` | `

` (what it measured) | `.segment` | |---|---|---| | `3X` | `Participation increase, 163 to 550 active users, first challenge to third` | `Wipro · 3 challenges, Apr to Aug 2025`
`Active users, not enrolled` | | `46.53M` | `Cumulative steps logged across the three challenges` | `Wipro · 3 challenges, Apr to Aug 2025`
`Program total` | | `30+` | `Countries with participants in this program` | `Wipro · 3 challenges, Apr to Aug 2025`
`Participant footprint, not a customer footprint` | **`.proof-fine`** under the grid: - ``: `Results from a named customer program. Outcomes vary by workforce and program design.` - `.text-link`: `Read the Wipro story →` → `https://www.vantagefit.io/casestudy/wipro-global-wellbeing/` **One text-only quote band** (`.quote-band.text-only`) under the proof fine: > `"The app's analytics provided clear insights into participation levels and helped us recognize and celebrate achievements effectively."` `.quote-who`: `Shubham Sanghavi, Consultant, Avalon Consulting` --- ### S9. Security and compliance `

` dark gradient **Eyebrow** (lime): `Enterprise security & compliance` **H2:** `Built to survive a privacy review, not just a demo.` **Lead:** `Vantage Fit operates under HIPAA guidelines and is SOC 2 Type II. The reporting layer is aggregate by design, and the data never leaves the region you pick.` **Trust actions:** - Primary: `Book a demo` → `https://www.vantagefit.io/request-demo/` - Text link (lime variant): `Explore security & compliance →` → `https://www.vantagefit.io/features/security-and-compliance/` **Four `.trust-card` items** (2×2 via `.solutions-trust`): | Icon entity | H3 | Body | |---|---|---| | `◉` | `Aggregate by design` | `Admins see company and department level metrics. No admin screen and no export exposes one person's assessment answers, lab values, mood logs or food diary.` | | `☉` | `Your data stays in your region` | `Four isolated regional instances: India, US, EU and UAE. Chosen at signup, with no cross-region sharing.` | | `⇄` | `No personal data in the AI layer` | `Leadership Insights runs on aggregated signal buckets. No employee identifiers are sent to the insights service.` | | `✓` | `Employees hold the delete key` | `Employees delete their own lab reports, and delete their own account with OTP verification. An admin cannot do it on their behalf.` | **Trust plaque:** the typeset `.mark-strip`, three marks only. **No certification raster.** - `Operates under HIPAA guidelines` (the exact approved phrasing; do not paraphrase it to "Follows" or anything else) - `SOC 2 Type II` - `Secured regional data hosting` `.trust-support`: `Security documentation is available during evaluation.` --- ### S10. FAQ `
` ground `#fff` **Eyebrow:** `Questions` **H2:** `Questions HR asks before the first review.` Five `
`. First one carries `open`. Question text goes in `summary > h3`. **1. What are workforce health insights?** *(answer-first definitional item, mirrored in FAQPage schema)* `Workforce health insights are the aggregate reports an HR team uses to see whether a wellness program is working: how many employees enrolled and stayed active, how each challenge performed and which tasks people skipped, and how average activity and wellness scores move over time. In Vantage Fit they live in one admin console, and every figure is company or department level rather than individual health data.` **2. Can HR see an individual employee's health data?** `No. Admins see aggregate metrics, challenge participation and leaderboard rankings, plus employee reports that show registration status and last active date. They cannot see weight, BMI, Health Risk Assessment answers or risk categories, lab report values, mood logs, food diaries or sleep patterns. Where wellness scores are enabled, an admin sees a score derived from the assessment, never the assessment itself, and the product documentation states that individual scores are for program design rather than decisions about specific employees.` **3. Which analytics are included, and which need an annual contract?** `Participation analytics, challenge analytics and the six CSV reports ship with every plan. Org Wellness Score, Wellness Leagues and Health Insights are included on annual contracts, are set up by your account manager rather than a toggle, and need 2 to 4 weeks of data collection before the baseline reads reliably.` **4. Can reports be scheduled or emailed to leadership?** `Not today. Every report has an Export CSV button and the file downloads to your browser with the filters you applied. The documented practice is to set a monthly reminder, export, and archive. There is no scheduled delivery, no emailed report and no data warehouse connector.` **5. How do we know the activity behind the numbers is real?** `Steps count only from approved apps and devices, one primary device at a time so nothing is double counted, and GPS workouts are checked for unrealistic pace and for vehicle travel. Flagged activity does not reach the rankings, source tracking supports investigation, and challenge results stay provisional for 3 days after the end date so late-syncing wearable data lands before winners are picked.` --- ### S11. Related `