How the Free Business Scan calculates operational risk.
A transparent account of the questions, score calculation, prioritization, recommendations, privacy boundaries and limitations behind Plynt RADAR.
Deterministic, explainable and private by design.
- 25 questions
- Five questions for each operational dimension.
- Five dimensions
- Money, time, margin, focus and execution.
- 0–100 risk score
- A higher number means a larger indicated operational leak.
- Browser-only answers
- Answers and scores are calculated and stored on the user's device.
Five connected sources of operational leakage.
- 01
Money
Cash visibility, receivables, financial control and confidence in current numbers.
- 02
Time
Time capture, capacity visibility, workload balance and the cost of unrecorded effort.
- 03
Margin
Project cost awareness, pricing discipline and the ability to see profitability before work ends.
- 04
Focus
Priority clarity, interruption load, ownership and the amount of work competing for attention.
- 05
Execution
Request intake, handoffs, follow-through and the reliability of work reaching completion.
Every score can be reproduced from the answers.
Each statement uses a five-point response. Strong agreement represents no indicated leak and maps to 0; strong disagreement represents the highest indicated leak and maps to 4.
1. Dimension score
Add the five 0–4 values in one dimension, divide by 20, multiply by 100, then round to the nearest whole number.
2. Overall score
Calculate all five dimension scores, take their arithmetic mean, then round to the nearest whole number.
3. Priority order
Sort dimensions from highest score to lowest. Ties use a fixed order: money, time, margin, focus, then execution.
4. Complete answers only
A final report is generated only when all 25 questions have an answer. No missing answer is silently imputed.
dimension score = round((sum of five answer values ÷ 20) × 100)overall score = round(mean of the five dimension scores)Four fixed score bands.
| Score | Band | Meaning |
|---|---|---|
| 0–24 | Steady | Few issues indicated; protect the working controls and review periodically. |
| 25–49 | Watch | Some repeatable friction is visible and deserves targeted attention. |
| 50–74 | Notable | Material operational leakage is indicated; prioritize corrective work. |
| 75–100 | Severe | Persistent, high-impact leakage is indicated; begin with the clearest control gaps. |
Recommendations follow the score, not a generative guess.
The report selects the three highest-risk dimensions. It shows the answered statements that contributed most strongly, then selects prewritten actions attached to those dimensions. Actions are grouped into three fixed phases: this week, the next two weeks and by day 30, with no more than four actions in each phase.
- The same complete answer set always produces the same scores, ranking and plan.
- RADAR does not send answers to an AI model and does not generate recommendations from free-form prompts.
- A low score is reported as a strength only when a dimension score is below 40.
Assessment content stays in the browser.
- Answers, dimension scores and the overall score are stored in localStorage on the user's device so an unfinished scan can resume.
- Deleting assessment data removes the stored answers and progress from that browser.
- Plynt's identifier-free analytics may count lifecycle events such as scan start, completion or report view, unless Global Privacy Control or Do Not Track is enabled.
- Analytics records contain no answer, score, cookie, visitor ID, IP field, user-agent field or free-form assessment content.
What the score does not claim.
- • RADAR is a structured self-assessment, so its output depends on the completeness and honesty of the responses.
- • The 0–100 score is an internal diagnostic scale, not a percentile and not a benchmark against other companies.
- • The assessment does not prove causation, predict financial results or replace accounting, legal, security or management advice.
- • Recommendations are prioritization prompts. Teams should validate them against their actual operations, constraints and evidence.
- • No customer result, industry average or performance claim is inferred from anonymous scan events.
Versioning and review.
This page documents RADAR methodology version 1.0. Material changes to questions, formulas, thresholds, ranking or recommendation logic require a new review date and an updated sitemap last-modified value. Plynt publishes the method at organization level; no individual reviewer is named until a verified reviewer has approved the methodology.
The production implementation is the controlling source for calculation behavior.
See the method applied to your own operations.
Complete the 25 questions privately, inspect the evidence behind each finding and decide which actions fit your business.