How to Document Longevity Assumptions for Fiduciary Compliance

The Documentation Gap

Every financial plan contains a longevity assumption. It might be explicit — a planning horizon of age 90, or a withdrawal rate calibrated to a 30-year retirement. Or it might be implicit — an insurance recommendation that only makes sense if the client lives past a certain age, or a Social Security timing decision that assumes a particular lifespan.

Either way, the assumption exists. And in a growing number of regulatory actions and arbitration cases, the question being asked is not just whether the assumption was reasonable — but whether the advisor documented how they arrived at it.

This is not a hypothetical concern. The SEC's Regulation Best Interest, FINRA's suitability framework, and state fiduciary standards all require that advisors demonstrate a reasonable basis for their recommendations. When those recommendations depend on how long a client will live — and most of them do — the longevity assumption becomes part of the evidentiary record.

Most advisors have no documentation for this assumption at all. They used a default age in their planning software, or they picked a round number that "felt right," or they applied the same planning horizon to every client regardless of health. None of these approaches creates a defensible record.

What Regulators Actually Look For

Regulators do not expect advisors to predict the date of death. They expect advisors to demonstrate that they considered the relevant factors and applied a reasonable methodology.

In practice, this means three things:

1. Individualized Analysis

A regulator reviewing a complaint wants to see evidence that the advisor considered the specific client's circumstances. A boilerplate planning horizon applied uniformly to all clients — "we plan to age 95 for everyone" — is better than nothing, but it does not demonstrate individualized analysis. It raises the obvious question: if Client A has stage 3 COPD and Client B is a healthy marathon runner, why do they have the same longevity assumption?

The standard is not perfection. It is reasonableness. An advisor who documents a health-adjusted life expectancy estimate based on the client's disclosed conditions, family history, and lifestyle has a far stronger position than one who used a default.

2. Methodology Transparency

The advisor should be able to articulate the methodology used to arrive at the longevity assumption. This does not require disclosing proprietary model parameters. It requires explaining the conceptual approach.

For example: "We estimated Client A's health-adjusted life expectancy using actuarial mortality tables (SOA 2015 VBT) adjusted for individual health conditions, severity levels, and comorbidity interactions, with mortality improvement projections (MP-2021). Monte Carlo simulation was used to generate a distribution of outcomes. The median life expectancy was used as the central planning assumption, and the plan was stress-tested against the 90th percentile outcome."

That paragraph is defensible. "We used age 90 because that's what our software defaults to" is not.

3. Consistency Between Assumption and Recommendation

Regulators look for internal consistency. If the advisor's longevity assumption implies a 20-year planning horizon but the withdrawal rate assumes 30 years, there is an unexplained contradiction. If the advisor recommended an annuity that only breaks even at age 88 but the health-adjusted life expectancy is 78, the recommendation needs justification.

Consistency does not mean the recommendation must mechanically follow from the longevity estimate. There are valid reasons to plan conservatively beyond the central estimate — that is what confidence intervals are for. But the file should show that the advisor considered the longevity assumption and made a deliberate choice about how to use it.

Why Population Tables Create Liability

Most advisors who document longevity assumptions at all use population life tables — Social Security Administration period tables, CDC National Vital Statistics, or the defaults embedded in planning software. These tables are convenient and authoritative, which makes them feel safe.

They are not safe. They are a liability when applied to individual clients.

Population tables describe average mortality across the entire population, including people with and without health conditions, across all socioeconomic strata, and regardless of lifestyle. For any specific client, the population average can be significantly wrong. A 70-year-old with congestive heart failure and diabetes has a materially different life expectancy than a healthy 70-year-old. The population table treats them identically.

If an advisor uses a population table for a client with significant health impairments and then recommends a 30-year planning horizon, they have potentially overestimated the client's lifespan by a decade. That overestimate might cause the client to live more frugally than necessary, delay Social Security claiming beyond the optimal date, or maintain an insurance policy whose economics do not justify continued premiums.

Conversely, if the advisor uses a population table for a remarkably healthy client, they may underestimate the planning horizon — creating a real risk that the client outlives the plan.

In both directions, the advisor is exposed. Not because they used a published table — that is understandable — but because they failed to consider whether that table was appropriate for the individual client.

The Documentation Framework

Building defensible documentation does not require a radical overhaul of your practice. It requires adding a systematic step to your existing process.

Step 1: Gather Health Information

During discovery or annual review, collect the client's current health conditions, including diagnoses, severity, and treatment status. Document medications, as they serve as a proxy for conditions and severity. Record family history of longevity — parents' and siblings' ages at death or current ages. Note lifestyle factors: smoking history, exercise habits, BMI, alcohol use.

This information should be captured in a structured format that can be filed with the planning documentation. A free-form note is better than nothing, but a standardized health questionnaire is better.

Step 2: Generate a Health-Adjusted Estimate

Use actuarial-grade longevity tools to convert the health information into a quantitative estimate. The output should include at minimum a central estimate (mean or median life expectancy), a confidence interval (such as the 5th and 95th percentiles), and survival probabilities to key ages.

Try our free calculator to see how individual health factors shift longevity estimates from population averages.

For clients where the planning decision is sensitive to the longevity assumption — which is most clients — this step is not optional. It is the difference between a defensible assumption and an arbitrary one.

Step 3: Document the Assumption and Its Basis

In the planning file, state the longevity assumption used, the methodology that produced it, and the key health factors that influenced the result. This documentation should be specific enough that a reviewer can understand why this client received this assumption.

An example entry might read: "Client's health-adjusted life expectancy estimated at 81 years (median), with a 90% confidence interval of 74-89. Key factors: type 2 diabetes (moderate severity), history of coronary artery bypass grafting (2021), former smoker (quit 2015, 25 pack-year history). Based on SOA 2015 VBT tables with MP-2021 mortality improvement, adjusted for individual health profile. Planning horizon set at 89 (90th percentile) to provide conservative buffer."

