How We Project Distributions

Definition

Distribution projections are the forward-looking numbers behind your portfolio's Yearly Income, the projected dividends chart, the income calendar, and the long-range forecast: Dividend Vision's estimate of the cash each holding will pay over the months ahead, per share, on its actual payment schedule.

Every projected dollar on the site sits on a ladder of certainty, and the charts shade each rung differently so you always know which kind of number you're looking at:

1. Received — cash that has already landed, from your broker's transaction history or the fund's realized per-share record. Not an estimate at all.
2. Announced — a payment the issuer has formally declared: a known per-share amount with a stated pay date that hasn't arrived yet. Nearly certain; only the settlement is pending. We capture many of these from issuer announcements within hours of posting.
3. Estimated — everything beyond the declared horizon, projected from the fund's payout cadence and its recent distribution record.

Most of this article is about rung 3, because that's where methodology actually matters — and where we do considerably more than the industry default of "take the last payment and multiply by 12."

Why It Matters

Here is the uncomfortable truth about how forward income is usually calculated, across trackers, brokers, and even fund sponsors themselves: the most recent payment is annualized by the payment frequency, and that's the whole model. Last payment × 12 for monthly payers, × 52 for weekly. It's the industry-standard "indicated rate," and for a steady quarterly payer it works fine.

For the modern generation of variable-distribution funds, it breaks badly:

• Weekly option-income ETFs routinely swing their payout ±40% week to week. Annualizing one fat week overstates the next twelve months by thousands of dollars on a modest position; annualizing one thin week understates it just as hard. The number whipsaws every week and tells you very little.
• Year-end specials masquerade as run-rate. A fund that pays a $0.15 quarterly and one $6.72 year-end capital-gains distribution briefly "yields" 181% to any tool that annualizes blindly. Real tools published exactly that.
• The workarounds are avoidance, not solutions. One major broker simply excludes weekly payers from its income estimates entirely. Fund sponsors publish the same latest-payment-annualized rate with a disclaimer that it "does not imply future distributions."

We think income investors deserve better than a disclaimer. Projections drive real decisions — how much you can withdraw, when a portfolio covers your expenses, whether a holding is pulling its weight — so the estimate underneath them should be built like it matters.

How It's Calculated

Our projection engine works in two independent layers: when each payment lands, and how much it pays. Both layers are recomputed with the daily data build, and every surface — the dividends page, the dashboard, the income calendar, widgets, the forecast — reads the same engine, so no two pages ever disagree about your income.

The schedule layer

