Tool & guide

Inland DST Reviews: Trust Update and Amendment Log

By Sequoia ResearchPublished Read as Markdown

Trust Update and Amendment Log

Users maintain a dated index of reports, amendments, notices, and open questions for one identified trust. The log links each new item to the portion of the existing review that may require revision.

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 a tool for keeping new reports, amendments, notices, and open questions tied to one Delaware statutory trust, or DST. Each document can point to the part of an existing review that may need another look. The log keeps the date of a document separate from its receipt, stated effective date, and the reader's review action. It organizes your entered records without deciding which contract controls or whether the investment is sound.

Table of Contents

What Belongs in a DST Update Log

A new report may answer an old question while raising another one. An amendment may change a single fee line. A notice may provide a new contact but leave the payment instructions unchanged. A useful log records the narrow change and the work still needed.

This tool accepts up to thirty manually entered document records. You can classify each as a report, amendment, notice, requested record, or other item. No Inland documents are loaded into the tool. The name in the title identifies the research subject; it does not imply access to a sponsor's private files or an endorsement.

The tool works as an editable index. It does not hold the original files, track edits automatically, or preserve an archive of every earlier entry. Add a separate record when a new document arrives. Keep the original file and earlier exports elsewhere so that you can retrace the review.

Private investments can provide less information than public investments. The Securities and Exchange Commission (SEC) also warns about illiquidity and possible loss. A well-kept index does not remove those risks or prove that every needed document was supplied. SEC private-placement bulletin, updated September 21, 2026.

The useful output is a set of traceable questions and recorded actions. “The fee section needs revision” is a clearer result than a general claim that the entire investment has been reviewed.

Set the Exact Trust and Review Scope

Enter the trust's full name and an identifying reference. Then describe the ownership interest and the part of the review being maintained. A sponsor name alone may refer to many separate trusts. A document for another interest or transaction may not answer the question in your file.

The review cutoff states when this copy of the log stops. It cannot be later than the current date in Coordinated Universal Time, or UTC. This avoids treating a planned review as a completed one. The browser uses UTC consistently, which can differ from your local date near midnight.

The optional file label helps you recognize an export. Changing that label alone does not change the underlying trust or scope. Changing the trust, scope, or cutoff does require a new applicability check for each recorded assessment.

After a successful context change, the tool clears saved assessment confirmations. It keeps the entered descriptions, reading choices, dates, and recorded actions. Their output becomes pending until you check them again. It also clears a confirmation in the open document form while preserving its text.

Spaces and equivalent common Unicode forms are normalized when deciding whether the context changed. Stored text is otherwise retained with leading and trailing spaces trimmed. The tool does not resolve aliases, corporate name changes, or legal identity for you.

Give Each New Document Its Own Record

Enter the document title, a source reference, the relevant page or section, and a summary in your own words. The source field can hold a file name, publisher reference, or URL. It is stored as text. The tool does not open the link or confirm the source.

A useful summary states the portion that matters. For example, “Section 3 changes the stated base for the annual charge” is more useful than “Important amendment.” Add enough context to distinguish the claim from a change in rate, timing, or payer.

You may save an incomplete record. This allows a requested loan statement or an unclear notice to stay visible. The report will identify missing support fields. Saving a title does not mark the item read or establish that it was received.

Each record receives a stable ID, starting with D1. IDs follow entry order, not document date. A later entry can describe an older document. Removing another record does not renumber the remaining IDs, and removed IDs are not reused.

For a revised document, add a new record and link it to the earlier one where appropriate. Editing an old record instead would overwrite its saved fields in this index. That may be right for a typing correction, but it will not preserve the earlier version of the entry.

Keep Five Different Dates Separate

The issue date describes the date shown for the document. The received date describes when you obtained it. The stated effective date describes when the text says a change takes effect. The review date records your reading and assessment. A chosen follow-up date is a separate planning entry for an open question.

Blank issue, receipt, and effective dates remain unknown. The tool counts those three types of unknown date fields. It does not substitute the cutoff or the day you use the browser. A record can support a limited review action even when one of those dates remains unknown, provided you explain the limits.

