Delaware Statutory Trust Reviews: Source-Date Freshness Map

What Is This Article About?

This guide explains a tool for checking the dates behind Delaware statutory trust reviews. The map separates when a document was issued from when its data or terms applied. It flags older evidence, unknown dates, future dates, and mixed reporting periods based on your entries. The result helps you ask for the right update without treating a recent document as proof of a sound investment.

Table of Contents

• What the Source-Date Map Checks
• Choose a Review Date and Age Threshold
• Enter the Dates Behind Each DST Review Claim
• Compare Reporting Periods Without Mixing Measures
• Follow the Four-Source Example
• Read Future and Missing-Date Flags
• Turn the Map Into Specific Research Requests
• Keep Contract Dates and Current Data Separate
• Save the Map and Preserve Its Limits
• Frequently Asked Questions

What the Source-Date Map Checks

The map checks whether the dates in your research fit the question you are asking. It can show that an October review relies on June operating data, or that two documents describe different quarters. It cannot tell whether the income figures are accurate or whether a newer report exists.

You enter the document title, the claim it supports, its date type, and the dates you can establish. You may add a source address, a comparison group, and notes. The output keeps the claim beside its source so an old date does not become a vague complaint about the whole review.

Limited information is a real part of private-placement research. The SEC explains that these offerings may provide less disclosure than registered offerings. That makes a blank date worth recording rather than filling with a guess. It does not mean that every missing public document signals a problem. SEC private-placement bulletin, updated September 21, 2026

The map produces date flags, not ratings. A source can be old and still answer a historical question. A new page can repeat outdated facts. The useful result is a precise statement about which claim needs a date check, an update, or better context.

Choose a Review Date and Age Threshold

The review date is the date against which the map measures evidence. Use the date of the decision or review you are examining. For a current review, enter your current cutoff. For a past review, keep the past cutoff even if you are doing the work today.

That choice changes the result. A report issued after a past review date could not have supported that review in its final issued form. A later correction may help explain what happened, but it should not quietly replace the evidence available at the time. Check whether an earlier version was actually available.

The age threshold is your reminder setting in whole calendar days. The example uses 90 days. That number is not a reporting rule, a deadline set by a regulator, or a Sequoia investment standard. Choose a setting that helps organize the task, then judge each flagged item in context.

The tool flags evidence only when its age is greater than the threshold. Evidence exactly 90 days old does not trigger a 90-day flag. At 91 days it does. A zero-day setting flags all evidence dated before the review day, which can be useful for a narrow same-day check but may create many routine flags.

Age uses the evidence date, not the publication date. Both ages appear in the output so you can see the difference. Changing the threshold changes reminders; it does not change the underlying dates or make a document more reliable.

Enter the Dates Behind Each DST Review Claim

Start with the claim, such as “property income covers the stated debt payment.” Then name the document used to support it. Include a page or table reference in the notes. A title alone may not identify which of several dates inside a packet applies to that claim.

The publication date is when the document was issued or published, based on the evidence you have. It is not automatically the date you downloaded it, the date an email was forwarded, or the date your device saved the file. If the issue date is unknown, leave it blank and explain the uncertainty.

Choose one of three evidence date types. A point-in-time snapshot describes a condition on one day, such as a dated rent roll. A reporting period describes activity across a start and end date. A contract or rule effective date describes when a stated term takes effect. These dates answer different questions.

For a reporting period, enter both the start and the end when known. The evidence-date field holds the end. For the other two types, leave the period start blank. The tool rejects an end before a start and asks you to clear a start if you select a non-period type.

You may leave dates unknown. A missing date stays unknown in the map; it never becomes zero days old. If one document supports claims with different dates, use separate rows. The same source address may appear more than once because the relevant unit is the claim and its evidence.

Compare Reporting Periods Without Mixing Measures

Use a comparison group when you want to check related rows together. For example, assign “Property operations” to two quarterly income packets. Group names ignore letter case and repeated spaces. Leave the group blank when a row has no useful date comparison.

