How the TIME Score Works
The TIME Score measures one thing: how much human time a system liberates or destroys. It is a number from 0 to 100, calculated from four components, grounded in a signal-noise framework adapted from information theory. Every score on this site traces back to the formulas below.
The Core Idea
Time is value. Not a metaphor — a measurement. When a tool saves you three hours of work, those three hours are the value. When a platform holds your attention for two hours without producing anything you can point to afterward, those two hours are the cost.
The TIME Standard makes this visible. For every system we score, we ask: how many hours of human time does it return? How much of that time produces real change — output created, knowledge gained, conditions improved? How much is wasted on redundancy, friction, drift, and dissipation? What's the net direction?
The Four Components
QATU — Quality-Adjusted Time Units (35% of score)
How much human time the system liberates, weighted by utility (is the saved time high-value or low-value?) and distribution (does everyone benefit or just a few?). One QATU equals one hour of human time returned at maximum utility and perfect distribution. A medical AI saving emergency triage time earns more QATUs per hour than an entertainment app saving content browsing time.
TSNR — Temporal Signal-to-Noise Ratio (25% of score)
Of all the time this system touches, how much produces real state change versus how much is wasted? Adapted from Claude Shannon's signal-to-noise ratio in information theory — the same mathematical structure used in electrical engineering, MRI imaging, and quantitative finance, applied to time.
TSNR greater than 1 means the system produces more signal than noise. Less than 1 means more noise than signal. TikTok's TSNR is 0.18 — for every hour of signal, it produces 5.5 hours of noise. Wikipedia's TSNR is 32 — for every hour of noise, it produces 32 hours of signal.
CPI-T — Consumption-Productivity Index (25% of score)
The net direction. After everything is accounted for, is this system giving you time or taking it? Ranges from −1 (pure time destroyer) to +1 (pure time creator). Zoom scores exactly 0.000 — it saves exactly as much time as it consumes.
TLR — Time Leverage Ratio (15% of score)
How much human time is returned per unit of computational time consumed. A system that uses enormous GPU resources to save a small amount of human time scores lower than one that uses minimal compute to save significant human time. This component naturally decays in weight as compute becomes cheaper.
Signal and Noise
The framework classifies every unit of time expenditure as either signal or noise.
Signal: The State Change Test
Time is signal if and only if it produces a measurable state change:
ΔO (Delta Output) — a tangible artefact was produced or a task reached completion. Code was written. A document was finished. A transaction was processed.
ΔK (Delta Knowledge) — information was acquired, synthesised, or transferred that did not previously exist in the recipient. Someone learned something. A decision was informed by new data.
ΔS (Delta State) — the condition of a system, person, or process moved from one state to a different, intended state. A patient was treated. A relationship was maintained. A mood was regulated.
Noise: The Four Components
Time is noise if nothing changed and resources were consumed:
R (Redundancy) — repeated processing without incremental value. Regenerating the same AI output. Re-reading the same Slack thread. Retrying an identical search.
F (Friction) — unnecessary intermediation, latency, or poor design. Loading screens. Authentication loops. Fee calculations. Format conversions.
D (Drift) — movement away from an intended objective. Content rabbit holes. Algorithmic recommendations that pull you off-task. Scope creep without value.
Dp (Dissipation) — energy consumed with zero output. GPU cycles on discarded inference. Human attention on content that leaves no memory, skill, or changed state. Browsing without choosing.
Grading Scale
50–59 C | 40–49 D | 25–39 F | 0–24 F-
Data and Sources
All scores on this site are currently marked ESTIMATED, meaning they are calculated from publicly available data: published monthly active user counts, published session duration statistics, published benchmark results, pricing pages, app store analytics, and industry research reports. Specific sources for key inputs include Sensor Tower, SimilarWeb, company earnings reports, and official platform transparency disclosures.
We distinguish three data confidence levels:
OBSERVED — calculated from direct telemetry, API logs, or first-party operational data. The gold standard. Available when companies share data directly or when we instrument systems ourselves.
ESTIMATED — calculated from public data, published benchmarks, and industry norms. The current basis for all scores. Assumptions are stated and defensible but not verified against internal data.
PROJECTED — calculated from stated capabilities, roadmaps, or theoretical performance. Used only for pre-release or early-stage systems.
We welcome corrections. If you have better data for any scored entity, contact us. We will update scores when provided with evidence that materially changes any input assumption.
Frequently Asked Questions
The TIME Standard
The full mathematical framework, intellectual lineage, and extended methodology are documented in the TIME Standard paper by Ash Koosha (2025). The paper covers dynamic baselines, temporal deflation, time-energy entanglement, currency implications, and the complete derivation of every formula used on this site.
Read the TIME Standard ↗Contact
Corrections, data submissions, scoring requests, and press inquiries:
ashkoosha@gmail.com