Canonical page: https://sequoia-research.com/writing/are-dst-investments-safe-tenant-dependency-analyzer
Author: Sequoia Research
Published: 2026-10-17T10:30:36.011Z
Updated: 2026-10-17T10:30:36.011Z
Interactive tool: https://sequoia-research.com/writing/are-dst-investments-safe-tenant-dependency-analyzer#research-tool

# Are DST Investments Safe: Tenant Dependency Analyzer

## What Is This Article About?

This guide explains how to map shared tenant relationships across DST holdings without counting the same dollars twice. The Tenant Dependency Analyzer groups amounts you enter by tenant, parent organization, industry, and property. It keeps unknown amounts and missing relationships visible instead of filling them with guesses. You will learn to choose a clear total, read the separate views, and use the results to ask more precise research questions.

## Table of Contents

- [What Tenant Concentration Can Reveal](#what-tenant-concentration-can-reveal)
- [Choose One DST Exposure Basis](#choose-one-dst-exposure-basis)
- [Build Distinct Allocation Rows](#build-distinct-allocation-rows)
- [Enter Tenant and Parent Relationships](#enter-tenant-and-parent-relationships)
- [Read the Worked Dependency Map](#read-the-worked-dependency-map)
- [Keep Missing Data in the Result](#keep-missing-data-in-the-result)
- [Check Rental Periods and Source Dates](#check-rental-periods-and-source-dates)
- [Use the Map in a DST Risk Review](#use-the-map-in-a-dst-risk-review)
- [Save and Recheck Your Work](#save-and-recheck-your-work)
- [FAQ](#faq)
- [About Sequoia Research](#about-sequoia-research)
- [Sources](#sources)

## What Tenant Concentration Can Reveal

A list of five investments does not answer how much they rely on the same business. Two properties may have different street addresses while their tenants share a parent. Several distinct tenants may also work in one industry. These are different questions, so this tool gives each one its own view.

FINRA describes concentration risk as the chance of amplified losses from a large holding in an investment, asset class, or market segment. It also discusses related exposures and overlap within a portfolio. That provides context for checking shared dependencies. It does not provide a safe tenant percentage or endorse this analyzer. [FINRA: Concentrate on Concentration Risk](https://www.finra.org/investors/insights/concentration-risk).

The analyzer answers a narrow question: how do the amounts and relationships in your entered map group together? It cannot tell whether a tenant will pay, whether rent will cover costs, or what an interest could sell for. It does not read leases or confirm who stands behind a payment promise.

A 40% entered parent share means that 40% of the defined amount has that parent key in your records. It does not mean a 40% chance of loss. Nor does it say that a parent default would destroy every dollar in those rows. Those outcomes need separate evidence and a separate model.

## Choose One DST Exposure Basis

Choose either invested capital allocation or rental income for a defined period. Every row must use the same choice. The full-scope total is the number against which each share is measured. Write down what it includes before entering individual rows.

For invested capital, you might define the scope as the purchase amounts for a selected set of interests. Then explain how you assigned that capital to distinct tenant or property slices. The analyzer does not decide that allocation method. It does not turn original cost into current value.

For rental income, define both the period and the rent measure. Cash rent collected and rent billed are different amounts. A map that combines them has an unclear total even when its arithmetic balances. State whether the figures describe whole properties or a chosen investor share. Use that same scope throughout.

Consider an invented property with $2 million of annual rent. One tenant accounts for $500,000, or 25%. A separate investor has put $200,000 into an interest connected to that property. Entering the tenant's $500,000 beside the investor's $200,000 would mix property rent with invested capital. They cannot share a meaningful denominator.

You could choose to assign 25% of the $200,000 to that tenant as a research method. That would produce $50,000. But it is your stated allocation assumption, not a measured tenant-specific investment value. Record that assumption and its source. The tool never makes this conversion on your behalf.

Changing the basis menu leaves your entered numbers in place and removes the allocation confirmation. Review every amount before checking the box again. A different label cannot fix numbers prepared on a different basis.

## Build Distinct Allocation Rows

Each row should describe one nonoverlapping slice of the full scope. Give it a unique slice reference, a readable label, an amount if known, and supporting evidence with a date. The tool accepts from one through 30 rows.

The reference can point to your own worksheet row or another clear record. A repeat reference is rejected after spaces at its edges are removed. That catches an exact duplicate. It does not catch two different references that describe the same money. You still need to check the underlying records.

Suppose a $300,000 holding is split into two supplied allocations of $180,000 and $120,000. Those two rows use the full $300,000. Adding a third $300,000 row for the entire holding would count it again. Do not add a whole-position row beside its component slices.

The tool also rejects known row amounts above the full-scope total. That is a useful warning, but it is not a complete overlap test. Two duplicated $100,000 rows could still fit inside a $1 million total. A valid sum is only one check on a good map.

Use the evidence field to describe both the amount and the relationship mapping. Include a document title, date, page, and useful notes. If different records support different parts, identify each one. A source name typed into a field is not proof that the source says what you entered.

The confirmation box records your statement that the rows use one basis and do not overlap. Adding or removing a row clears that confirmation. No software check can replace your review of how the slices were formed.

## Enter Tenant and Parent Relationships

For each row, you can enter a tenant key, parent key, industry key, and property key. A key is a short identifier you choose and support with your records. Each entered key needs a readable label. Labels help readers understand the output; keys control the grouping.

Use the same key only when you intend the same relationship. The analyzer removes spaces at the edges of keys. It keeps letter case, punctuation, internal spaces, and leading zeros. Therefore, `TEN-01`, `ten-01`, and `TEN-1` remain three keys. It does not guess that they name the same firm.

This strict rule makes your choices visible. It also means a typo can split a group. Review the source list before concluding that similar names belong to separate businesses. If one exact key has different label text, the result keeps both labels and flags the difference.

Choose a consistent parent level. A direct parent and an ultimate parent may answer different research questions. Mixing those levels can hide shared exposure or create false conflicts. State the level in the scope notes, then use evidence that supports it for the chosen date.

A parent entry is only a recorded relationship. It does not establish a guarantee, financial support agreement, or right to collect rent from that parent. Review the actual legal documents separately before making any such claim.

When one tenant key has multiple entered parent keys, the analyzer shows a conflict notice. It retains both row-based mappings. A corporate change, inconsistent dates, different parent levels, or an input error could explain the conflict. The tool chooses none of these explanations for you.

## Read the Worked Dependency Map

The built-in example is invented. Its full scope is $1 million of allocated invested capital. It is not an actual portfolio, a current valuation, or a recommended allocation.

| Slice | Entered amount | Tenant | Parent | Industry | Property |
|---|---:|---|---|---|---|
| R1 | $250,000 | Shop One | Retail Parent | Retail | Building One |
| R2 | $150,000 | Shop Two | Retail Parent | Retail | Building Two |
| R3 | $200,000 | Clinic Three | Unknown | Healthcare | Building Three |
| R4 | $100,000 | Unknown | Unknown | Unknown | Building Four |
| R5 | Unknown | Warehouse Four | Industrial Parent | Industrial | Unknown |

The four known amounts total $700,000. That is 70% of the full scope. The remaining $300,000 is labeled unallocated or unquantified. The analyzer does not assign it to R5. Other missing slices could also explain some of that remainder.

Shop One has a known share of 25%, and Shop Two has 15%. In the parent view, their common Retail Parent totals $400,000, or 40%. This shows why separate tenant names do not always mean separate parent dependencies.

The parent view also contains $300,000 of known amounts without a parent key: R3 plus R4. The Industrial Parent group has an unquantified amount because R5's amount is blank. That is different from an identified parent with a known amount of zero.

In the industry view, Retail totals 40% and Healthcare totals 20%. Another 10% of known capital has no industry key. Industrial appears, but its amount is unquantified. In the property view, all $700,000 of known capital has a property key. R5 still lacks both a property key and a known amount.

Do not add the 40% Retail Parent share to the 40% Retail industry share. Both views include the same R1 and R2 dollars. The four views are alternate ways to group one scope. They are not four pools of money.

## Keep Missing Data in the Result

Blank and zero have different meanings. Leave the amount blank when you do not know it. Enter zero only when the evidence supports a zero amount on the chosen basis. The tool keeps that difference in the output and exports.

In the example, changing R5 from blank to zero removes it from the unquantified-row list. Its identified tenant and parent then show $0.00 and 0.00%. The $300,000 full-scope remainder still exists. A zero entry does not allocate missing capital elsewhere.

A readable name without a key remains unidentified for grouping. You might have a tenant's trading name but still be unsure of the legal entity. Keeping the name in the label field preserves that clue while leaving the grouping unresolved.

The result separates known dollars with a key from known dollars without one. Those two amounts sum to the quantified amount in each view. Unknown rows remain listed as well. They do not become zero merely because the known-dollar subtotal is available.

Percentages always use the full-scope total. If you divide Retail Parent's $400,000 only by the $700,000 of known rows, you get about 57.14%. That is its share of the quantified subset. The analyzer instead reports 40% of the stated $1 million scope. Shrinking the denominator would hide the remaining coverage gap.

Amounts are calculated in whole cents. Shares are rounded to two decimal places, with exact halfway values rounded upward. Rounded group shares may not add to the rounded total. Read the dollar amounts when checking a small difference caused by rounding.

## Check Rental Periods and Source Dates

Rental mode requires a start and end date. The end cannot precede the start or follow the review cutoff. The cutoff cannot be later than the current UTC date. A source date also cannot follow the cutoff.

These checks catch impossible combinations within the entered record. They do not prove that a source covers the whole rental period. For example, a June source for a period ending in September may contain only partial-year results. It could instead contain a forecast. The analyzer flags that source date so you can investigate.

A source dated after September is not automatically complete either. It may discuss an earlier month or use a different accounting basis. Read the document and state the actual period covered. A date gate is a consistency check, not an audit.

For invested capital mode, leave the rental dates blank. The review cutoff and source dates still apply. Explain in your notes whether the cost records include later purchases or reductions. The tool does not rebuild past positions from a transaction history.

If a relationship changes during a rental period, do not assign the same rent twice. Prepare distinct, supported slices if you need to separate the periods. Explain the split. The analyzer has no automatic time-weighting or corporate-history function.

## Use the Map in a DST Risk Review

Start with the largest supported groups and the largest evidence gaps. A large group with clear records calls for different follow-up than a large unidentified amount. The first needs analysis of the shared dependency. The second needs better mapping before its size can be interpreted.

Useful questions are specific. Which agreement identifies the rent-paying entity? What supports the parent connection? Does a portfolio-level number include the same properties and period? Which amount is still based on an allocation assumption? Keep the answers beside the source references.

Also consider what the map leaves out. It does not test debt payments, lease renewal costs, reserve access, sale timing, or your need for cash. A complete tenant map cannot settle those separate risks.

The SEC's March 2026 investor bulletin explains that asset allocation depends on personal risk tolerance and investing timeframe. The analyzer does not collect enough information to choose that mix or decide which holding you should buy or sell. Its role is to make one part of the evidence easier to inspect. [SEC: Investor.gov Tips for 2026](https://www.investor.gov/introduction-investing/general-resources/news-alerts/alerts-bulletins/investor-bulletins/investorgov-tips-2026-investor-bulletin).

## Save and Recheck Your Work

Analyze the entered map, then select a view if you want a narrower screen display. The JSON and text exports still include all four views, every input row, source notes, unresolved amounts, and conflict notices. The display filter does not remove records from the exported report.

Editing an input clears the prior result and disables exports until you analyze again. Clear, example replacement, and row removal use an on-page confirmation. Cancel preserves the entries. An edit while confirmation is pending cancels that pending action.

The tool has no automatic saving, import, source fetching, or revision history. Export a copy before leaving or clearing the page. Keep earlier reports separately if you need to compare versions. An exported source reference does not include the underlying document.

Inputs are limited to 120,000 UTF-8 bytes, and each export is limited to one mebibyte, or 1,048,576 bytes. Text with non-English characters can use more bytes than its character count suggests. If a limit is reached, shorten notes without removing the evidence needed to understand the map. Rejected analysis preserves your entered fields.

## FAQ

### Does a low tenant percentage mean a DST is safe?

No. It measures an entered share of one defined scope. It does not estimate default, loss, sale value, or investment suitability. Check the missing data and the other financial and legal risks separately.

### Can I combine invested capital and annual rent in one map?

No. Choose one basis and apply it to every row and the full-scope total. Prepare separate maps for separate questions. Changing the menu does not convert the amounts already entered.

### Why does the tool leave some named tenants unidentified?

A label alone does not control grouping. Enter a supported key when you intend to identify a group. A missing key keeps the name visible while preventing the tool from guessing which rows belong together.

### Is a shared parent responsible for all tenant obligations?

The map cannot establish that. It only records the relationships you entered. Any guarantee, support duty, or payment claim requires separate review of the relevant entities and documents.

### Can I add tenant and industry shares to measure total exposure?

No. The same allocation can appear in both views. Adding those shares would count that money again. Review each dimension separately and trace its row references to understand the overlap.

### Will an export keep the rows hidden by my view filter?

Yes. Both export formats retain the complete analyzed map. They include all four dimensions and the source notes. Export again after each revision you want to preserve, because the tool keeps no saved history.

## About Sequoia Research

Sequoia Research, LLC provides independent research on DSTs and other real estate investment offerings. This educational tool helps readers organize evidence and understand the limits of an entered dependency map.

## Sources

- [FINRA: Concentrate on Concentration Risk](https://www.finra.org/investors/insights/concentration-risk), June 15, 2022. General concentration and overlapping-exposure context; not an allocation threshold or endorsement of this tool.
- [SEC: Investor.gov Tips for 2026—Investor Bulletin](https://www.investor.gov/introduction-investing/general-resources/news-alerts/alerts-bulletins/investor-bulletins/investorgov-tips-2026-investor-bulletin), March 31, 2026. Personal risk tolerance and timeframe context. Both sources inspected October 17, 2026.


## Related Reading and Tools

- [Are DST Investments Safe in 2026? What Investors Should Understand About Risk](https://sequoia-research.com/writing/are-dst-investments-safe-in-2026-what-investors-should-understand-about-risk)
- [Problems With Delaware Statutory Trust (2026): What Investors Should Investigate Before Buying](https://sequoia-research.com/writing/problems-with-delaware-statutory-trust-2026-what-investors-should-investigate-before-buying)
- [Delaware Statutory Trust Returns: Exit Assumption Sensitivity Grid](https://sequoia-research.com/writing/delaware-statutory-trust-returns-exit-assumption-sensitivity-grid)