The tool identifies different complete reporting periods within a group. It checks both start and end dates. A three-month report and a nine-month report ending on the same day therefore do not count as the same period. It also flags different known snapshot dates and groups that mix date types.

If a reporting period lacks its start or end, the group reports an incomplete-date limit. It does not infer that the missing period matches another row. A group with one source cannot establish a trend. It simply keeps that source's date record together.

Matching dates are only the first step. Two reports for the same quarter may define net operating income differently. One may include the sponsor's whole portfolio while another covers one property. The map does not read these definitions, normalize the figures, or decide that a comparison is valid.

Keep the next question close to the result: “These periods match; do the properties, costs, and calculation methods also match?” That prevents a clean date table from becoming an unsupported comparison. The same caution applies when several reviews repeat one underlying report.

Follow the Four-Source Example

The tool opens with four invented source rows. They describe no actual sponsor, property, or offering. The review date is October 16, 2026, and the reminder threshold is 90 days. Replace the rows with your own records before using the map for research.

The June operations packet was issued on September 15. Its reporting period runs from April 1 through June 30. By the review date, the publication is 31 days old, but its period-end evidence is 108 days old. The gap from period end to publication is 77 days.

The September operations packet was issued on October 5. It covers July 1 through September 30. Its publication age is 11 days, while its evidence age is 16 days. The five-day publication gap tells you when the packet appeared; it does not prove that every item was verified within five days.

An undated loan amendment copy states an August 1 effective date. Its evidence age is 76 days, and its publication age is unknown. The map can calculate one without inventing the other. The effective date alone does not establish whether another amendment later changed the term.

The fourth row is a later-issued summary with an October 20 publication date. It covers the same July-through-September period as the second packet. Its evidence age is 16 days, but publication falls four days after the review cutoff. The map flags that timing conflict.

Invented source	Publication age on October 16	Evidence age	Main date question
June operations packet	31 days	108 days	Is the older quarter enough for this claim?
September operations packet	11 days	16 days	Do its definitions match the earlier packet?
Undated amendment copy	Unknown	76 days	When was this version issued, and was it later changed?
Later-issued summary	Four days after review	16 days	Was any earlier version available at the review date?

Only the June evidence exceeds the 90-day reminder. The operations group also contains two distinct reporting periods. Those flags can overlap because they describe separate issues. They are not two adverse findings about the property.

The group does not average the quarters or score the newer one higher. A quarter-to-quarter income change still requires the actual figures, common definitions, and an explanation of what changed. This tool organizes that request rather than doing the financial comparison.

Read Future and Missing-Date Flags

“Published after review date” means the entered issue date is later than the chosen cutoff. First check for a typing error. Then check whether you have a later revision, a planned publication, or the wrong review date. Preserve the original record while resolving the question.

“Evidence date after review date” has a different meaning. A document may discuss a future forecast or a contract change that has not yet taken effect. The flag helps keep that future item separate from a claim about conditions already observed. It does not by itself establish that the document is wrong.

The publication gap can also be negative. A contract issued on October 1 may have a November 1 effective date. The tool would report publication before evidence. That is a valid date relationship to explain, not a reason to move either date merely to remove a flag.

Missing dates deserve targeted follow-up. Ask for the original issue date if publication is unclear. Ask for the covered period if an income figure has no period label. A website footer showing the current year does not fill either gap unless it actually identifies the relevant content date.

The summary counts can overlap. One row may have an unknown publication date and old evidence. Counting it twice across categories does not mean there are two documents. The total source count shows how many rows you entered, including repeated documents used for separate claims.

Turn the Map Into Specific Research Requests

Use the result to narrow the next request. Instead of asking for “newer research,” name the claim, the current source, its evidence date, and what would help. A useful request might seek the next quarter's operating statement using the same property set and expense definitions.

FINRA's private-placement guidance discusses material developments and keeping diligence files updated in the context of member firms' recommendations. It also describes records of the review process and its results. The map borrows the practical idea of keeping dated support visible; completing it does not satisfy a firm's legal duties or establish that a recommendation is appropriate. FINRA Regulatory Notice 23-08, May 9, 2023