Document, receipt, and review dates cannot exceed the cutoff. A review date cannot precede a known receipt date. If receipt predates the recorded issue date, the log flags it for attention. It does not decide whether the cause is a draft, a later issue, or an entry error.

A future stated effective date is permitted and flagged. A notice received in October might describe a November change. Recording that date does not establish that the change is valid, unconditional, or already in force. The actual text and professional review must answer those questions.

The chosen follow-up date may be before, on, or after the cutoff. It needs an open question. These are your planning dates. The tool does not calculate a consent window, filing deadline, notice period, or limitation period.

Choose one or more of eight review topics. They cover cash and reserves, fees, financing, leases and operations, property work, ownership and transfers, provider roles, and other issues. These categories organize the file; they do not certify coverage of the entire investment.

One report can touch cash, fees, and property work. That creates three topic links but still only one document. Keep the summary specific enough to show why each selected topic belongs there. A topic checkbox does not establish that the issue was resolved.

You may also link the record to one earlier saved document ID. The choices distinguish a reference from a claimed change in selected terms or replacement of selected text. “Relationship unconfirmed” preserves a link whose meaning still needs review.

The linked ID must exist and must have been assigned earlier. This prevents loops such as D2 pointing to D3 while D3 points back to D2. It does not establish legal priority. An earlier ID can describe a later-dated document if that document was entered first.

No link automatically marks another item obsolete, changes its assessment, or closes its question. For instance, a fee amendment might address one paragraph of an earlier report while leaving its reserve discussion untouched. Read and record that limited effect rather than treating the whole report as replaced.

Record the Review Action Without Closing Every Question

The recorded action has four choices. “Not assessed” keeps the review open. “No review change identified” records a reader's limited conclusion. “Review revision needed” identifies unfinished work. “Review revised” says that the reader has changed the relevant part of the review.

A recorded choice is different from a confirmed assessment. Until you check the assessment against the saved trust, scope, and cited passage, the output says “Pending reader assessment.” The original choice stays visible so that you can see what still needs confirmation.

A confirmed action needs a title, source, locator, summary, at least one topic, source-reading check, review date, and reason. “Review revised” also needs the location of the revised review. “Not assessed” cannot be confirmed into a completed action.

The reason should explain the comparison. “Read it” is weak. “The notice changes the manager contact; the payment section is not addressed” tells a later reader which conclusion was reached and what was left alone. The software checks that text is present, not whether that reasoning is correct.

An open question is independent of the action. A reader may update one sentence while still asking for a supporting record. The question remains open until you edit or remove it. The log does not infer resolution from a checked box, a document link, or the arrival of a newer file.

Work Through the Five-Document Example

The example uses an invented Alder Cove trust. All documents and conclusions are fictional. Load it to see how a compact file works before entering your own material. Loading the example replaces the current log only after an in-page confirmation.

D1 is a quarterly operating report linked to cash and fees. The reader records that no change was identified in the selected review passages. That statement is confirmed, but the example does not claim that the figures were audited.

D2 is a selected fee amendment linked to D1. The reader records that the review needs revision. Its question asks which charge periods the signed change covers, with a chosen follow-up date of October 15. D1 remains in the file with its own assessment. D2 does not automatically invalidate every earlier conclusion.

D3 is a manager contact notice. The reader records a completed revision and supplies the location of the changed review section. That action affects the provider-role topic. It does not imply that the reader tested a new bank instruction or changed a payment destination.

D4 is a requested loan statement with issue and receipt dates not established. It remains pending, with a question assigned to October 18. D5 is a lease notice with a stated November 1 effective date. Its effect is also pending, and the question has a November 1 planning date.

At the October 18 cutoff, the file contains five documents. There is one confirmed no-change action, one confirmed revision-needed action, one confirmed revised action, and two pending assessments. Three questions remain open. This is a work record, not a conclusion that three-fifths of the investment is safe or complete.

Read the Counts and Follow-Up Dates

The example has six topic links across five documents because D1 links to both cash and fees. Fees appears twice, while cash, financing, leases, and provider roles each appear once. The other three topics have no linked document in this file. Zero links means none recorded, not that the issue does not apply.

There are six unknown issue, receipt, or effective date fields. Four records have no effective date entered; D4 also lacks issue and receipt dates. A blank effective date is not a statement that no effective date exists. The future November date is counted separately.

