Tool & guide

1031 Exchange DST Brokers: Offering Amendment Review Queue

By Sequoia ResearchPublished Read as Markdown

Offering Amendment Review Queue

Users manually reference successive document versions and record changes to terms, assumptions, or availability. The queue retains review history and flags earlier conclusions for recheck when a later version is added; it does not upload or read documents.

For an export, select Download in the tool, then Save file when it appears below. Your entries stay in your browser.

What Is This Article About?

This guide explains how to track changes in a Delaware statutory trust (DST) offering packet. The tool links each change to two document versions and keeps the review notes that follow. When you add a later version, earlier conclusions need another check against that version. The queue helps organize that work without claiming that the offering is approved or that every change has been found.

Table of Contents

Why DST Offering Amendments Need a Separate Review

An offering can change while an investor is reading it. A new debt term may change cash available for distributions. A revised allocation note may change how much appears available. A new form may ask for information that the first packet did not request. These examples call for different questions, even when they arrive in the same email.

A prior review is useful evidence of earlier work. It should still identify the documents it covered. Otherwise, “reviewed” may refer to a packet that is no longer the one being considered. This queue makes the version boundary visible. It keeps the old conclusion and shows when a later packet needs another check.

FINRA's private-placement guidance addresses a broker's reasonable investigation when recommending a security. This reader worksheet does not perform that investigation, replace the broker's process, or establish that any firm's duties have been met. It gives you a way to record questions about changed facts and discuss them with the responsible people. FINRA Regulatory Notice 23-08.

A current public contract offers a concrete example of why the timing matters. Section 5.1 of Blue Owl's June 26, 2026 DST dealer manager agreement addresses a suspension while certain memorandum changes are prepared, followed by instructions to resume sales. Those are terms of that agreement. They are not a rule that every amendment to every DST always stops sales. Blue Owl agreement, Section 5.1.

The tool does not decide whether an amendment is legally material or whether sales may resume. If either issue is open, record it as a question and obtain a scoped answer. A new file in an inbox does not answer the question by itself.

Define One Offering and Document Scope

Start with the exact offering identity and the scope you intend to review. Include the interest class if it matters. State whether the queue covers the offering memorandum and supplements, a sales packet, or another defined set of documents. Do not combine unrelated DSTs because they share a sponsor or broker.

The identity and scope lock after you save the first version. That keeps existing conclusions from appearing under a new offering name. If you made an identity error, download the record and use Start new queue. The tool has no rename function for a saved offering.

Set the board review date. It cannot be later than today in UTC. Document receipt and review-entry dates must fall on or before that date. This allows an earlier review cutoff, but it prevents later evidence from quietly appearing in that earlier record.

Keep investor account details out of the scope field. A short description such as “Willow Court DST, class A, packet and supplements” can identify the work without a tax ID or payment instruction. Names and source references stay in the browser unless you download them.

Record Successive Document Versions

Each version needs a distinct label, document date, received date, and source reference. The document date cannot follow the received date. Versions must be added in the order of their received dates, with equal dates allowed. A later received packet can carry an older document date; ask why rather than changing the printed date to make it look newer.

The tool assigns V1, V2, and later IDs in order. These labels describe your record. They do not establish which document legally replaces another. A supplement may add to an earlier memorandum rather than replace it. Your source reference should identify the base packet and added document when both are needed.

For example, V2 might mean “October 12 supplement read with the October 10 memorandum.” A standalone filename called “final” says much less. Describe the packet well enough that another reader can locate the same materials and understand what you compared.

You can save up to eight versions. They are fixed after saving and cannot be removed. This protects the links from each change and review note back to its source version. If a version reference is wrong, export the old queue and start a corrected one. The exports do not include the underlying files, so retain those files separately.

No document is uploaded, opened, scanned, or compared by this tool. The manual source field can contain a filename, page reference, or document location. The tool treats it as text. It does not know whether the reference exists, is complete, or belongs to the named offering.

Describe the Change Before Choosing a Status

Save at least two versions before adding a change. Select the later version in an adjacent pair. Choosing V3 creates a comparison from V2 to V3. This structure keeps a sequence of changes visible instead of jumping over an intermediate packet without notice.

