Canonical page: https://sequoia-research.com/writing/dst-brokers-broker-transition-planner
Author: Sequoia Research
Published: 2026-10-18T03:35:38.262Z
Updated: 2026-10-18T03:35:38.262Z
Interactive tool: https://sequoia-research.com/writing/dst-brokers-broker-transition-planner#research-tool

# DST Brokers: Broker Transition Planner

## What Is This Article About?

Changing DST brokers can leave open questions about old documents, current service, and who owns the next task. This planner helps you record those questions for each Delaware statutory trust, or DST, holding. It keeps document access, accepted service scope, and request status separate. You enter the facts and sources yourself, and earlier snapshots remain in the download. The planner does not contact firms, move assets, or verify that anyone has accepted responsibility.

## Table of Contents

- [What a DST Broker Transition Plan Covers](#what-a-dst-broker-transition-plan-covers)
- [Start With Holdings and Specific Handoff Items](#start-with-holdings-and-specific-handoff-items)
- [Separate Retained Documents From Ongoing Access](#separate-retained-documents-from-ongoing-access)
- [Record a Contact and the Scope They Accepted](#record-a-contact-and-the-scope-they-accepted)
- [Track Open Requests and Responses](#track-open-requests-and-responses)
- [Read the Fictional Broker Handoff Example](#read-the-fictional-broker-handoff-example)
- [Preserve Changes Without Carrying Old Checks Forward](#preserve-changes-without-carrying-old-checks-forward)
- [Review Dates, Limits, and Downloads](#review-dates-limits-and-downloads)
- [Turn the Plan Into Clear Follow-Up Questions](#turn-the-plan-into-clear-follow-up-questions)
- [FAQ](#faq)

## What a DST Broker Transition Plan Covers

A relationship change can affect several kinds of work. You may need a past report, a reply to an old question, or a clear route for future notices. Those needs can belong to different firms or roles. Writing one new name beside the holding may leave the real work unclear.

This planner organizes your own notes about that work. A holding is the investment label you choose to track. A handoff item is one specific service question for that holding. A snapshot records the current document, role, and request states for that item. These are separate records, so one answer does not fill every gap.

The Financial Industry Regulatory Authority, or FINRA, addresses member-firm communications when a registered representative departs. Its guidance discusses clear service information and answers to customer questions, if known. Contact-information disclosures also have consent, privacy, and knowledge limits. Those points support asking precise questions; they do not establish what happened in your file. [FINRA Notice 19-10](https://www.finra.org/rules-guidance/notices/19-10).

FINRA Rule 2273 separately requires an educational communication in defined recruitment and account-transfer situations. Its timing provisions govern the covered firm's delivery duty. They are not a universal investor deadline to move a holding. This planner neither determines whether the rule applies nor performs an account transfer. [FINRA Rule 2273](https://www.finra.org/rules-guidance/rulebooks/finra-rules/2273).

Use the plan to prepare a conversation about your actual needs. A fully filled form does not establish that the list is complete. Nor does a zero gap count establish that a new service arrangement is suitable. You still need the relevant agreements, records, and responses from the right parties.

## Start With Holdings and Specific Handoff Items

Enter a short plan title, the service change being reviewed, and a review cutoff date. Then add the holdings within that scope. Use a label that distinguishes the trust and class or interest. Keep account numbers, tax identifiers, private contact details, passwords, and access tokens outside this tool.

A holding label is a reference, not a verified ownership record. If you use a nickname, maintain the mapping to the exact issuer in your secure records. Two labels that differ only by spacing or letter case cannot be entered as separate holdings. The planner does not detect every alias or prove that two different labels refer to different assets.

For each holding, add one specific handoff item. Choose a service area: reporting access, tax document access, an existing request, or other service. Then describe the actual task. “Obtain the September report” is more useful than “handle everything.” A separate question about who will review that report may need its own item.

The same holding can have several items in one area. Each should have a distinct purpose. The planner rejects the same normalized title within the same holding and area. It allows that title for another holding because the source, responsible role, and outcome may differ.

A holding without any items remains visible as a gap in the entered plan. It is not treated as finished. Review it and decide whether work needs to be added. The tool has no list of legally required tasks and does not create one automatically from the type of investment.

## Separate Retained Documents From Ongoing Access

Choose a document state for each item. This field asks what you have recorded about the particular document need. It does not judge the content of a report. The five states have different meanings:

| Document State | Meaning Within This Plan |
|---|---|
| Not assessed | You have not recorded an assessment of this item's document need |
| Reference recorded | You have a source reference, but have not recorded a retained copy or tested access |
| Copy retained | You report that a copy has been retained |
| Access tested | You report that the relevant access route was tested |
| Not needed for this item | You give a reason that no document is needed for this narrow task |

The three recorded-document states need a reference and a check date. The reference could name a secure folder and file version. It could instead identify a separate note about an access test. It is plain text here. The planner does not open the location, upload the file, or test the route.

A saved copy can help preserve information even if a portal later changes. It does not establish that you can retrieve next month's report. Conversely, a working route does not prove that every past document has been saved. Write these as separate items when both questions matter to the handoff.

Use “Not needed” only for the specific item and explain why. A question about which department owns a request may not yet require a document. That choice says nothing about the documents needed to assess the investment itself. The reason remains in the full snapshot so a later reviewer can revisit it.

“Not assessed” keeps the document evidence fields blank. This makes a missing assessment visible instead of letting a vague reference imply progress. If the situation changes, append a new snapshot with the appropriate state and source. The earlier uncertainty remains in the history.

## Record a Contact and the Scope They Accepted

Naming a role and recording scope acceptance are separate steps. “Investor service team” may describe where you intend to ask a question. It does not establish that this team has agreed to review a report, resolve a fee dispute, or provide investment advice.

The responsibility field offers three states. Unconfirmed allows a proposed role label, but keeps contact evidence and acceptance fields blank. Proposed role recorded requires the role label, a contact-source reference, and a date you checked that source. Acceptance recorded also requires the exact accepted scope, its evidence reference, and its date.

These are your statements about the evidence. The tool does not authenticate a message or determine whether the writer could bind a firm. A contact-source reference should point to the separate record you used. Avoid pasting private addresses or login details when a non-sensitive reference will do.

The Securities and Exchange Commission, or SEC, explains that the services you receive depend on your agreement with the broker or adviser. Its relationship-summary guide helps readers ask about services, fees, and conflicts. A name entered into this planner does not create that agreement or add ongoing monitoring. [SEC guide to relationship summaries](https://www.investor.gov/CRS).

Keep the accepted scope narrow enough to test. A reply agreeing to supply one report may resolve the delivery role while leaving report analysis unassigned. If a different party is meant to interpret the report, create another item or keep that next step open. Do not stretch a limited reply into responsibility for the entire holding.

## Track Open Requests and Responses

The work state describes progress on the specific handoff item. Open means you still have a next action. Response recorded means an answer has been entered, but the plan has not recorded its closure review. Closed in this plan means you entered the response, a review date, and the reason for closing that item.

A response needs its date, reference, and summary. Closure needs those fields plus a date and reason for the review. The closure date cannot precede the response being reviewed. Open and response-recorded items require a next action so the plan says what remains to be done.

Closure is a local planning judgment. It is not a ruling that a firm met every duty or that the investment is sound. You may close a narrow request after learning that a party will not provide the requested service. The reason should explain that result and, where needed, point to a separate open task.

The planner allows a closed item to retain a document or responsibility gap, and flags that combination. This is deliberate. Forcing acceptance would encourage an inaccurate entry when a question ended with a refusal. Review the flagged closure reason to decide whether the item really ended or whether a new task is needed.

A response can also arrive before responsibility is settled. Someone may provide useful information without accepting future work. Recording that answer should not fill the scope-acceptance fields automatically. Separate states preserve the difference between one helpful reply and an agreed ongoing role.

## Read the Fictional Broker Handoff Example

The example button loads invented records for Rowan, Cedar, and Pine holdings. None represents an actual investment or client file. It contains three handoff items and four snapshots. Two items concern Rowan, one concerns Cedar, and Pine has no entered item.

Rowan's first item asks for a September report. Its first snapshot records tested access, a prior role's limited acceptance, and closure of that request. A later snapshot records a changed service route. Its document state is not assessed, responsibility is unconfirmed, and work is open. The old checks remain in history rather than filling the new snapshot.

Rowan's second item concerns a prior tax document. A copy is marked retained and scope acceptance is recorded. A response has arrived, but review by the tax preparer remains the next action. Cedar's item asks who owns an open fee question. It has no named role and says no document is needed for that narrow routing question yet.

| Current Example Count | Result |
|---|---:|
| Holdings | 3 |
| Handoff items | 3 |
| Saved snapshots | 4 |
| Prior snapshots retained | 1 |
| Holdings without items | 1 |
| Items without recorded scope acceptance | 2 |
| Items without a named role | 1 |
| Open items | 2 |
| Responses awaiting review | 1 |
| Items closed in this plan | 0 |

The document states also split three ways: one not assessed, one copy retained, and one not needed. No current item has tested access recorded. The first Rowan snapshot did have that check, but it is no longer the current snapshot. Counting it again would hide the changed route.

The rows are not independent problems to add into one total. Cedar's item is both open and missing a role. Rowan's changed-route item is open and lacks scope acceptance. The counts describe different views of the same entered work. The tool gives no completion percentage or readiness grade.

## Preserve Changes Without Carrying Old Checks Forward

Choose “New snapshot” beside an existing item to record a change. Its holding, service area, and title stay fixed. All evidence and status fields start blank or unconfirmed. Enter the current facts again, including a reason for the new snapshot. The tool does not copy old acceptance or closure into a new review.

This extra step is useful when a role, route, or service scope changes. A source supporting the former arrangement may still be important history. It does not automatically support the new one. Re-enter any evidence that remains relevant after checking what it actually covers.

Snapshots are append-only. Saving a later snapshot does not erase an earlier answer. The current review uses the latest saved snapshot for each item. The full export includes every snapshot and the link to the prior one, so a reader can follow why the plan changed.

Snapshot dates may be equal, but cannot move backward within an item. If you discover an old record today, describe its original date in the source reference and use the date of the new snapshot for the entry. The separate evidence dates can be earlier. The planner does not turn the latest-entered record into proof that it is the newest underlying document.

Holding and item identities cannot be renamed or deleted. This prevents earlier work from silently attaching to a different holding or task. To correct a mistaken identity, export the plan and start a new one. State the correction in the new scope and keep the prior copy as appropriate for your records.

## Review Dates, Limits, and Downloads

The review cutoff cannot be later than today's date in UTC, the time standard used by the tool. Snapshot dates must fall on or before that cutoff. Evidence dates cannot follow their snapshot date. Dates must be real calendar dates from 1900 onward. These checks find impossible entries; they do not calculate legal deadlines or test timeliness under a contract.

The plan permits eight holdings, twenty-four handoff items, and seventy-two snapshots. Saved records also have a size limit of 80,000 UTF-8 bytes. Each complete export must fit within 190,000 bytes. Longer text and some characters use more bytes, so a size limit can apply before the record-count limit.

A rejected save leaves the saved plan unchanged. Clear or correct the unsaved fields before preparing another review. Changes to inputs clear the displayed result and disable downloads until you prepare again. Selecting a new snapshot also blocks export until you save or cancel that revision.

Downloads are available as JSON and readable text. Both include all holdings, item identities, current results, and prior snapshots. The JSON format is useful for preserving named fields; the text format is easier to read without special software. There is no import function or automatic recovery of a downloaded plan.

The tool uses local page memory and does not automatically save records. Leaving or refreshing the page can lose the plan. Download a copy before doing so. Loading the fictional example or starting a new plan requires confirmation because it replaces both saved and unsaved work on this page.

## Turn the Plan Into Clear Follow-Up Questions

Prepare the review and read the gaps by holding. Begin with a specific need: which report, period, version, request, or service is unresolved? Then identify the role that can answer that question. A document gap and an authority gap often need different responses.

Use the source references to find the actual records outside the tool. Check that the reply concerns the right holding and task. If it covers only delivery, avoid treating it as an agreement to analyze the investment. If a response changes the scope, record the change and decide whether another item belongs in the plan.

The planner does not send the questions. You choose what to share, with whom, and through which established route. Review exports before sharing because even short references can reveal sensitive context. A useful handoff record leaves the next person able to see what is known, which evidence supports it, and what still needs an answer.

## FAQ

### Does This Planner Transfer My DST Holding?

No. It records a service handoff and its open questions. It does not submit transfer forms, change ownership, contact firms, or determine whether an asset can move. Any actual transfer process remains separate from this local plan.

### Does Acceptance Recorded Mean the Contact Is Verified?

No. It means you entered a role, contact-source evidence, and a dated reference for the stated scope. The tool checks required fields and date order. It does not authenticate the contact, inspect the reply, or decide whether the person has authority to accept the task.

### Can a Retained Copy Count as Ongoing Portal Access?

No. Copy retained and access tested are separate states. A copy shows what you say you saved. It does not establish access to future reports. Use separate items if you need to track both the saved record and the continuing route.

### Why Does a New Snapshot Start With Blank Checks?

A changed role or service route can make an old acceptance inapplicable. Blank checks require you to review the current facts instead of silently carrying those claims forward. The old snapshot remains in the full history and download.

### Can I Close an Item That Still Has a Gap?

Yes, with a recorded response and a closure reason. The planner flags closed items that still have a document or scope-acceptance gap. A refusal may end one request while creating another. Review the reason rather than treating the closed label as complete service coverage.

### Is a Holding With No Items Considered Finished?

No. It appears in the holdings-without-items count. The planner cannot know what work you omitted. Decide what needs to be recorded for that holding before drawing a conclusion from the entered plan.

### Will the Plan Remain Here When I Return?

There is no automatic saving or account storage. Download the full text or JSON before leaving or refreshing. There is no import feature, so retain the export as a separate reference. Starting a new plan also clears the page after confirmation.

## About Sequoia Research

Sequoia Research, LLC provides independent research on DSTs and other real estate investment offerings. This educational library explains how to inspect sources, compare investment terms, and separate supported facts from open questions. This tool and guide provide general research education, not individual investment, legal, or tax advice.

## Sources

- [FINRA Notice 19-10: Customer Communications Related to Departing Registered Representatives](https://www.finra.org/rules-guidance/notices/19-10), April 5, 2019; relevant current guidance read October 17, 2026.
- [FINRA Rule 2273: Educational Communication Related to Recruitment Practices and Account Transfers](https://www.finra.org/rules-guidance/rulebooks/finra-rules/2273), current rule text; effective November 11, 2016; read October 17, 2026.
- [SEC Guide to Relationship Summaries](https://www.investor.gov/CRS), undated current guide; read October 17, 2026.