DV Income Vision™: How We Project Distributions

Definition

Dividend Vision Income Vision™ — DV Income Vision™ for short — is Dividend Vision's forward-income projection: the estimate behind your portfolio's Est. Annual figure, the projected dividends chart, the income calendar, the top-earners list, and the long-range forecast. Its job is one sentence: see the income ahead — how much cash your holdings are on track to pay, per share, on their actual payment schedules.

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

1. Paid — the distribution has already gone out. On the portfolio dividends chart this same cash is Received, from your broker's transaction history or the fund's realized per-share record. Not an estimate at all.
2. Declared — the issuer has formally announced a known per-share amount with stated ex and pay dates that haven't arrived yet. Nearly certain; only settlement is pending. We capture many of these from issuer announcements within hours of posting. The dividends chart shades this rung Announced.
3. Issuer scheduled — the issuer published the ex and/or pay dates (a 2026 schedule, for example) but has not yet announced the amount. Dates are on file; the dollars are still a projection. Calendar-only — the dividends chart still paints these as Estimated until an amount is declared.
4. Estimated — everything past the declared or issuer-scheduled horizon, projected from the fund's payout cadence and its recent distribution record.

Dates are never labeled Exact. A published date can still move; Declared and Issuer scheduled say what we actually know.

Most of this article is about Estimated, because that's where methodology actually matters — and where DV Income Vision does considerably more than the industry default of "take the last payment and multiply by 12."

It pairs with the Distribution Safety Score™: the score judges how sustainable a fund's income may be; DV Income Vision projects how much you may receive, and when. On the portfolio dividends page the two meet — the projection drives the numbers, the score grades the funds behind them.

DV Income Vision™ is a trademark of Dividend Vision LLC.

Why It Matters

Here is how forward income is calculated nearly everywhere else — brokers, portfolio trackers, even fund sponsors' own fact sheets: the most recent payment is annualized by the payment frequency, and that is the entire model. Last payment × 12 for a monthly payer, × 52 for a weekly one. It's called the "indicated rate," and for a steady quarterly dividend grower it works fine.

For the modern generation of variable-distribution funds, it breaks in ways that cost real money:

• One week sets the whole year. 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 "estimate" whipsaws every single week and tells you almost nothing.
• Year-end specials masquerade as run-rate. A fund that pays a $0.15 quarterly dividend and one $6.72 year-end capital-gains distribution briefly "yields" 181% to any tool that annualizes blindly. Real tools have published exactly that number.
• Dead funds keep "paying." A fund that quietly suspended its distribution still has a last payment on file — so naive tools keep annualizing it against a fallen share price and show 300% yields on funds that stopped paying years ago.
• The industry's workaround is avoidance, not a fix. One major broker simply excludes weekly payers from its income estimates entirely. Fund sponsors publish the same latest-payment rate with a disclaimer that it "does not imply future distributions."

Projections drive real decisions — how much you can withdraw, when a portfolio covers your expenses, whether a holding is pulling its weight. An estimate that swings 40% on one payment or triples on a special isn't a projection; it's a disclaimer wearing a number. DV Income Vision was built on the view that income investors deserve the model, not the disclaimer.

How It's Calculated