Give the change a clear topic. “Loan interest rate” is easier to work with than “debt changes.” Select a category, enter the earlier and later wording or assumption, and provide page or section locations for both. The categories cover terms and fees, debt and assumptions, availability, ownership and exit, and other issues.

Keep one main issue in each item. A supplement could change both the loan rate and the reserve schedule. Two rows make it easier to record who checked each one and whether either remains open. Putting both in one row can hide a partial answer under a broad review label.

Use short paraphrases with exact numbers where needed. The fields are not intended to hold complete contracts. If a comparison depends on a definition, condition, or footnote, include its locator and explain the condition in the review note. The software does not inspect omitted text.

You can save up to thirty change items. The same topic cannot appear twice for the same transition after spaces and letter case are normalized. That check reduces accidental duplicates. It cannot detect different labels describing the same issue, so read the queue for overlap before sharing it.

Separate Clarification From a Fresh Investment Decision

A review entry needs a reviewer and role, date, evidence reference, and short conclusion. Each entry applies to the latest version then recorded in the queue. The reviewer name is an unverified statement entered by the reader. It is not a signature, credential check, or proof that the person agreed to the description.

Choose Clarification needed when an important fact remains unclear. An example is a new hold end date with no stated time zone. Record what must be answered and who you intend to ask. Merely receiving another document does not resolve that question.

Choose Fresh decision needed when the fact is understood but its effect still needs a decision. A higher debt payment may be clear while the choice to proceed remains open. The entry should explain the decision at issue and the source of the changed fact. The tool does not decide whether the new terms fit a particular investor.

Choose Review recorded when the specified review has been documented for the latest recorded packet. Describe its actual scope. “Checked the interest calculation” is narrower than “approved the investment.” The output preserves that note so a limited check is not silently presented as an overall recommendation.

Choose Out of scope recorded when the issue falls outside this defined review. Give a reason and evidence reference. This status keeps the item and its history. It does not erase a risk, show that another person handled it, or prove that the topic does not matter to the investment.

Understand the Latest-Version Rule

An entry applies to the version named in that entry. Once you append another version, a change with an earlier review becomes Recheck after later version. Its previous status, reviewer, note, date, and evidence remain in the history. The old statement is no longer counted as a review of the latest packet.

This rule is intentionally broad. A new version might only correct a spelling error, but the queue cannot read it and prove that nothing else changed. Rechecking is a workflow prompt, not a conclusion that every earlier term was amended. A new review note can explain that a particular issue was checked and remains unchanged.

An item with no review entry stays No review entered. An item with a current review uses that entry's chosen status. If several reviews exist for the same current version, the last saved entry controls the displayed status. All earlier entries remain available in entered order.

Review dates cannot precede receipt of their target version or move backward from an earlier review of that item. They cannot follow the board review date. Equal dates are allowed; entry order then shows which statement was added last. These calendar checks do not establish a precise time sequence within a day.

Work Through the Fictional Amendment Example

The built-in example concerns an invented Willow Court DST. V1 is an initial packet, V2 is a debt supplement, and V3 is a revised allocation notice. All source references, reviewer roles, dates, and terms are fictional. They show the method without describing an available investment.

The first change concerns a $12 million interest-only loan. The annual rate moves from 5.5% to 6.0%. Annual interest rises from $660,000 to $720,000, a $60,000 increase. That is a half-percentage-point rate change. It is not a claim about an investor's after-tax return or every cost in the offering.

A review of that calculation was entered for V2. After V3 is added, the first item requires recheck. The calculation note still exists. The queue simply does not assume that someone checked the debt terms in the latest packet. That person would need to add a review entry for V3.

The second change concerns a reported hold end time. It moves from October 20 to October 18, both at noon Pacific. A clarification entry for V2 remains in the history. A later entry for V3 still asks which conditions apply. The current status is therefore Clarification needed, rather than a historical conclusion carried forward without review.

The third change concerns an indicated amount dropping from $300,000 to $200,000. The difference is $100,000, or one-third of the earlier indicated amount. Neither amount is described as reserved. No review has been entered for this item, so it stays open.

The loaded queue has three versions, three change items, and three review entries. Its current groups are one recheck, one clarification, and one item without a review. All three are open. The count of three review entries does not mean three issues have been settled; two entries concern the same hold question.