• Each holding's payment dates are projected forward from its last declared ex-dividend and payment dates, stepped by its real cadence — daily, twice-weekly, weekly, semi-monthly, monthly, quarterly, and everything between.
• Distributions settle on market days. A weekly payer whose cadence lands on a holiday rolls forward the way it does in real life, without letting the schedule drift; daily payers step only through actual market sessions (about 252 a year, not 365 — a calendar-day walk would overstate a daily payer's income by roughly 45%).
• Dates are marked Exact when they come from a declared ex/pay date on file and Estimated when they're cadence projections, so the calendar is honest about which is which.

The amount layer

For each future payment, the engine takes the best number available, in strict order:

1. The declared amount, when the issuer has announced it. Declared beats estimated, always.
2. Your selected estimate basis (next section) for everything past the declared horizon.

Before any amount is projected, it has to survive a battery of sanity checks that most tools simply don't run:

• One-off specials are detected and refused. A payment more than 3× the median of its own two-year neighborhood is classified as a special — a year-end capital-gains distribution, a one-time supplemental — and is never annualized into your forward income. The payment itself still shows (it's real money); only projecting it forward is blocked. See Section 19(a) notices for how these distributions are disclosed.
• Bunched supplementals are caught by spacing. An extra payment that lands days after a regular one — ordinary in amount, wrong in timing — is recognized by its gap, not its size, so it can't distort the run-rate.
• Stale payers don't project. A fund whose last distribution is far overdue for its cadence (a suspended dividend the data never cleared) is not annualized against today's price — that's how other tools end up showing 300% "yields" on funds that stopped paying years ago.
• Split-adjusted history. All per-share amounts are restated to the current share count, so a reverse split can't fake a payout jump.
• Implausible values are rejected. A recorded "payment" larger than the share price is bad data, not a 8,000% yield, and is discarded.

The estimate basis: DV Income Vision™ or Industry Standard

This is the part nobody else offers: past the declared horizon, you choose what gets annualized, with one setting that applies consistently across every projection surface. DV Income Vision™ is Dividend Vision's forward-income projection — see the income ahead — and it pairs with the Distribution Safety Score™: the score judges how sustainable the income may be; DV Income Vision projects how much you may receive, and when. On the portfolio dividends page, look for the *Estimate basis* control above the chart.

• DV Income Vision *(default)* — the right model per holding, chosen from the fund's own payment history and validated by backtest against the realized payouts:
• Steady payers — funds whose recent regular payouts barely vary — project their most recent payment. For a stable payout there is no spike to average away, and the latest payment picks up a dividend raise a full period sooner than any average.
• Variable payers — everything else — are projected from an *average* of their recent regular payments, so one fat or thin week doesn't set the whole year.

The averaging window is sized to the fund's cadence (about the last 4 weekly, 3 monthly, or 2 quarterly payments) and measured from the *observed spacing* of the payments themselves — so a mislabeled frequency can't skew it, a fund that just switched from monthly to weekly averages only its weekly-era history, and one-off specials are already filtered out. One setting, the right model per holding — chosen by measurement, not by vibes. And "chosen by measurement" cuts both ways: we also built a rate-space projection (the fund's average distribution rate × today's price) for percent-of-NAV funds, backtested it against their realized payouts — and retired it when it lost to these simpler models even on the funds it was designed for.

• Industry Standard — the most recent regular payment, annualized. The indicated rate that brokers and fund sponsors publish: most responsive, fine for steady payers, and the view to use when you want to reconcile our numbers against another tool's. Its weakness is exactly the whipsaw described above — one fat or thin week from a variable payer sets the whole year.

The right basis depends on what you're asking. For a SCHD-style dividend grower the two barely differ. For a variable weekly payer like ULTY they can differ meaningfully — and that spread is itself information: it measures how volatile the fund's payout really is.

Example

Suppose a weekly option-income ETF has paid these last five regular distributions per share: $0.10, $0.11, $0.09, $0.10 — and then a big week, $0.25. You hold 1,000 shares at a $10 share price.

• Industry Standard basis: $0.25 × 52 = $13,000/yr projected — a 130% implied rate, driven entirely by one week.
• DV Income Vision: this fund's payouts clearly vary, so it projects the average of the last four regular payments (($0.25 + $0.10 + $0.09 + $0.11) ÷ 4 = $0.1375) × 52 = $7,150/yr — the big week still counts, but as one week out of four, not as the new permanent run-rate. If its payouts were steady in dollars instead, it would simply project the latest payment, exactly like the Industry Standard view — for a stable payout that's the measurably better model.

For scale, the trailing twelve months actually paid — say $5.20/share, or $5,200 on this position — is the rearview number your TTM Yield card reports; the projection is the windshield.

Now add a wrinkle: in December the same fund pays a $0.90 year-end capital-gains special. Every naive tracker's projection triples overnight. Ours doesn't move: the special is more than 3× its neighborhood median, so it's flagged, displayed as real received cash — and excluded from every forward number on both bases.

Common Mistakes

• Reading a projection as a promise. Every estimated figure assumes distributions continue at the basis rate. Funds cut, raise, and suspend; a projection is a structured estimate, not a forecast with a warranty. The Likely range under the Yearly Income card makes the width honest — computed from how much each fund's recent payouts actually vary, half the time a year like this one lands inside it — but a cut or suspension is never inside any historical range. Pair it with the Distribution Safety Score™ to judge how durable the payout behind it looks.
• Leaving a variable weekly payer on the Industry Standard basis and trusting the spike. If your projected income jumped 40% the week after a fat distribution, that's the basis talking, not the fund. Switch back to DV Income Vision before drawing conclusions.
• Comparing our forward projection to a trailing number and calling one of them wrong. Forward (what the current rate implies) and trailing (what was actually paid) answer different questions. We show both — Yearly Income vs. TTM Yield — on purpose.
• Expecting specials to repeat. A year-end capital-gains distribution was real income once. Budgeting as if it arrives every quarter is how a 12% plan becomes a 7% reality.
• Forgetting that smoothing works both ways. After a genuine cut, DV Income Vision takes a few periods to fully believe it — its average reads slightly high while it catches up. The Industry Standard basis reacts immediately. That trade-off is exactly why the control is yours.

FAQ

Where do I change the estimate basis?

On the portfolio dividends page, above the projected chart — DV Income Vision or Industry Standard. The setting applies to the projected chart, the income KPIs, the top-earners list, the income calendar, and the other portfolio surfaces, so every page tells the same story. The Yearly Income card's sub-line names the active basis.

Which basis should I use?

DV Income Vision, almost always — it's the default, and it picks the right model per fund automatically. Switch to Industry Standard when you want the latest-payment indicated rate: it's what brokers and fund sponsors publish, so it's the view for reconciling our numbers against another tool's, and for steady payers the two barely differ anyway. Checking both takes two clicks, and the spread between them tells you how volatile your payout mix is.

Do special distributions count in my projection?

No — and this is deliberate. A payment more than 3× the median of its two-year neighborhood is classified as a one-off special and excluded from every forward basis. It still appears in your received history and trailing yield, because it was real cash; it just doesn't get annualized into next year.

Why does my projection differ from my broker's estimate?

Most brokers publish an "estimated annual income" built from the latest regular payment × frequency — equivalent to our Industry Standard basis, minus the specials filtering, the staleness guard, and the market-day schedule walk. If you're on DV Income Vision, or your broker is annualizing a payment we've flagged as special or stale, the numbers will differ — usually in our favor for realism.

How often do projections update?

With the daily data build, plus intra-day upgrades when an issuer declares a payment we capture from announcements. A newly declared amount immediately replaces the estimate for that payment and shades it as Announced.

Does the projection use the fund's price?

Not directly — we project cash per share first, then derive yield from it, never the reverse. Projecting yield and back-solving for cash is how a collapsing share price can make a "forecast" look accurate while the income quietly shrinks. Price enters only as a sanity check (a payment larger than the share price is rejected as bad data) and in the yield figures derived from the projected cash.