Record the response in notes, but separate a promised delivery date from an evidence date. “The report is expected next Friday” is a follow-up fact. It does not prove the report's contents or create a new period-end figure. Add the actual document and its dates when you receive it.

For a claim that cannot yet be refreshed, narrow the wording. A review may be able to describe results through June without making a claim about October. That change can make the statement more accurate even before another document arrives. Keep the limit beside the claim wherever it appears.

Keep Contract Dates and Current Data Separate

An old contract can remain relevant long after a recent operating report has become too old for a specific task. The age threshold applies to every evidence date entered, including effective dates. For a contract, an age flag is a prompt to check amendments and scope, not a declaration that the term has expired.

The map does not compare effective dates as if they were reporting periods. Two different contracts may properly take effect on different days. Their legal relationship requires reading the documents. If a group mixes a contract date and a snapshot, the tool calls out the different date types without deciding which governs.

Ratings have their own date questions. In a December 16, 2025 risk alert, SEC staff described missing disclosures about when third-party ratings were given and the periods on which they were based. That discussion concerns the adviser marketing rule for advisers within its scope. The alert is staff guidance, not a new rule for every DST research website. SEC risk alert, printed page 7

For a rating claim, use separate rows if needed to track the award date and the research period. A badge shown this year may rely on earlier data. The map can make that gap visible, but it cannot decide whether the rating method is fair or the required disclosures are complete.

Save the Map and Preserve Its Limits

The tool accepts up to 50 source rows. Titles and claims are required so each result has a clear subject. Dates use the year-month-day format, and invalid calendar dates are rejected. The calculation uses whole calendar days, so daylight-saving changes do not add or remove an hour from the age count.

Names, notes, and source addresses appear as plain text. The tool does not open links, fetch documents, verify dates, monitor updates, or save entries between visits. A source address is a pointer you entered. It is not evidence that the page was inspected or remains available.

After building the map, download its JSON record to retain the inputs, flags, group comparisons, and calculation conventions. The download is not an import file for this tool. Changing any input or adding or removing a row clears the old result and disables download until you rebuild.

Removing a row requires an in-page confirmation. Canceling keeps the entries in that row and elsewhere. Review the exported file before sharing it, and avoid placing account details or private access links in the notes. Its value is a clear date record, not a certificate that the investment passed review.

Frequently Asked Questions

Does a recent publication mean the underlying data is current?

No. A newly issued document can describe an earlier period. Read both ages and check the date tied to the specific claim. The map keeps those two dates separate.

Is 90 days the required freshness standard for DST research?

No. It is the example's reminder setting. Different claims may need different evidence. The tool flags ages above your setting without declaring a document invalid or a review complete.

What should I enter when a document has no date?

Leave that field blank and explain what is missing in the notes. Do not substitute the download date. You can still enter an evidence date if the document clearly identifies one.

Can matching reporting periods prove two reviews are comparable?

No. The populations, definitions, methods, and included costs may still differ. Date alignment helps organize the next check; it does not complete the comparison.

Why would a contract be published before its effective date?

A document can state terms that will apply later. The map preserves that order and flags it for context. It does not treat a future effective date as proof of a mistake.

Does the map find the newest version of a report?

No. It uses only the dates and text you enter. You must check the source, request updates, and confirm which version supports the claim. There is no background monitoring or automatic verification.

About Sequoia Research

Sequoia Research, LLC provides independent research on DSTs and other real estate investment offerings. This educational tool helps readers keep the dates behind their research clear and prepare focused requests for missing evidence.

Sources

• SEC private-placement bulletin, originally August 17, 2022; updated September 21, 2026.
• FINRA Regulatory Notice 23-08, May 9, 2023.
• SEC adviser marketing-rule risk alert, December 16, 2025; rating date and measurement-period discussion on printed page 7.

Sources accessed October 16, 2026. All four example documents and their dates are invented for this tool's worked example. The sources listed above are actual primary guidance, with their actual publication or update dates.