Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.vanticlab.com/llms.txt

Use this file to discover all available pages before exploring further.

The four dimensions

Your Friction Score combines four independently calculated dimensions of operational friction. Each captures a different way time leaks from structure.

Tool Fragmentation (TFI)

How spread across applications a given class of work is. Many apps touched for one workflow usually means more context recovery and coordination overhead. Lower: A tight toolset per workflow. Higher: Constant hopping across many apps.

Sequence Consistency (SCI)

How repeatable your workflow sequences are. Stable A → B → C patterns are easier to execute reliably than ad-hoc ordering every time. More friction: High variance run-to-run — a different order every time. Less friction: Predictable, repeatable sequences.

Context Switch Density (CSD)

How often you change focus in rapid succession. Rapid back-and-forth usually reads as coordination cost, interruption load, or cross-app copy-paste overhead. Lower: Meaningful dwell time per app. Higher: Rapid, frequent switching.

Workflow Duration Anomaly (WDA)

Sessions that run materially longer than your established baseline for comparable work. Duration spikes often flag blockage, rework, or handoffs that didn’t complete. Lower: Stable, predictable session durations. Higher: Frequent unexplained spikes.

Score bands

RangeBandWhat to do
0–29LowNo urgent action needed. Monitor for drift.
30–59ModerateReview the top one or two contributing patterns.
60–79HighPrioritise the highest-scoring dimension this week.
80–100CriticalTreat as urgent. The top pattern is costing material time.

The confidence gate

Vantic IQ does not publish the composite Friction Score (0–100) until the Pattern Engine has sufficient confidence. That means:
  • A minimum number of workflow instances observed — repetition, not a single unusual day
  • Enough dimensions crossing a reliability threshold independently
  • Signal quality high enough that a published headline score is not misleading
Note: before the full composite score is ready, you may see individual dimension observations in the conversational interface. Those are partial signals, not a partial Friction Score — the composite score is only published when all required dimensions reach confidence threshold. If the composite gate is not met, you do not get a headline Friction Score that implies the full model is ready — not a partial composite, not a “low” estimate. That is separate from early-window signals: you may still see Friction Pulse observations (single facts, no multi-pattern claim), and some accounts may show per-dimension readouts before the composite is final, as described in First use and Quickstart. The confidence gate applies to the full composite, not to every individual observation. Friction Score architecture and confidence gate

Why waiting is a feature

A score built from thin or non-representative data would be worse than no score. If your first week was unusually busy, unusually quiet, or atypical in any way, the Pattern Engine will wait for a clearer picture. This is by design.

Optional benchmarking

If sector benchmarking is enabled on your account, your Friction Score is displayed alongside a contextual range for your industry vertical. This is opt-in and can be disabled at any time. See Sector benchmarking.

The Diagnostic

How the Friction Score becomes a 30-day operational report.

Sector benchmarking

How your score is contextualised against patterns in businesses like yours.