Tool & guide

DST Due Diligence: Final-Document Change Checklist

By Sequoia ResearchPublished Read as Markdown

DST Due Diligence: Final-Document Change Checklist

Users compare the decision-stage document set with the final available versions and record material changes. The checklist links each change to affected assumptions and unresolved professional questions.

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 tool helps you compare an earlier document set with the final set available for your review. You record changes, missing documents, affected assumptions, and questions for the right review role. The guide explains how to use the checklist without mistaking a completed form for verified terms or investment approval. Each export keeps the entered records and their saved revision history.

Table of Contents

What a Final-Document Review Can Establish

A Delaware statutory trust, or DST, review may begin with one version of a document and proceed after another becomes available. This checklist helps you record the difference between those two sets. It does not decide which document legally controls or whether the final set is complete.

The phrase “final-available” means the set you identify at your chosen review date. A later amendment, exhibit, signature page, or corrected schedule may still exist. A label in this tool cannot establish that no further change is possible.

The Financial Industry Regulatory Authority, or FINRA, discusses new material developments and the need for primary-record review in its private-placement guidance. It also cautions covered firms about offering schedules that leave too little time for proper investigation. Those duties depend on the firm's role and facts. This checklist does not certify that any person or firm has met them. FINRA Regulatory Notice 23-08

The tool organizes a manual comparison. It does not upload documents, run text comparisons, search a portal, contact a sponsor, or determine materiality. You supply every reference, description, judgment, and response. The summary counts reflect only the records you enter.

Use the result as a record of what you compared and what still needs attention. Keep the actual documents in an appropriate separate location. Short file names, version labels, and page references are enough for this tool. Avoid placing confidential investor details or full private documents in its text fields.

Define the Offering and the Two Document Sets

Start with the exact offering and class identity. A similar product name does not establish that two packets govern the same interest. State the relevant class, series, or other scope in plain language so later readers know what was compared.

Name the earlier set and its version. Then enter the date you reviewed that set. Name the final-available set and enter the final review date. Include source document dates in the packet labels or row references where useful. Document dates and your review dates are different facts.

The two review dates must be real dates from 1900 through today's UTC date. UTC is the time standard the tool uses for this limit. The final review date cannot precede the earlier review date. The date checks only validate the entered timeline; they do not prove that the documents were available then.

Once the first record is saved, the identity, packet labels, title, and review dates are locked. This prevents old findings from silently carrying into a newly named offering or packet. If the scope changes, export the old comparison and start a new one.

The lock does not prove that the original scope was correct. Check it before saving. A typo discovered later may require a fresh comparison. Keep the old export with a clear note about the correction instead of treating the two records as the same untouched review.

A later final packet deserves its own comparison. You might use the previous final set as the next earlier set, but that choice is yours. The tool does not merge reviews or infer that a prior answer applies to revised terms.

Record the Earlier and Final Evidence

Each record addresses one document, clause, or other defined check. Choose an affected topic, such as debt, fees, reserves, or investor rights. Then name the document and identify the earlier source or the request for a missing earlier document.

Summarize the earlier wording or unresolved starting fact. For a compared item, supply the final reference and final summary as well. Keep the summaries short and faithful to the stated scope. If you compare only one fee row, do not describe the whole fee schedule as unchanged.

Record the comparison method and its limits. You may have read two clauses manually, checked two table rows, or found that an exhibit was unavailable. Explain which pages and versions were used. The tool cannot verify that your description matches the underlying files.

Choose among four comparison labels. “Change recorded” means you entered a difference. “No change found” means no difference was found within your stated scope. “Not yet compared” means the review remains incomplete. “Final document missing” means the required final document was not available for this check.

A compared record requires both a final source reference and final summary. A missing-final record requires those two fields to stay blank. Describe the missing request in the comparison-basis field. This keeps a request for evidence from looking like evidence already received.

Do not use a blank summary as shorthand for zero cost or no obligation. Missing information is a different condition. If the terms state zero, record that statement and its source. The tool preserves your wording but does not decide whether the source supports it.

