A portfolio list answers what is held. An exposure map asks what those holdings depend on. A website, a token, a domain collection, and an AI product may have different labels while relying on the same payment provider, customer group, or operating budget. Making those relationships visible is a practical step toward understanding concentration.

The exercise below extends the portfolio screening framework into a working record. It does not prescribe a target allocation or select investments. Its purpose is to organize evidence, prevent double counting, and help a reviewer see where a single interruption could affect several assets at once.

1. Define what the map is supposed to measure

Start by writing the review date, the portfolio boundary, and the decision being supported. A household inventory, an acquisition shortlist, and a company's operating asset register need different boundaries. Specify whether the map includes direct holdings, contractual claims, committed spending, borrowing, or assets under consideration. Keep prospective holdings separate from assets already owned.

Investor.gov's guide to asset allocation and diversification explains diversification as spreading investments to reduce risk and emphasizes examining holdings within asset categories as well as across them. It also notes that allocation depends on circumstances such as time horizon and risk tolerance. The exposure map applies that general principle by making shared dependencies explicit; it does not establish that a particular mix is appropriate.

Choose one reporting currency for monetary summaries and preserve original units alongside conversions. Record the valuation basis and date for each asset. An indicative token quote, a negotiated website estimate, and a domain asking price have different evidential strengths; combining them should not erase those differences.

2. Build an inventory that avoids duplicate economic interests

Give each holding a stable identifier and record its legal or operational description, quantity, valuation method, responsible account, and evidence location. Include a separate field for the person or organization responsible for maintaining the record. The aim is to make updates possible without reconstructing the entire portfolio each time.

Look for wrappers and components before adding totals. A website valuation may already include its domain. A claim token may represent an interest in assets shown elsewhere in the inventory. An operating business may own software that is also listed as a separate asset. State how each relationship is treated in the chosen portfolio boundary.

Maintain an explicit adjustment column. If an item is excluded from an aggregate to prevent double counting, preserve it in the inventory with the reason. Deleting the row loses useful dependency information. For example, a domain included in a website's value can still require its own renewal and access controls.

3. Tag each holding across several independent dimensions

Use separate columns for economic exposure, custody, counterparty, platform, revenue source, liquidity route, and operating obligations. These dimensions answer different questions. A holding can belong to several groups at once, so the map should not force every dependency into a single category.

  • Economic exposure: identify the asset, market, customer demand, or contractual payment that drives the holding's value.
  • Custody and control: identify where access is managed and which party can authorize movement or changes.
  • Counterparty: name the entity expected to honor a claim, process a payment, or provide a service.
  • Operating dependency: identify infrastructure, labor, renewals, data, and other inputs needed to keep the asset useful.
  • Exit route: record the specific market, buyer process, or redemption arrangement through which value might be realized.

For RWA holdings, use the RWA claim review to distinguish the issuer from the underlying exposure. For an operating AI asset, the AI screening criteria help identify model access, data permissions, and service costs. Preserve unknown dependencies as explicit entries rather than leaving ambiguous blank cells.

4. Summarize concentration without adding incompatible totals

Create a separate view for each dimension. One view can group values by custodian, another by revenue source, and another by exit venue. Explain whether each group is exclusive or overlapping. If a holding relies on both a model provider and a payment service, it can appear in both dependency views without becoming two economic assets.

In a fictional portfolio, two websites might depend on the same advertising account while an AI subscription product uses a different revenue channel. The important finding is the shared advertising dependency, even if the websites cover unrelated topics. The website screening framework can help document that relationship at the individual asset level.

Show both the amount associated with a dependency and the quality of the evidence. An apparent small exposure with a highly uncertain valuation deserves a different explanation from a precisely measured small holding. Where valuations are weak, use a clearly labeled range or a qualitative classification. Do not invent a midpoint merely to make the chart complete.

5. Add a liquidity timeline and a cash obligation calendar

For every holding, record the steps required to realize cash or another intended asset. Distinguish an indicative market quote from an actual sale process, a contractual redemption process, and an estimated search for a buyer. Include known restrictions, settlement steps, eligibility requirements, and relevant fees.

Use descriptive time categories only when their basis is clear. “Listed for sale” says little about when a buyer will arrive. “Redemption requested” does not mean funds are available. Record the evidence and conditions behind each timing assumption, then show which holdings cannot support a dependable liquidity estimate.

Separately list recurring obligations such as hosting, domain renewals, software access, and required administrative work. This calendar makes an operating mismatch visible: expenses may arrive before an illiquid asset can be sold. Keep the calendar distinct from the valuation table so future obligations are neither ignored nor accidentally counted twice in a business valuation.

6. Run scenarios that expose shared failure paths

Choose a small set of concrete scenarios relevant to the inventory. Examples include an unavailable custodian, a payment interruption, a loss of a major traffic source, a delayed redemption, or a required vendor replacement. For each scenario, identify the affected rows and the route by which the effect travels.

Separate immediate consequences from later ones. A vendor interruption may first stop new work, then delay revenue, then require migration spending. Write the sequence in plain language and identify the evidence needed to estimate each consequence. Use numerical assumptions only when they are documented or explicitly labeled as hypothetical inputs.

A scenario is a sensitivity exercise, not a forecast. Avoid assigning probabilities simply because the worksheet has a column for them. A useful result can be qualitative: several holdings share an access dependency, an exit route is untested, or a recovery task lacks an owner. Those findings can guide the next round of evidence gathering without pretending to measure every uncertainty.

Walk through one operational interruption

Assume a fictional operator manages domain registration, website hosting, and model access through accounts sharing one recovery address. Examine what happens if that address becomes unavailable. Which routine tasks can continue? Which account changes would be blocked? Who has documented responsibility for recovery? Keep this access scenario separate from a claim that every asset would lose its entire value.

Next, identify the work required to restore the affected functions and any obligations due during the interruption. The map may reveal a concentration of administrative access that is invisible in an allocation chart. Record the missing recovery evidence or ownership assignment as a concrete follow-up. This approach connects a shared dependency to an operational consequence without inventing a loss estimate that the available information cannot support.

7. Turn the map into a maintained decision record

End the review with a short action register. Each entry should name the exposure, the unanswered question, the person responsible for investigation, and the event or date for the next review. Useful actions include confirming a custody arrangement, updating an asset estimate, checking a renewal, and documenting an alternative operating process.

Preserve prior versions so changes in the map can be explained. A rising concentration may reflect a price change, an acquisition, a reclassification, or better evidence. Those causes have different implications. Record which one applies before interpreting the new percentage or assigning a response.

Conclusion: make dependencies visible before choosing a response

An exposure map becomes useful when every holding has a clear identity, valuation basis, dependency record, and potential exit path. Review one dimension at a time, preserve uncertainty, and use scenarios to locate unanswered questions. The resulting picture supports a more informed discussion of risk and operating resilience without implying that a large number of assets guarantees meaningful diversification.