What the Diagnostic Report is
The Diagnostic Report is the headline output of your 30-day Diagnostic window. It is a branded, exportable document that answers one question in quantified form: Where is your business losing time — and what is that costing you? A consulting-scale process audit answers the same question for 249–$349, with no configuration and no consultation required. The report is designed to be forwarded internally. The dollar figure leads. The temporal map makes the problem self-evident. The ROI calculation box makes the subscription decision clear.When your report is ready
Your Diagnostic Report becomes available at Day 25 of active signal detection — not at Day 30. If you have been active on your Mac throughout the window, you may export the report five days before the formal 30-day close. If you ask Vantic for the report before Day 25, the conversational interface responds:“Your Diagnostic report will be ready at Day 25 — you’re on Day [n].”Once ready, ask Vantic for the report in chat — say “my report”, “export report”, “show my diagnostic”, or similar — or trigger it from the menu bar. The report generates and opens in your default browser.
The Day 14 ROI preview surfaces an early estimate in the conversational interface if at least two High or Critical confidence patterns are present by that point. This is a conversational preview only — not the full report. The full eight-section report requires Day 25+ and is a separate export.
Eight sections in order
1. Header
VanticLab wordmark, your business name, date range of the detection window, and the generated date. Establishes the report as a formal, attributable document.2. ROI hero
The estimated recoverable time cost in AUD — large, leading. This is the number the report is built around. Immediately beneath, in small monospace text, the full assumption line:“Assumptions: avg. team rate $[X]/hr [provided by you | sector median estimate] · [n] staff · [n] hrs recoverable time identified · High and Critical confidence patterns only”
3. KPI row
Four headline metrics:| Metric | Description |
|---|---|
| Friction Score | Your overall composite score (0–100) |
| Peak friction window | The day and hour where friction concentrates most |
| Pattern count | Number of High or Critical confidence patterns detected |
| Detection days | Days of active signal in the evaluation window |
4. Temporal heatmap
A grid showing friction density by day of week (Monday–Sunday) and hour of day (8am–4pm). Darker cells indicate higher context-switching density in that slot. This is where you see when friction concentrates — not just that it exists. Legend: “Friction concentration — by day and hour · Darker = higher context-switching density”5. Top 3 patterns
The three highest-scoring friction patterns, ranked by score. Each shows:- Rank
- Friction Score and band label (Low / Moderate / High / Critical)
- Plain-language dimension name (not the dimension code — e.g. “Context switching” not “CSD”)
- One-sentence description of the specific workflow
6. Weekly trend
A four-week Friction Score trajectory showing how your score has moved over the detection window. If your score has increased across the window, the report notes: “Friction is not self-resolving.”7. ROI calculation box
The arithmetic displayed visibly:Recoverable hours × hourly rate = monthly recoverable costBelow the calculation, the full assumption block in small monospace:
Monthly recoverable cost vs Starter subscription monthly cost
“Estimate based on: [n] hrs recoverable time × $[X]/hr avg [provided / sector median] · [n]-day detection window ([start] – [end]) · Conservative estimate: 15 min/day friction overhead per pattern · High and Critical confidence patterns only · Actual time recovered depends on interventions implemented.”ROI scope: Only patterns with a Friction Score of 60 or above (High or Critical band) are included in the dollar figure. Moderate and Low patterns are excluded from the calculation. Hourly rate labelling: If you provided a rate during onboarding, the report labels it “provided by you.” If you left the field blank, the sector median for your vertical is used and labelled “sector median estimate” throughout.
8. Footer
VanticLab · SRVD NEAT PTY LTD · ACN 679 533 076 · s.attwood@vanticlab.com · vanticlab.comRight: DIAGNOSTIC REPORT · CONFIDENTIAL · [Business Name] · [Date] · Generated by Vantic IQ
Exporting as PDF
The report renders to a self-contained HTML file and opens in your default browser automatically on generation. To save as PDF:Let the report open in your browser
Vantic IQ generates the report and opens it in your default browser. Wait for it to fully render before proceeding.
What the report does not contain
- Internal engineering score values (0.0–1.0 scale)
- Raw application bundle IDs or hashed window title values
- Verbatim text from your conversational sessions
- Any dollar figure without the full assumption line visible
ROI framing — approved language
The following mandatory language is used throughout the report. It appears in your Diagnostic Report and is reproduced here for reference.| Context | Approved language |
|---|---|
| ROI hero subtext | ”Across [n] staff · based on workflow signal patterns detected over [n] days. This is estimated time lost to fragmented work — not billed hours, not system downtime.” |
| Summary framing | ”Based on the [team rate provided / sector median estimate] and the workflow patterns detected, approximately $X in recoverable time per month.” |
| Calculation framing | ”This is an estimate based on: [rate] × [recoverable hours] across [n] patterns at High or Critical confidence.” |
| Detection window note | ”Estimate based on [n]-day detection window. Actual time recovered depends on which interventions are implemented.” |
The Diagnostic
What the Diagnostic tier is, what it costs, and the conversion credit.
Reading your Diagnostic
Interpreting your Friction Score, dimension breakdown, and recommended next steps.
Friction Score
How the score is calculated and what the four bands mean.
Privacy Hub
What is stored, how to delete it, and the retention policy.