Separate a Change From Its Effect

A wording change and a financial or legal effect are different findings. The checklist records both, because neither can safely be inferred from the other. A small text change can matter, while a large formatting change may leave the reviewed economics unchanged.

Choose an impact label separately from the comparison label. You can leave the effect unassessed, identify an effect or follow-up, or record that no effect was found within the stated review. Describe the assumptions affected and the limits of that judgment.

For example, a fee rate may change while the applicable payment base remains uncertain. Record the changed rate, then identify the question about the base. Do not turn a correct rate comparison into a complete fee calculation without the missing amount and terms.

Consider a separate fictional fee illustration. A rate changes from 0.50% to 0.75% on an assumed $400,000 investment base. The modeled fee rises from $2,000 to $3,000, a $1,000 difference. The rate rose by 0.25 percentage points, or 50% relative to the earlier rate. These calculations are explained here; the checklist does not calculate fees.

The example says nothing about who pays, whether a waiver applies, or which document controls. Those questions require the actual terms. A recorded response should identify its source and scope rather than simply say “approved.”

A no-effect judgment still needs a reason. The tool requires affected-assumption notes for every record. If you choose no follow-up, it also requires a dated rationale and supporting reference. That requirement improves the record; it does not validate the judgment.

Keep Missing Documents and Open Questions Visible

A missing or unreviewed document cannot be marked as having a resolved impact in this checklist. Its impact must stay unassessed, and its action must stay open or waiting. You must also record the question and a responsible review role.

Use roles such as loan-document reviewer, tax adviser, or investor review lead. A role identifies who should assess the question. It does not mean that the person has been contacted or accepted the work. The tool sends no messages.

A chosen follow-up date is optional. It can be a real date from 1900 through 2100, including a future date. It is a planning entry, not a legal deadline, reminder, or automatic calendar event. The tool does not mark a question resolved because that date has passed.

The Securities and Exchange Commission, or SEC, warns that private placements can provide limited information and that offering documents generally are not reviewed by regulators. A document's title or delivery does not make its claims verified. If important evidence remains missing, the checklist should show that gap. SEC Private-Placement Bulletin, Updated September 21, 2026

“Response recorded” means you entered a reply and its supporting reference. It does not mean the reply is accurate, legally sufficient, or accepted by every adviser. Its date cannot follow the final review date. Keep an unassessed impact visible even if a response has arrived but has not settled the effect.

If later information reopens a question, revise its action to open or waiting and explain why. A prior response can remain in the saved history. Do not hide the unresolved issue merely because someone answered an earlier version of the question.

Follow the Fictional Alder Example

The example concerns invented Alder DST, Class A. Its earlier training packet is labeled October 1, 2026 and was reviewed October 10. Its later training packet became available October 15 and is reviewed October 17. These are fictional records, not observations about an actual offering.

The first record compares the fee clauses described above. It initially has an open question about whether the changed fee applies to the selected class. A second save records a fictional response with a source pointer. The earlier open version remains in the history, while the current record shows the response.

The second record concerns a missing final loan exhibit. An earlier summary exists, but the final exhibit has not been received in the example. The record stays waiting, with impact unassessed. The presence of an earlier summary does not satisfy the missing final-document check.

The third record compares two insurance-budget rows. Both show $120,000. The reviewer records no change in that line and no follow-up needed for that narrow comparison. The notes expressly exclude verification of an insurance policy or current insurer quote.

The example therefore has three active records and four saved events. Two records were compared: one has a change and one has no change found. One final document is missing. There is one unassessed impact, one open-or-waiting action, one response recorded, and one no-follow-up judgment.

These categories overlap. The missing loan exhibit is also the unassessed and waiting item. Adding those counts would count that record more than once. The tool does not add them into a risk score or estimate the chance that the investment is suitable.

Revise, Archive, and Restore Records

Editing a saved record appends a revision when you save it. It does not erase the earlier saved wording. A record's revision number rises when its data are revised. The full entered history shows the create and revise events in sequence.