The 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. The dividends page, Overview, Forecast's automatic starting income and Goals' projected progress use the shared per-holding income total. The calendar uses the shared event-amount model and dated payment schedule. Cross-surface regression tests cover their gates and assumptions; a monthly planning average still answers a different question from a month's dated cash.

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.
• Ex-dates walk the NYSE trading calendar. Weekends and exchange holidays are skipped so a daily payer goes ex on market sessions (about 252 a year, not 365 — a calendar-day walk would overstate a daily payer's income by roughly 45%).
• Pay dates walk the Fed / DTC settlement calendar, not the exchange calendar. The NYSE is open on Veterans Day and Columbus Day / Indigenous Peoples' Day; the Federal Reserve is not. A "next market day" pay offset can therefore land cash on a bank holiday. We roll pay dates forward to the next settlement day instead. Veterans Day Wednesday 11/11/2026 is a trading day and a bank holiday; YieldMax's published 2026 schedule pays Thursday 11/12, and so do we.
• Calendar labels follow the four-state ladder above (Paid, Declared, Issuer scheduled, Estimated). A declared or issuer-published date is never called Exact.

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.

Three more rules shape the months ahead, and all three are in the chart rather than hidden behind it. A fund that publishes a target distribution (a "Target 15" policy, for example) is pinned to that band while its recent checks sit steady on it, and is steered toward the band over the coming months when they wander. A fund whose regular payouts fell over the past year is projected at its current rate, not decayed further: a decay was built, replayed over each such fund in the history, and retired when the replay showed those funds tend to restore rather than keep falling. Weekly payers are the exception the same replay found: across 47 weekly option-income funds, the year after each payment came in a median 12% under the rate at the time, in each quarter since 2024. So a weekly fund's next payment is projected as printed and each later one tapers a little, averaging about 88% of today's rate over the year — a rule the replay re-checks on each run and retires if it stops beating a flat projection on the most recent funds.

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 an 8,000% yield, and is discarded.

Each event also carries its distribution type and classification confidence. A payment explicitly identified as a special, supplemental, or capital-gains distribution is never used as a recurring baseline. If the type is unknown and the amount is an extreme outlier, the recurring projection is suppressed for review instead of assuming the payment repeats.

For a declared event, portfolio cash uses the shares eligible at its ex-date when transaction history is available. A later buy cannot earn that payment, and a later sale does not erase an entitlement already earned. Future estimates use current shares as a labeled assumption. Shares bought by reinvesting event N begin earning income only on a later eligible event; they never recursively enlarge event N itself.

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 each projection surface. 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 an amount-model backtest against the realized payouts (the same code the site runs, replayed over every fund's history):
• 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.
• Seasonal payers — quarterly or semi-annual funds whose year repeats a lopsided shape, like an international equity ETF that pays most of its year in June — project the year as their last full cycle and each payment from its counterpart a year earlier, so the big payment lands in the right month at about the right size instead of four identical quarters. The profile has to be real and repeating (the same peak position two years running, each position's share within a fifth of the year before) or the fund is treated as an ordinary variable payer; the replay showed the rule loses on monthly payers, so it is not applied to them.

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. In total, that validation replays roughly 140,000 forward-year projections against what funds actually went on to pay, and the per-fund model beats the industry-standard estimate on the median and the average, and on monthly, quarterly and semi-annual payers. On weekly payers — a young cohort of a few hundred forward years — the latest payment still scores as well or better, so the weekly rules are tuned on their own and the two bases differ least there.

• 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.

Scenario precedence and reproducibility

The portfolio forecast runs one distribution-amount engine at a time. A blank dividend- growth override uses DV Income Vision; entering a rate switches that scenario to User override. A blended scenario is a separate, explicitly weighted mode. The active source is shown beside the control and written into forecast exports. Clearing an override restores the model baseline; it does not rewrite that baseline.

Validation is a replay, not a fixture library. For each fund and each anchor date in its payout history, the estimator is handed only the data dated on or before that anchor and is scored against the regular payouts that actually followed — the next payment, and the next year of payments. Results are reported per payout cadence, both event-weighted and fund-weighted, as median and average percentage error; the Likely range's width is fitted on the older 70% of anchors and checked on the newest 30%, and each cadence class is held to a coverage window on each run. A model change ships only when that replay says it helps, and the replay is re-run on each change.

Portfolio-value Monte Carlo paths and payout uncertainty are separate channels. A joint income/price model is used only when a cohort has enough data to calibrate the dependency; its correlation assumptions carry a version. Otherwise the distribution forecast stays deterministic while market value remains stochastic. Identical saved scenario inputs use a stable seed so a run can be replayed, and simulated cash, shares, income, and value are floored at zero.

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. Next week the payout is $0.09 and the same tool says $4,680/yr. Neither number was ever the fund.
• 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, in dollars under the yield; 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 jumps roughly tenfold overnight ($0.90 × 52 = $46.80/share, against $4,680/yr the week before). 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 each 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 Est. Annual card makes the width honest — computed from how much each fund's recent payouts actually vary, calibrated per fund and payout cadence so that half the time a fund's year lands inside its own band, and never narrower than the year-over-year move the steadiest funds of that cadence still make — but a cut or suspension is never inside any historical range. That calibration is per fund. Holdings that share an underlying or an issuer's option lineup are counted as one shock, so spreading across them narrows the band less than it looks — and a diversified book's range can still come out narrower than its measured spread (the misses run mostly upward), so read it as a floor on the width rather than a coverage promise. 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 — see forward vs trailing yield. We show both — Est. Annual 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's average can read slightly high for a period or two while it catches up (a deep drop — past a third to a half of the recent average — is blended in at once on weekly, quarterly and semi-annual payers). The Industry Standard basis reacts immediately. That trade-off is exactly why the control is yours.

FAQ

What is Dividend Vision Income Vision?

It is Dividend Vision's forward-income projection — the estimate basis behind Est. Annual, the projected dividends chart, and the income calendar. Rather than annualizing a fund's last payment the way the industry-standard indicated rate does, it chooses the projection model per fund from its own payout history, filters out one-off specials, walks ex-dates on the NYSE calendar, and walks pay dates on the Fed settlement calendar.

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 cards, the top-earners list, the Overview's yearly income and the income calendar's amounts. Forecast and Goals use the shared per-holding income total for automatic starting income. Ask DV may use browser income totals or server distribution-rate estimates; the reconciliation section below explains the difference. The Est. Annual card's sub-line names the active basis.

How should I reconcile the calendar, Forecast, Goals and Ask DV?

Forecast's automatic starting income and Goals' projected progress now read the shared per-holding total under the selected estimate basis, Income Vision or Industry Standard. Forecast's editable assumptions can change the scenario after that starting point. Ask DV can read browser holdings income or retrieve server holdings with sourced distribution rates. Server rate estimates need not match the dated calendar model; ask which source, timestamp and account scope the answer uses before comparing numbers.

Annual income / 12 is a planning average; calendar cash follows payment dates. A hypothetical holding paying $10 per week produces $40 in a four-payment month and $50 in a five-payment month. A $520 annual run-rate averages $43.33 per month. None of these figures promises a future payment. The two estimate bases can also coincide for a steady payer; agreement does not mean the control failed.

Compare the same selected account or collection, on mobile as well as desktop. Received cash depends on available transaction history and its date window. It can include payments earned before a position was sold, whereas a forward projection starts from current holdings. Missing history is incomplete coverage, not evidence of no income. Manual corrections and ex-date ownership belong to received or declared cash; future estimates use current shares as a disclosed assumption.

Forecast growth, contributions, DRIP, withdrawals, taxes and margin settings are separate scenario assumptions. Existing portfolio/browser persistence keeps those saved settings; changing the income basis does not rewrite them. Compare gross distributions before subtracting taxes or margin interest. Declared amounts come from issuer announcements; estimated amounts remain projections. Stale holdings or payout data needs review.

Special is a recurring-income classification, not a final tax classification. An excluded special can still be received cash. Ordinary income, capital gains and return of capital need reconciliation against final issuer information and tax forms; a projection or preliminary notice cannot establish that character.

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?

Brokers differ, so compare like with like. Several 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 split exchange / settlement schedule walk. Schwab documents its figure as the prior twelve months of actual payments, which is our TTM Yield card's trailing dollars, not a projection at all. 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.

Is DV Income Vision a forecast or a guarantee?

Neither — it is a structured estimate. It assumes each fund keeps paying at its projected rate, and no historical model can see a cut or suspension coming. Pair it with the Distribution Safety Score, which grades how durable each payout looks, and read the Likely range for how wide a normal year could land.

How is it related to the Distribution Safety Score?

They are two halves of one question. The Distribution Safety Score answers how sustainable may the income be — a 0–100 grade of each fund's payout durability. DV Income Vision answers how much income may you receive, and when. The portfolio dividends page runs on the projection and grades it with the score.