The three open questions divide into one planning date before the cutoff, one on it, and one after it. If a question has no date, it appears under “No date chosen.” The tool uses the saved cutoff for these comparisons. It does not move the file forward each day unless you change and save that cutoff.

Filters change the documents displayed below the summary. They do not change the summary population or the full downloads. Viewing only “Review revision needed” shows D2, but both exported formats still contain all five records, their dates, links, choices, and questions.

Correct an Entry Without Losing Its Context

Editing a document field clears its assessment confirmation. Changing the title, source, locator, summary, or issue date also clears the source-reading check. Check the changed passage again before confirming the action. Text is preserved so that a correction does not erase the working notes.

Save or discard each open form before building a fresh output. Any edit invalidates the displayed result and download buttons. This prevents an earlier export from being presented as the result of unsaved input. A rejected date or missing support field leaves the prior saved record intact.

Removal requires an in-page confirmation. If a later document links to the selected record, removal is blocked. Edit those links first. The tool will not silently erase their target. Removing one document preserves unrelated open-form text; removing the document being edited clears that form after confirmation.

The confirmation can be canceled. Typing or changing another control cancels a pending confirmation too, so an old prompt cannot act on a newly edited file. These safeguards protect the index during editing. They do not create an audit archive or recover a closed browser session.

Use the Log With the Original Documents

Keep the cited passage, relevant attachment, and any controlling agreement available outside the log. A short entry is a guide to that evidence, not a replacement for it. Where sources conflict, record the conflict and the further evidence needed.

The Financial Industry Regulatory Authority (FINRA) discusses primary-record investigation and follow-up on inconsistent private-placement claims for covered firms. The tool supports organized questions; it does not certify compliance with those duties or impose them on every reader. FINRA Regulatory Notice 23-08, May 9, 2023.

Before recording that a review was revised, check the actual revised paragraph or calculation. A fee change may affect one period. A loan notice may affect a future date. A new report may simply describe a different measurement period. The reason and review-location fields should make the chosen scope understandable to another reader.

Save a Complete Copy of the File

Build the log, then download the full JSON, the full text, or both. JSON keeps the fields and generated counts in a structured file. Text creates a readable index. Both include the saved inputs and the tool's limits, regardless of the display filter.

The full JSON file is limited to 1 MiB, or 1,048,576 UTF-8 bytes. Individual fields and the thirty-record limit also apply. A rejected addition or edit does not consume an ID or replace the saved file. Shorten the proposed entry before trying again.

There is no import, automatic storage, source retrieval, scheduled alert, or sending function. Keep exports and original records in your chosen system. Earlier exports can preserve your prior working state, but the tool does not compare those versions or establish when they were created.

FAQ

Does the log retrieve current Inland reports?

No. You enter the document references and observations. The tool does not access a sponsor portal, identify the latest amendment, or verify that your file is complete. Its example is entirely invented.

Does linking an amendment replace the earlier record?

No. The link records your stated relationship. Both entries and their questions remain. The actual legal effect requires the document text, its scope, and any relevant agreements or advice.

Can I save a document with an unknown date?

Yes. Unknown issue, receipt, and effective dates remain blank and are counted. Other requirements still apply to a confirmed assessment. Explain any date limit that affects your conclusion.

Why did an assessment become pending after I changed the trust?

The old confirmation applied to the prior context. A trust, scope, or cutoff change clears that confirmation while preserving the content. Read the retained entry against the new context before checking it again.

Does a completed review action close its follow-up question?

No. The action and the open question are separate fields. A narrow revision can be finished while a supporting document is still missing. Remove or revise the question only when the evidence supports that change.

Will the log remind me when a chosen date arrives?

No. It compares chosen dates with the saved cutoff when you build the file. It sends nothing and does not run in the background. Use a separate reminder system if you need notifications.

About Sequoia Research

Sequoia Research, LLC provides independent research on DSTs and other real estate investment offerings. This tool helps readers connect changing document evidence to clearly bounded review actions.

Sources

Sources inspected October 18, 2026. Software behavior and the Alder Cove example are original descriptions of this tool. The example is not an Inland offering, legal interpretation, or investment assessment.