Canonical page: https://sequoia-research.com/writing/delaware-statutory-trust-1031-reviews-document-version-impact-tracker
Author: Sequoia Research
Published: 2026-10-17T10:49:49.653Z
Updated: 2026-10-17T10:49:49.653Z
Interactive tool: https://sequoia-research.com/writing/delaware-statutory-trust-1031-reviews-document-version-impact-tracker#research-tool

# Delaware Statutory Trust 1031 Reviews: Document-Version Impact Tracker

## What Is This Article About?

This tool links a changed document provision to the earlier review items that may need new work. You enter one earlier document, one newer document, and the conclusions or open questions affected by the change. The map separates a response received from a reviewed update and flags prior reviews when the document context changes. This guide explains the fields, the grouping rules, and the limits of what those labels can prove.

## Table of Contents

- [What the Document-Version Impact Tracker Does](#what-the-document-version-impact-tracker-does)
- [Start With the Correct Document Pair](#start-with-the-correct-document-pair)
- [Link a Change to an Earlier Conclusion or Question](#link-a-change-to-an-earlier-conclusion-or-question)
- [Read the Review Labels and Date Checks](#read-the-review-labels-and-date-checks)
- [Follow the Fictional Five-Link Example](#follow-the-fictional-five-link-example)
- [Understand What Happens When the Document Context Changes](#understand-what-happens-when-the-document-context-changes)
- [Use the Map in a DST Review Meeting](#use-the-map-in-a-dst-review-meeting)
- [Save, Filter, and Export the Complete Record](#save-filter-and-export-the-complete-record)
- [Limits of the Analysis](#limits-of-the-analysis)
- [FAQ](#faq)

## What the Document-Version Impact Tracker Does

A new supplement can change a number without answering every question that used it. This tracker helps you follow that change into the review. It records which earlier item relied on the old information, what changed, and what the reviewer did next.

The tool does not read a PPM, compare files, or locate amendments. A private placement memorandum, or PPM, describes an offering and its risks. You must obtain the documents, read the provisions, and decide which review items may be affected.

Each saved row is an **impact link**. It joins one change to one earlier conclusion or open question. If a reserve change affects both a cash test and a repair-budget question, enter two links under the same change key. This keeps the two tasks visible without pretending they have the same answer.

The output shows work still needing review, work marked reviewed, and links to open questions. It also groups matching change keys. Those counts organize the record. They do not rate an investment or show that a complete review has occurred.

That boundary matters with private offerings. The SEC explains that disclosure may be limited and that PPMs generally are not reviewed by a regulator. Receiving a revised document does not establish that its facts or terms have been independently verified. [SEC private-placement bulletin](https://www.investor.gov/introduction-investing/general-resources/news-alerts/alerts-bulletins/investor-bulletins/private-placements-under-regulation-d-updated-investor-bulletin).

## Start With the Correct Document Pair

Enter the case title and exact issuer and interest. A sponsor name alone may cover several different offerings. Use the identity needed to connect this record with the documents and earlier review.

Next enter the earlier document reference, its issue date, and the date of the earlier review. Then enter the newer document reference and its issue date. A reference may be a file name, a document title, a saved message, or a link. The tool keeps it as text. It does not open the source.

Blank source fields remain missing. You can begin a needs-review map before every reference is available. You cannot save a new reviewed label without both document references, both issue dates, and the earlier review date.

The review cutoff must be no later than the current UTC calendar date. UTC may differ from the date on your local clock near midnight. All document, earlier-review, and response dates must be real dates from 1900 through 2200 and cannot follow the cutoff.

When both issue dates are entered, the newer document cannot have an earlier issue date. The earlier review cannot predate its own document. These checks catch simple ordering errors. They do not prove that the document is the latest version or that it applies to this investor.

An issue date is also different from an effective date. A document issued today can describe a future change. The tracker does not calculate that change's legal effective date. Explain any such condition in the provision summary or remaining limits, and have the responsible professional address it.

Use one document pair per map. If several separate supplements need review, preserve a separate export for each pair or make clear which combined package each reference names. The tool has no document library or automatic version chain.

## Link a Change to an Earlier Conclusion or Question

Give the change a short key, such as “Reserve amount.” Keys group after spaces at the edges are removed and repeated spaces inside the text are reduced to one. Letter case still matters: “Reserve amount” and “reserve amount” form different groups.

Use a key only when you intend the links to be discussed together. Matching words do not prove that the same legal provision is involved. Two unrelated changes can have similar descriptions.

Choose the review area: investment or exchange transaction. Then identify the earlier item as either a conclusion or an open question. Copy a concise description of that item and record where it appeared in the earlier review.

Enter the old and new provision locations and summaries. Include enough context to avoid changing their meaning. A page reference without the relevant section can be hard to follow; a summary without a location can be hard to verify.

State the expected effect on this specific review item. “Reserve changed” repeats the source. “Recheck the cash available after the planned work” describes the work that the change may require. The expected effect is your analysis, not a result generated by the tool.

Finally, choose whether the link needs attention before the decision or is a follow-up. This priority is yours to set. It is not a legal deadline or an automatic finding that the issue is material.

You may save up to 20 links. Stable link IDs remain attached to their rows when another row is removed. The tool does not renumber surviving IDs or treat their number as a rank.

## Read the Review Labels and Date Checks

Four labels describe the recorded work. Their meaning is deliberately narrow.

| Label | Meaning in the map |
|---|---|
| Needs review | The entered impact still needs review work. |
| Response recorded | A response has been entered, but the link has not been marked reviewed. |
| Reviewed — update recorded | You recorded a reviewed change to the earlier item. |
| Reviewed — no update recorded | You recorded a review that did not change the earlier item. |

A response label requires response text. A reviewed label also needs the earlier-review location, both provision locations and summaries, the expected effect, the review response, reviewer name and role, and response date. You must confirm that you matched the change to this exact earlier item.

When saving a reviewed link, its response date must be on or after both the new document's issue date and the earlier review date. It also cannot follow the cutoff. A missing or out-of-order date prevents that new reviewed label from being saved.

For an exchange-transaction link, you must also record your confirmation that the answer came from the professional responsible for the issue. That checkbox records your statement. The tool does not check a license, contact the person, or approve the answer.

A reviewed label can still point to an open question. For example, a new reporting date may leave the question “Who receives the report?” unchanged. The date review is complete while the recipient question remains open. The output keeps that distinction visible.

FINRA's private-placement notice discusses independent investigation and careful review of third-party reports for the firms it covers. It also addresses follow-up when a report is incomplete or inconsistent. Those responsibilities are not satisfied by selecting a label in this tool. [FINRA Regulatory Notice 23-08](https://www.finra.org/rules-guidance/notices/23-08).

## Follow the Fictional Five-Link Example

The example uses a fictional Oak Terrace document pair. The original document is dated October 1, 2026, the earlier review October 8, and the supplement October 14. The cutoff is October 17. Nothing in the example describes an actual DST.

The first two links use the key “Reserve amount.” Link L1 records an updated cash-buffer review after an opening reserve changes from $800,000 to $650,000. Link L2 remains a response-only item because the remaining-work budget has been requested but not supplied.

The reserve falls by $150,000, or 18.75% of the original amount. That arithmetic does not establish whether the new reserve is enough. The map does not calculate reserve adequacy or infer the missing budget.

L3 links “Closing amount” to the earlier funding plan and still needs review. L4 links “Reporting date” to an open question about who receives a report. It records no update to that question, which remains open. L5 uses “Closing amount” for a separately reviewed purchaser-identity check.

The base output has five impact links under three change keys. Two links need review, and both are marked before-decision items. There are two open-question links, one of which has a reviewed label. That last count does not mean one question has been answered.

The two “Closing amount” links have different old and new provision descriptions. The tool flags that group for a label check. This could be an overly broad key, or the user may deliberately group related work. The text difference does not prove a source contradiction.

Filtering to “All needing review” shows L2 and L3. The summaries and exports still include all five rows. A filtered view is a way to focus a meeting, not a smaller underlying record.

## Understand What Happens When the Document Context Changes

When you save a reviewed link, the tool stores a small context record with it. That record contains the issuer and interest, both document references and issue dates, and the earlier review date. It allows a later build to notice when those fields no longer match.

If one of those fields changes, a previously reviewed link returns to the needs-review count. Its earlier label, response, reviewer, and notes remain in the record. You can inspect what the prior review said without treating it as a review of the new context.

For example, change the newer document reference in the five-link example. Three links had reviewed labels. All three now need renewed review, joining the two links that already needed work. The map therefore shows five links needing review, four of them before-decision items.

The tool does not know whether the new reference changes the investment. Even a corrected file name triggers the context check. Review the reason for the change, then edit and save each affected link with the appropriate response. Saving a reviewed link records the current context after its required fields and dates pass.

A changed title or later cutoff alone does not change the stored document context. Those fields do not identify the document pair. A later cutoff can change whether a chosen follow-up lies before, on, or after the cutoff.

This is not an audit trail of every edit. Each row holds its current data and the context from its last saved reviewed label. Editing the row replaces its prior contents. Export dated copies if you need to preserve earlier states, and retain the original source files elsewhere.

## Use the Map in a DST Review Meeting

Begin with the links that need review before the decision. For each one, open the actual source and earlier memo. Check whether the entered summary still matches the full provision and whether any conditions were omitted.

Then ask what the change affects. A new reserve figure may alter a cash test. A changed purchaser name may require a transaction check. A revised payment date may affect a household budget without changing the annual total.

Keep those paths separate even when they share one source. The investment reviewer and exchange professional may need different facts and may reach different conclusions within their own scope.

Record the response and any remaining conditions. A professional may confirm one point while leaving another unresolved. Enter the narrow answer rather than turning it into a broad “everything is approved” statement.

Next steps should name the work and the person responsible. “Obtain the dated repair budget” is more useful than “follow up.” The optional follow-up date is a planning date chosen by the user. The tool labels it before, on, or after the review cutoff; it does not declare a legal default.

The exchange calendar has its own rules. The IRS's 2025 Form 8824 instructions discuss identification within 45 days after the relinquished-property transfer and receipt by the earlier of 180 days after that transfer or the transfer-year return due date, including extensions. The tool does not calculate those deadlines or determine whether an amendment changes a valid identification. [IRS Form 8824 instructions](https://www.irs.gov/instructions/i8824).

## Save, Filter, and Export the Complete Record

Save each impact link before building the map. An unfinished new row or edit blocks the build, so the output cannot silently omit that work. You can clear the unfinished form after confirming that choice; saved rows remain.

Removing a row requires confirmation within the tool. If that row is being edited, its unfinished edit is removed too. Unrelated unfinished work remains in the form. Loading the example or clearing the entire map also requires confirmation. Cancel preserves the saved rows and the unfinished form.

Any input change clears the current results and disables exports until a fresh build. Editing also cancels a pending replacement confirmation. Display filters do not change the inputs or the full export.

The JSON export includes all entered fields, stored review contexts, calculated groups, and counts. The text export provides the same complete map in a readable form. Both retain all saved links, even when only one status or review area is displayed.

The saved map has a 60,000-byte UTF-8 limit. UTF-8 is the text encoding used to measure the actual data size; some characters take more than one byte. An over-limit save is rejected without replacing the saved map. Each export is limited to one MiB. These limits control file size, not the quality of the review.

Nothing is saved automatically. The tool has no account, source fetching, import feature, or browser storage. Keep exported copies in your own approved location and protect any private facts they contain. Do not expect the tool to restore a record after closing the page.

## Limits of the Analysis

The map covers only the links you entered. An empty review area is not evidence that the amendment has no effect there. A zero needs-review count does not show that every changed provision was found.

Grouping is based on user labels. Different keys can refer to the same change, and one key can cover unrelated changes. The description-difference flag asks for a grouping check; it does not decide which text is correct.

The tool checks required fields and date order. It cannot judge the source's authority, the completeness of a summary, a reviewer's competence, or the legal effect of a provision. Keep those judgments with the people and evidence needed to make them.

## FAQ

### Does the tool compare two PDFs for me?

No. You read the documents and enter the changed provisions. The tool maps those entries to earlier review items. It neither extracts text nor finds changes that you missed.

### Can one change affect several review conclusions?

Yes. Save one link for each affected conclusion or open question, using the same change key where appropriate. The group shows all linked IDs and the ones still needing review. Their answers can remain different.

### Does “Reviewed — no update recorded” mean the investment is approved?

No. It means you recorded a review that left the earlier item unchanged. The item may itself be an open question or a conditional conclusion. Read the response and remaining limits rather than treating the label as approval.

### Why did reviewed links return to Needs review?

One of the stored document-context fields changed. The tool preserves the prior response but no longer treats its reviewed label as current for that context. Check the new document pair and save each affected review again when the work is done.

### Can a missing document date be left blank?

Yes, while building an unresolved map. A newly saved reviewed label requires both document dates, both references, and the earlier review date. A blank stays missing; the tool does not replace it with today's date.

### Does a filtered export omit the other links?

No. Filters affect only the displayed rows. JSON and text exports keep the full saved map, all groups, and all conditions. Save dated copies if you need a record of how the review changed over time.

## About Sequoia Research

Sequoia Research, LLC provides independent research on DSTs and other real estate investment offerings. This educational library helps readers connect investment claims and review conclusions to their supporting documents.

## Sources

- [SEC private-placement bulletin](https://www.investor.gov/introduction-investing/general-resources/news-alerts/alerts-bulletins/investor-bulletins/private-placements-under-regulation-d-updated-investor-bulletin), August 17, 2022; updated September 21, 2026.
- [FINRA Regulatory Notice 23-08](https://www.finra.org/rules-guidance/notices/23-08), May 9, 2023.
- [IRS Form 8824 instructions](https://www.irs.gov/instructions/i8824), 2025 edition.