Read the Queue Without Creating a False Approval Score

The summary reports entered items by their latest status. Open items combine No review entered, Recheck after later version, Clarification needed, and Fresh decision needed. Review recorded and Out of scope recorded are separate groups. They are excluded from the open count, but neither means investment approval.

The queue also shows the number of entered changes for each adjacent version pair. A pair with zero rows has no comparison items in this record. That is not evidence that the documents are identical. A pair with several rows is not proof that all changes were found.

Do not turn the group counts into a percentage of investment readiness. One unanswered exit provision can matter more than several checked arithmetic items. The software has no basis to weigh those questions. Its useful output is the specific topic, source version, review history, and next question.

Private placements may involve limited disclosure and difficult resale. The SEC's current bulletin explains those risks. Completing this queue does not supply missing documents, create liquidity, or remove the need to understand the investment itself. SEC private-placement bulletin.

Keep Review History and Correct Mistakes

Saved versions and change descriptions are fixed. Review entries are added to the record, not overwritten. You can keep up to ten entries per change. To correct a review conclusion, add a new entry for the latest version that states what was wrong and what the new evidence supports.

For a wrong offering, source-version identity, or change description, download the old record and start a corrected queue. Do not add a misleading later review just to hide the original error. The new queue should clearly identify its scope and the documents it uses.

Each form must be saved or cleared before another form is saved or the queue is reviewed. Changing a field clears the prior results and disables downloads. A failed save leaves saved records unchanged. This reduces the chance that an old result will look as though it includes an unfinished entry.

Loading the example or starting a new queue requires confirmation. Cancel keeps the existing work. A later input change cancels a pending replacement. Saved data is limited to 200,000 bytes, and full downloads have a 1 MiB limit. Keep notes brief and preserve the detailed source files outside the tool.

Export a Useful Record for Your Next Discussion

You can export after saving the first document version. With fewer than two versions or no change items, the result is labeled a preliminary record. Its empty change count does not show that a comparison was completed. This lets you keep early work before correcting or expanding the queue.

JSON and text downloads retain every saved version, change item, and review entry. They also include the latest target, group counts, and comparison coverage. An older review remains visible even after a later version makes it require recheck. The exported record is not a signed attestation or an authenticated audit log.

The tool has no automatic storage, import, alerts, or contact with a broker. Refreshing or closing the page can lose the working queue. Save a download before leaving and keep it with the source documents. In the embedded tool, a separate Save file button may appear after you request a download.

For the next discussion, identify the latest packet and the open questions that could change the decision. Ask for answers tied to the actual document version and stated scope. If another version arrives, add it before treating earlier review entries as current. The point is to make the basis of the discussion clear enough to check.

Frequently Asked Questions

Does the tool find changes in uploaded documents?

No. It accepts manual document references and change descriptions. It does not upload, read, or compare files. Keep the underlying documents separately and use their actual page or section locations.

Why does a later version reopen a reviewed item?

The earlier entry covered an earlier target. The tool cannot prove that the new packet leaves that issue unchanged. It preserves the old entry and asks for a new check against the latest recorded version.

Is Review recorded the same as approval to invest?

No. It records the limited review described in the note. It does not establish suitability, legal materiality, available capacity, subscription acceptance, or tax treatment. State the scope so another reader can see what was actually checked.

Can a supplement be added without replacing the whole memorandum?

Yes. Use a version label that identifies the base packet plus the supplement. The sequence is your comparison record. It does not determine the legal effect of the supplement or which documents remain operative.

Can I change an earlier review note?

Add a new entry rather than overwrite it. The latest entry for the current version controls the displayed status. Earlier entries remain in the history. A new version makes that current conclusion require recheck again.

Can I use the export as proof that the broker did the review?

No. Reviewer names and conclusions are entered by the user and are not verified. The export organizes a discussion and preserves the entered record. Obtain the appropriate confirmation from the actual person and firm.

Does a queue with no open items mean the packet is complete?

No. It only describes the items you entered. Unidentified changes and missing documents remain outside that count. Review recorded and out-of-scope entries still need to be read for their limits.

About Sequoia Research

Sequoia Research, LLC provides independent research on DSTs and other real estate investment offerings. This educational tool helps readers keep offering changes, document versions, and reported review conclusions connected.

Sources