Archiving removes a record from the active summary but keeps it in the saved dataset and exports. It does not resolve the issue or declare it unimportant. Use a reason in the record before archiving if a later reader needs to understand the choice.

Restoring brings the same record back into the active review. Archive and restore events do not change the record's data revision number. They show a change in its active state. An archived record must be restored before it can be revised.

Archive, restore, loading the example, and starting a new comparison use confirmation controls inside the page. Cancel keeps the existing work. Switching to another saved record also asks before replacing unsaved editor fields. Changes to the form cancel an outdated pending confirmation.

Unsaved edits disable exports and prevent preparing a review. Save or clear the editor first. A rejected save leaves saved records unchanged. This protects the current dataset from a partial entry, but it cannot recover unsaved text after you close or reload the page.

History here means the versions entered during this page session. It is not a secure audit system, a timestamp service, or proof against alteration after export. Keep appropriate source records separately when formal recordkeeping is required.

Read the Counts Without an Approval Score

The summary counts active and archived records, compared items, changes, missing documents, unassessed impacts, and action labels. Each count has a defined meaning. None establishes completeness of the underlying document set.

One critical missing exhibit can matter more than many minor comparisons. For that reason, the tool does not turn three completed checks out of four into a diligence grade. It also does not assign a numerical weight to an issue or tell you whether to invest.

The display filter can show all records, active items needing attention, or archived records. The attention view includes active open or waiting actions and active unassessed impacts. A response-recorded item can still appear there if its effect remains unassessed.

Changing the filter does not change the dataset, summary, or export scope. The full export always includes every saved record and event. This prevents a filtered screen from becoming an incomplete file that looks like the entire review.

Export the Full Review and Preserve Its Limits

Select Prepare full review after saving or clearing edits. Then choose the JSON or text download. On the published page, use the outer Save file control that appears after selecting Download. The JSON file supports structured review; the text file presents the same entered scope, records, counts, and history for reading.

There is no import, automatic saving, cloud account, or background monitoring. Save an export before leaving the page or starting a new comparison. The checklist does not restore a file into the form. Retained files are for reading and separate recordkeeping.

The tool allows at most 40 records, including archived records, and 160 saved events. Text fields have length limits. The saved input is limited to 180,000 UTF-8 bytes and each export to 500,000 bytes. Long notes can reach a byte limit before the record limit. A rejected change preserves the last saved state.

Keep references concise and use separate comparisons for separate scopes. The limits are software boundaries, not a suggested amount of diligence. A short, well-sourced record can be useful; a large completed checklist can still miss an important question.

FAQ

Does the Tool Compare Uploaded PDFs?

No. It has no upload or file-reading function. You compare the documents yourself and enter the relevant findings. The tool validates the structure of those entries, not their truth.

Does Final-Available Mean Legally Final?

No. It means the set identified by the user at the review cutoff. The tool does not determine which document controls or whether later amendments exist. That question remains part of the actual review.

Can a Missing Final Exhibit Be Marked Complete?

No. A missing-final record must remain unassessed and open or waiting. You can revise it when the evidence becomes available and has been compared. Merely receiving a file does not complete that work.

No. It records one user-entered reply and source. The reply may leave the effect unassessed or require more work. Reopen the action when needed and keep the new reason in the record.

What Happens to Archived Records?

They leave active counts but remain in the full dataset and exports. You can restore them through confirmation. Archiving is not an approval or a finding that the issue no longer matters.

Will the Follow-Up Date Send a Reminder?

No. It is a date in the record only. The tool does not contact the assigned role, create a calendar event, or monitor the question. Use a separate authorized process for reminders.

Can I Change the Offering After Saving?

The comparison scope locks after the first record. Export the existing work and start a new comparison for a different offering, class, packet, or review date. This prevents findings from silently carrying into another scope.

About Sequoia Research

Sequoia Research publishes educational articles and tools for reviewing DST investments and their source evidence. This checklist helps organize manual document comparisons and follow-up. It does not provide legal advice, verify a specific offering, or issue an investment approval.

Sources