PureTechsHow we verify
How we verify
We only say what we actually know.
Every line in an IT check result carries an evidence label. Nothing is presented as fact because it sounded convincing — each finding says exactly how we came to know it.
The labels
Six labels. Each one means exactly one thing.
You told us.
Every finding in the IT check comes from one of your answers — and the result quotes that answer next to the finding. It never quietly becomes “verified”: it stays labelled as your report.
Where you see it: every finding in your IT check result.
You told us you were not sure.
When you answer “Not sure” about backups, the firewall, 2-step verification, staff exits or IT spend, we still raise a finding — if nobody knows, nobody is managing it. Backups, the firewall and 2-step verification count as a risk; staff exits and IT spend as needs attention. The finding says it in its own words, instead of claiming something you never said.
Where you see it: findings that came from a “Not sure” answer.
Calculated from your answers.
The Exposure Index and the category bars are arithmetic on your answers, and the arithmetic is printed below — so you can disagree with the formula rather than the conclusion.
Where you see it: the Exposure Index and the seven category bars on a result.
A band, not a number.
Used for recoverable staff hours. We show the range and the working, the percentages are stated as assumptions, and we never present it as a promise.
Where you see it: the hours estimate on the home page.
Not honestly checkable from a browser.
We leave it open rather than guessing and calling it a finding. Every result lists what the check cannot see, and any “Not sure” answer that did not raise a finding is listed as an open question.
Where you see it: “What this check cannot see” on every result, and “Open questions” whenever you were unsure.
Checked by an engineer, on your network.
Only an engineer working on your actual systems can confirm or close a finding. That happens in the engineer review — never in the browser.
Where you see it: nowhere on this website. This label only exists in the review an engineer does with you.
The arithmetic
How the Exposure Index is calculated.
- Sixteen questions. Thirteen of them can raise a finding; three — what has stopped in the last year, which IT costs you pay for, and whether monthly spend is known — are context only: they are not scored, and they are included when you send your result to an engineer.
- Fourteen rules. Each one reads a single answer, and each finding it raises quotes that answer.
- A risk finding adds 16 points. A needs attention finding adds 9.
- The Exposure Index is the total, capped at 96. Bands: 0–20 low, 21–45 moderate, 46 and above high.
- Each category bar is the points found in that area divided by the most that area can score: continuity 25, email & cloud 16, backup 16, network edge 16, access control 25, managed IT 18, licensing & cost 36.
- The five-statement teaser on the home page uses fixed weights (22, 20, 18, 20 and 20) with the same bands and the same cap of 96, and is labelled indicative only.
Stated plainly
What this website does not do.
- It does not scan your network or your devices.
- It does not look up your domain, DNS or email records.
- It does not test your email, firewall or backups.
- It measures nothing on your systems — so nothing here is labelled “measured”.
- It does not store your answers or send them anywhere.
- No fake score, no fake loading, no fake urgency.
The only urgency that is real
Configurations keep changing, so every result is a dated snapshot. An older result should be re-checked before it is relied on.