Definition
The Distribution Safety Score — often shortened to just the "Safety Score" — is Dividend Vision's own 0–100 estimate of how safe a fund's distribution looks going forward. Higher is safer. It appears on every covered fund's ticker page as a gauge with a color band, and the same number shows up as a sortable column in the screener, watchlist, holdings table, compare pages, and the portfolio risk view.
It is deliberately not an AI model or a black box. It is a transparent, rules-based penalty engine: every fund starts at 100, points are deducted for specific, named red flags — a falling or recently-cut payout, price/NAV erosion, deep drawdowns, leverage, crypto exposure, a short track record, and so on — and the result is clamped to 0–100. Because every deduction is a labeled factor, the ticker-page card can always show a plain-language "What's pulling it down" breakdown next to the number. No hidden weights shift around behind the scenes, and the same fund scores identically on every surface because every surface runs the exact same engine on the exact same daily data.
One thing the score is emphatically not: a yield penalty. A high distribution rate on its own is not treated as a red flag. Many income funds yield high by design, and the score judges them on their payout trend, price behavior, and track record — not their headline rate. Only genuinely extreme yields, far above what a fund's structure normally supports, draw a deduction.
Why It Matters
Income investors face an asymmetric problem: the headline yield is the easiest number to see and the least informative one. A 12% yield tells you nothing about whether the payout is growing or being quietly cut, whether the share price is eroding underneath it, or whether the fund has existed long enough to prove anything at all. Chasing the biggest number is exactly how investors walk into a yield trap.
The Safety Score compresses the checks a careful analyst would actually run — payout trend, past cuts, price erosion, drawdown, beta, leverage, coverage, track record, cost — into one comparable number with a visible breakdown. That does three useful things:
- It surfaces problems the yield hides. A fund can pay a flawless-looking 11% while its distribution has been trimmed twice and its NAV has ground down 20% — the score flags all three even though the headline yield still looks generous. See why high yield isn't high income.
- It sets expectations for young funds. New funds simply don't have the history to prove a durable payout, so instead of projecting confidence the score caps them and labels them *Unproven* — a "no verdict yet," not a "risky."
- It makes portfolios comparable. Because every fund is scored by the same engine, you can sort a screener by safety, spot the lowest-scored holding in a portfolio, or compare two candidates side by side without re-reading ten fund pages.
What it is not: the score is an educational estimate, not investment advice, a prediction, or a credit rating. A high score isn't a promise the distribution holds, and a low one isn't a prediction of a cut.
How It's Calculated
The mechanics are simple to state: start at 100, deduct points for each red flag present, clamp the result to 0–100, and round. Every deduction has a fixed maximum, so no single signal can dominate beyond its cap. The factors, what triggers them, and their maximum deductions:
| Factor | What triggers it | Max deduction |
|---|---|---|
| Falling payout | Distribution down year-over-year across the last 12 months | 35 |
| Past dividend cut | A deeper payout cut with its trough 1–5 years ago (never double-charged with the row above) | 28 |
| Price / NAV erosion | Share price down over the trailing 12 months | 25 |
| Volatile price | Peak-to-trough drawdown deeper than ~20% within the year | 12 |
| High volatility | Beta above ~1.3 vs. the broad market | 6 |
| Extreme yield | Yield above the structure's soft cap — ~8% for plain funds, ~12% for BDCs/CEFs/MLPs/REITs, ~40% for option-income funds | 15 |
| Leverage & concentration | Leveraged strategy (+8) and/or a single-underlying fund (+4) | 12 |
| Crypto-linked volatility | Bitcoin/crypto exposure — a structural forward risk | 12 |
| Too new to score | Not enough actual payouts banked yet (see the track-record gate below) | 10 + score capped at 50 |
| Infrequent payout | Annual or semi-annual cadence — a cut can stay hidden for up to 12 months | 4 |
| Thin coverage (BDCs only) | Paying out more than ~75/90/100% of earnings | 10 |
| Cost / size | Very small AUM and/or a high expense ratio | 8 |
A few design choices in that table deserve emphasis:
High yield per se is not penalized. The "extreme yield" caps are structure-specific because context matters: 9% is unusual for a plain equity ETF but routine for a BDC or CEF, and a covered-call fund can sustainably distribute far more than either. Only yields beyond ~40% for option-income funds, ~12% for BDCs/CEFs/MLPs/REITs, or ~8% for everything else draw the deduction — the territory where chronic NAV decay becomes the norm. Likewise, *being* an option-income fund is not treated as a defect: the strategy itself carries only a token deduction, because its real risks (an eroding NAV, a cut payout) are already measured directly by the erosion and payout-trend factors.
Price-behavior factors share a combined cap. Erosion, drawdown, and beta all describe how the fund's price moved, so their combined deduction is capped (at 35 points, equal to the payout-trend maximum) to stop one bad market move from being charged three ways at once. The lowest scores are reserved for funds failing on multiple *independent* dimensions. Crypto exposure deliberately sits outside that cap: it's a structural forward risk that holds even after a calm year, and backtesting showed crypto-linked funds cut far more often than same-scored plain funds.
The track-record gate counts payouts, not birthdays. What proves a distribution durable is the *number of payouts observed*: roughly eight distributions across at least six months of history. A monthly payer clears that in about eight months; a quarterly payer needs about two years; a weekly payer even less. A fund that hasn't cleared the gate takes a "Too new to score" deduction and has its score capped at 50, with the band relabeled Unproven — shown in a neutral slate color rather than red, because it means "no verdict yet," not "dangerous." Proven-but-young option-income funds face an extra confidence ceiling: they can't read *Safe* (80+) until about two years of record, and can't score above 90 until about five — not a strategy penalty, but a requirement that a volatility-premium payout prove itself across more than one market regime.
Missing data caps, rather than penalizes. A missing input applies no deduction — the score never punishes a fund for a data gap. But a record missing two or more of the three core signals (payout trend, 12-month price change, track record) is flagged *Low confidence* and capped at 79, so a sparse record can never read as Safe.
The final number maps to bands: 80+ Safe, 60–79 Generally safe, 40–59 Caution, 20–39 Elevated risk, below 20 High risk — plus the special Unproven band for funds that haven't cleared the track-record gate.
What isn't scored at all: money-market funds (a pinned $1 NAV has no safety question), funds with no recurring distribution (a lone special dividend isn't an income stream), and inverse/bear daily trading products, whose distributions are incidental collateral interest. Short-strategy *income* funds that sell option premium as the product are still scored.
When it updates: the score is recomputed with the daily data build, and one engine produces the number for every surface — the ticker card, screener, compare pages, watchlist, holdings, portfolio risk view, and Ask DV chat all read the same daily inputs, so a fund never shows two different scores. It is not a live intraday metric.
Example
Here is how the ticker-page breakdown reads for an illustrative fund — call it a one-year-old, single-stock option-income ETF yielding 45%, whose payout has drifted down 20% year-over-year while its share price fell 16% with a 35% mid-year drawdown. Every figure is illustrative, but the arithmetic mirrors the real engine:
Distribution Safety Score: 48 / 100 — Unproven
What's pulling it down:
Falling payout -14.0 distribution -20% over the past year
Price erosion -12.8 share price -16% over 12 months
Too new to score -10.0 only ~12 distributions so far
Volatile price -7.5 fell 35% peak-to-trough within 12 months
Leverage & concentration -4.0 tied to a single underlying asset
Very high yield -2.0 45% yield vs. the ~40% option-income cap
100 - 52.3 penalty ≈ 48 → under the Unproven cap of 50 → band: Unproven
Notice what did *not* hurt it: the 45% yield cost only 2 points (it barely exceeds the option-income cap — the yield level is mostly tolerated), and being a covered-call fund cost essentially nothing. The damage came from the payout actually falling, the price actually eroding, and the fund being too young to have proven anything — the things that distinguish a real distribution problem from a scary-looking headline rate.
At the other end of the spectrum, a large, decade-old dividend fund with a growing payout, a stable price, modest yield, and a low expense ratio — the SCHD profile — accumulates almost no deductions and reads in the high 90s. A proven option-income fund like SPYI or QQQI is judged the same way — payout trend, NAV behavior, track record — with the young-fund ceiling lifting as its history lengthens.
Does It Work?
The score has been backtested against history rather than just asserted. The backtest reconstructs each fund's inputs as they stood on monthly evaluation dates from mid-2022 through mid-2025, scores them with the exact engine that ships today, and then looks at what actually happened over the following 12 months — across 774 funds and more than 21,000 fund-month observations. The share of funds that went on to cut their distribution by 15% or more within a year, by band:
| Band | Cut ≥15% within 12 months | Cut ≥30% within 12 months |
|---|---|---|
| 80+ Safe | 6.7% | 3.0% |
| 60–79 Generally safe | 15.1% | 8.3% |
| 40–59 Caution | 22.8% | 16.5% |
| 20–39 Elevated risk | 31.2% | 19.9% |
| 0–19 High risk | 49.3% | 43.5% |
Cut rates rise strictly band by band: a High-risk fund was roughly 7x more likely to cut by 15%+ within a year than a Safe one, and roughly 14x more likely to cut deeply. Two of the engine's thresholds — the crypto factor stacking outside the market cap, and the young option-income ceilings — were recalibrated directly against this evidence.
That's the honest case *for* the score. The honest case for reading it carefully:
- These are cohort base rates, not per-fund predictions. "Safe" means the band historically cut at a 6.7% rate — it does not mean *this* fund has a 6.7% chance, and it certainly doesn't mean zero. Some Safe funds cut; some High-risk funds never do.
- The inputs are trailing, so the score lags regime changes. There are no forward-looking inputs (no options-overwrite math, credit quality, or rate sensitivity). After a long calm market, scores drift up — and in the backtest, Safe-band funds evaluated in 2022 went on to suffer 12-month price crashes at several times the rate of those evaluated in 2023–2025, because a bear market arrived through perfectly calm trailing signals.
- The weights are hand-tuned heuristics. The band-level results validate the overall calibration, and two thresholds were empirically recalibrated, but most individual multipliers and cutoffs are sensible rules, not fitted parameters. It is a rules-based estimate — never a "model" output or a probability.
- Missing data applies no penalty, so a fund with a sparse record can read more reassuring than its true risk. The confidence chip and the Low-confidence cap exist precisely to flag that case, but the number itself can still run optimistic.
- Coverage is checked for BDCs only. Distribution coverage is the best forward-looking cut signal for BDCs, but an earnings-based ratio is misleading for CEFs and plain ETFs (whose payouts routinely include return of capital and capital gains), so the score may catch a quietly under-earning ETF only later, through NAV erosion or the cut itself.
Common Mistakes
- Treating the score as a guarantee. An 85 is a favorable trailing profile, not a promise — 6.7% of Safe-band observations in the backtest still cut within a year. Use it to prioritize attention, not to replace it.
- Comparing scores across structures without context. A 75 on a two-year-old option-income fund (sitting under its confidence ceiling) and a 75 on a decade-old plain dividend ETF got there differently. Read the factor breakdown, not just the number.
- Reading "Unproven" as "risky." The Unproven cap is a statement about *evidence*, not danger — the fund hasn't banked enough payouts to judge. Some Unproven funds will mature into 90s; the score just refuses to guess which.
- Using it as a standalone sell signal. A score that drops is a prompt to look at *why* — one factor (a mid-year drawdown that later recovers, say) can move the number without changing the fund's payout economics. Check the breakdown, the payout history, and the NAV trend before acting.
- Assuming a high yield lowered the score. It almost never does — yield only draws a deduction above the structure-specific extreme-yield caps. If a high-yielder scores low, the breakdown will show the real reasons: a falling payout, erosion, or a thin record.
FAQ
What is a good Distribution Safety Score?
80 and above reads Safe, and 60–79 Generally safe — in backtesting those bands went on to cut by 15%+ within a year at roughly 7% and 15% rates respectively, versus ~49% for the High-risk band. But "good" is contextual: a proven option-income fund under 3 years old tops out at 84 by design, so a 79 there can be a strong result. Always read the number next to its band and factor breakdown.
Does a high yield lower the score?
On its own, no — that is a deliberate design choice. Yield only draws a deduction above a structure-specific extreme threshold: roughly 8% for plain funds, 12% for BDCs, CEFs, MLPs and REITs, and 40% for option-income funds. Below those caps, a fund is judged on its payout trend, price behavior, track record, and cost — not its headline rate.
Why is my new fund capped at 50?
It hasn't banked enough payouts to prove its distribution durable — the gate is roughly eight distributions over at least six months, so a monthly payer clears it in under a year while a quarterly payer needs about two. Until then the score is capped at 50 and labeled Unproven, which means "not enough evidence yet," not "unsafe." The cap lifts automatically as real payouts accumulate.
How often does the score update?
It is recomputed with the daily data build, and every surface — ticker page, screener, compare, watchlist, holdings, portfolio analysis, Ask DV — reads the same engine and the same inputs, so a fund shows one consistent score everywhere. It is not a live intraday number, and it does not react to today's price move until the next build.
Can a fund with a Safe score still cut its distribution?
Yes. In the 21,000-observation backtest, 6.7% of Safe-band fund-months were followed by a 15%+ cut within a year. The bands are historical base rates, not per-fund guarantees — and because the inputs are trailing, a sharp market regime change can hit before the score reflects it. Treat Safe as "few red flags visible," never "nothing can go wrong."
Where do I see the Safety Score?
The flagship view is the gauge card on each fund's ticker page (for example QQQI), which includes the full "What's pulling it down" factor breakdown. It's also a sortable column and filter in the screener, a row on compare pages, a column in your watchlist and holdings tables, and a band-by-band breakdown in the portfolio risk view. Money-market funds, non-payers, and inverse trading products show no score by design.