Step 4: Connect the Assumption to the Recommendation

For each recommendation that depends on the longevity assumption, document the connection. If the withdrawal rate was set at 4.5% instead of 4% because the client's health-adjusted life expectancy is shorter than average, say so. If Social Security claiming at 66 was recommended because the client is unlikely to reach the breakeven age of 82, document the analysis.

This step protects the advisor in two directions. It shows the regulator that the recommendation followed from a reasoned analysis. And it shows the client — or their heirs — that the advisor was acting in their interest, not applying a generic formula.

Step 5: Schedule Reassessment

Health changes. Document when the longevity assumption will be revisited — annually at minimum, and whenever the client reports a significant health event. A longevity assumption made at age 65 may be materially wrong by age 72 if the client has had a cancer diagnosis, a cardiac event, or a significant functional decline.

The reassessment schedule itself becomes part of the compliance record. It demonstrates that the advisor views longevity assessment as an ongoing obligation, not a one-time exercise.

Common Documentation Failures

Using Software Defaults Without Explanation

Planning software typically defaults to population-average life expectancy or a fixed age like 90 or 95. Using the default is not inherently wrong, but failing to document why the default is appropriate for this client is a gap. If you use the default, write one sentence explaining why it is reasonable. If the client has health conditions that make the default inappropriate, override it and document the override.

Inconsistent Assumptions Across Documents

A client's financial plan assumes age 92. Their insurance analysis assumes age 85. Their Social Security analysis uses the population average of 84. These inconsistencies are common when different tools and different parts of the practice use different defaults, and they create exactly the kind of contradictions that regulators notice.

Pick a longevity assumption, document it, and use it consistently across all planning analyses for that client. Where you deliberately deviate — using a more conservative assumption for withdrawal rate planning, for example — document the rationale.

No Record of Health Information

If the advisor never asked about health conditions, there is no basis for any longevity assumption other than the population average. Even if the advisor's recommendation is sound, the absence of health documentation suggests that health was not considered. Build health information gathering into your standard discovery process and keep the records.

Stale Assumptions

A longevity assumption made five years ago for a client who has since been diagnosed with a serious illness is not just outdated — it is potentially negligent if the advisor continued to rely on it. Document reassessment dates and follow through.

How Automated Tools Strengthen Compliance

One of the reasons advisors skip longevity documentation is that it historically required manual effort — looking up tables, making subjective adjustments, writing up the analysis. The process was time-consuming and the output was hard to standardize.

Automated longevity platforms change this calculus. When you run a client's health profile through an actuarial longevity model, the platform generates a structured output that includes the health-adjusted life expectancy, confidence intervals, the methodology description, and the key factors that influenced the result. This output can be filed directly in the client record.

Lumis Life generates reports that include all of these elements — the central estimate, the confidence interval, survival probabilities, and the key health factors that drove the result. The report itself becomes the documentation. There is no need to manually write up the analysis, because the tool produces a structured record that satisfies the documentation requirements.

This does not replace the advisor's judgment. The advisor still decides how to use the longevity estimate in the financial plan, and that connection still needs to be documented. But the most time-consuming part — generating a defensible, individualized longevity estimate and documenting its basis — is handled by the platform.

What Good Documentation Looks Like in Practice

To make this concrete, here is what a well-documented longevity assumption looks like in a client file versus a poorly documented one.

Weak documentation: "Planning horizon: age 92. Source: firm default."

This tells a reviewer nothing about why age 92 is appropriate for this client. It does not reference the client's health, does not describe a methodology, and does not explain the connection to any recommendation.

Strong documentation: "Client's health-adjusted life expectancy estimated at 83 (median) with 90% CI of 76-91. Methodology: SOA 2015 VBT with MP-2021 mortality improvement, adjusted for client's reported conditions (type 2 diabetes, controlled hypertension, former smoker quit 2018). Planning horizon set at 91 (95th percentile) for withdrawal rate analysis to provide margin of safety. Social Security breakeven analysis conducted using median LE of 83. Insurance review conducted using full LE distribution. Reassessment scheduled at next annual review or upon significant health change."

The difference is not length — it is substance. The strong documentation takes perhaps five minutes longer to produce, but it demonstrates individualized analysis, methodology transparency, and consistency between the assumption and the recommendations.

The Fiduciary Trend

The direction of regulation is clear. Both the SEC and FINRA have increased scrutiny of the analytical basis for financial recommendations. State fiduciary standards for insurance advice are expanding. The NAIC has adopted model regulations that address the suitability of insurance recommendations in the context of the client's life expectancy.

Advisors who document their longevity assumptions now are ahead of the curve. Those who wait until a complaint or examination forces the question will find themselves defending undocumented assumptions retroactively — a much harder position.

The framework is straightforward: gather health information, generate a health-adjusted estimate, document the assumption and its basis, connect it to each recommendation, and schedule reassessment. Five steps that transform an implicit guess into a defensible, documented analysis.

Conclusion

Every financial recommendation that depends on how long a client will live rests on a longevity assumption. That assumption is either documented or it is not. It is either individualized or it is generic. It is either defensible or it is vulnerable.

The standard of practice is shifting toward documented, individualized, defensible longevity assumptions. Advisors who build this documentation into their workflow are not just managing compliance risk — they are building better plans, because the act of examining and documenting the longevity assumption forces a more rigorous analysis.

The clients benefit. The practice benefits. And when the inevitable question arises — "how did you arrive at this assumption?" — the answer is already in the file.

Get a free longevity report and see how automated documentation can strengthen both your planning process and your compliance record.