Research guide

DST Due Diligence: How to Document Open Questions Before Making a Decision

By Sequoia ResearchPublished Read as Markdown

What Is This Article About?

This article explains how to keep an open-questions log while reviewing a Delaware statutory trust (DST) investment. It shows how to connect each question to a source, an owner, a reply, and a reason for accepting or rejecting the answer. A fictional review illustrates why a large stack of documents can still leave a key issue unresolved. The goal is a clear decision record that another person can follow, including what remains unknown.

Table of Contents

Start With the Decision the Question Could Change

An open question should point to a choice that could change. “Get more information about debt” names a topic. “Confirm whether the stated maturity includes an extension that has not yet been earned” identifies a gap. The second question shows why you need another source or answer.

Begin with the claim that caught your attention. Record where you found it and what it appears to mean. Then state the fact you need to check. Avoid turning your first reading into a conclusion. Two pages may use different dates, interests, or terms. It may also be a real error. Keep both options open until the evidence supports one.

The Securities and Exchange Commission (SEC) warns that private placements can provide less information than registered offerings. They may also be hard to resell and expose investors to a total loss. Its investor bulletin was updated September 21, 2026. An organized file helps you see gaps; it does not remove those investment risks. SEC private-placement bulletin.

Write the possible effect in plain language. A lease-date question might change how you assess near-term rent risk. A fee question might change the cash amount required at closing. A missing report might limit your ability to assess a stated property condition. Those effects tell you more than a label such as “important.”

Keep the effect separate from the answer you hope to receive. “Confirm the tenant is strong” sets a desired outcome. “Identify the tenant, any guarantor, and the evidence available for each obligation” leaves room for an unfavorable answer. Good questions can weaken a proposed investment case as well as support it.

This article offers an editorial method for organizing a review. Its labels, example dates, and case figures are teaching aids created for this article. They are not a regulator's prescribed investor form, a legal recordkeeping standard, or a substitute for a firm's required investigation. Use the method to make your reasoning visible, and keep the duties of each professional separate.

Build a DST Due Diligence Issues Log

Use one row for one question that can reach a clear outcome. Give it a stable identifier such as Q-01. A stable ID lets you discuss the same issue across emails, meetings, document versions, and a final memo. A short topic label helps sorting, but it should not replace the question itself.

Start with a small set of fields that people will actually maintain. The following layout is a suggested working record, not a required industry format. A spreadsheet, document table, or approved internal system can hold it. The choice of software matters less than whether each field contains a useful fact.

Field What to record What to avoid
Issue ID and question One specific unknown A broad topic with no requested answer
Source pointer Title, version, page or section “See the documents”
Decision effect Why the answer could matter An unexplained high-priority label
Follow-up owner Person coordinating the request Assuming everyone is responsible
Intended respondent Entity or role able to address it Treating a brand name as authority
Reply and evidence Dated answer with its support A bare “done” note
Reviewer and disposition Who assessed the reply and why Calling receipt a verified conclusion
Next action or trigger Specific task, date, or change An open item with no next step

Add an access field when some records have limits on who can read them. Add a dependency field when one answer is needed before another analysis can be completed. For example, a cash-flow comparison may depend on a correct fee basis. Keep these fields simple enough that a reviewer can understand them without a separate manual.

Do not split a single issue into many rows just to show more work. Three emails seeking the same lease amendment can remain one issue with three contact entries. A reply about a property manager may leave another issue open. It may not name the firm that sends investor reports. Separate questions when their evidence and closure tests differ.

Keep a short history beneath each row or in a linked record. Record the original question, later clarification, and reason for any change. If the scope narrows, preserve the part no longer being answered. Otherwise, the final green status may describe an easier question than the one that mattered at the start.

The log should point to evidence without becoming a warehouse for sensitive material. Store full records in their authorized location. Use a permitted source reference and enough context to locate it. A broad team worksheet does not need bank details, tax identifiers, signatures, or unrelated personal information to show that a question remains open.

Record Sources and Dates So Answers Can Be Checked

A useful source pointer has enough detail for someone else to find the same passage. Include the document title, the version or date printed on it, and the page or section. If a PDF has cover pages before its printed numbering begins, record both the PDF page and the printed page when needed.

Separate the date you read a source from the date it describes. A statement read in October might report June results. An amendment signed in August might change a lease from September onward. These dates answer different questions. One “date” column can hide the distinction and make an old fact appear current.

For a website, keep the page title, address, access date, and the limited statement you used. If the page has no clear revision date, say so. An access date shows when you checked the page. It does not establish when the company last changed the policy or whether an older version said the same thing.

For a phone discussion, record the date, participants, the speaker's role, and your understanding of the answer. Label it as a conversation note. Ask for a written source or confirmation when the answer matters to the decision. A polished note written by the reviewer is still the reviewer's account of the call.

The Financial Industry Regulatory Authority (FINRA) discusses documenting the process and results of private-placement investigations in its May 2023 guidance. Its examples include reviewed material, meetings, dates, people, and work on potential warning signs. Those provisions concern covered member-firm obligations and practices. The investor log described here does not perform or certify that firm's work. FINRA Regulatory Notice 23-08.

Make changes visible. If a replacement file arrives, add its reference and the date received. Keep the prior reference beside the issue history. Note whether the new file answers the question, changes the question, or merely repeats the prior claim. A new file name alone does not establish new evidence.

Assign a Follow-Up Owner and the Right Respondent

The person who keeps a question moving may differ from the person qualified to answer it. Call the first person the follow-up owner. This person tracks the request and keeps the source record up to date. They make sure the reply reaches the reviewer. Owning this task does not give someone control over the investment.

Name an intended respondent by role and entity. A sponsor contact may route a property question to an asset manager. A broker's compliance team may explain the firm's process. A tax adviser may address a specific investor question within an agreed engagement. Do not assume that one contact can speak for every entity in the transaction.

Record the routing basis when authority is unclear. “Sponsor contact offered to obtain a lender response” describes a limited role. “Lender confirmed” says something stronger and needs the lender's actual response or an accurately labeled source. That difference matters when an answer passes through several people.

Choose a review date for the next action, but label what the date means. It may be your requested reply date, a date the respondent agreed to, or a date when the decision team will revisit the issue. It is not automatically a legal deadline, a promise of delivery, or an extension of a transaction period.

If the owner is absent, name a backup or reassign the task openly. Retain the handoff date and current state. A question should not disappear because the person who first asked it has left a meeting or changed roles. A new owner needs the exact request and evidence received, not a vague message to “follow up on the loan.”

Avoid sending the full log to every person involved. Different respondents need different parts. A targeted request can include the issue, relevant source, requested clarification, and useful reply date. Preserve the full internal reasoning for the people authorized to review it. This article does not send any request or establish access to a restricted file.

Separate Replies From Resolved Questions

Use status labels that tell you what actually happened. “Reply received” means a reply arrived. “Evidence under review” means someone is checking it. “Resolved for this scope” means the reviewer accepted a supported answer to the defined question. Those are separate events, even when they occur on the same day.

Other useful states include open, waiting on a named dependency, unable to verify, and reopened. A question can also become irrelevant because the investment scope changed. Record why. Do not hide an unanswered question under a broad “closed” label when it was dropped because the property was removed from the proposed package.

Set a closure test before reading the answer. For a lease-date conflict, the test might be a matching executed lease and any applicable amendment, reviewed for the relevant term. For a fee basis, it might be a current schedule and a clear calculation tied to the proposed interest. The test should fit the question, rather than demanding every possible document.

The reviewer should write a short finding in their own words. “Accepted because the two pages describe different fee classes, and the proposed subscription uses Class B” explains the decision. “Sponsor said okay” does not. The conclusion should name the support and preserve any limit, such as an unreviewed later amendment.

Resolving a fact is different from accepting its economic risk. You might establish that a lease ends before a planned sale. That answers the date question. It does not establish that the tenant will renew or that the exposure is acceptable. Keep the verified term and the investment judgment in separate fields.

An issue may remain unanswered when the review ends. Say what could not be established and how that affected the decision. Do not replace uncertainty with the most favorable assumption. A complete record can honestly conclude that the available evidence was not enough to support the proposed action.

Work Through a Fictional DST Review

Consider an invented review of Cedar Point Industrial DST. The names, documents, figures, dates, and decisions in this example are fictional. They do not describe a current offering or any sponsor's actual practices. The example follows a small review file so the logic stays visible.

Morgan maintains eight issue rows. Six have received some form of reply. Four have passed their stated closure tests. One of the other two replies needs support, and one addresses only part of the question. The two remaining issues have no reply. The file therefore has a 75% reply rate and a 50% resolved rate at this stage.

Those figures describe this log only. They do not mean that the investment is 50% safe or that half the needed research is finished. One unanswered issue can matter more than several resolved details. The counts help Morgan manage work, while the decision effect column explains what the work means.

One open issue concerns a fee. An invented summary says the fee is 1%, but Morgan cannot tell whether the amount is included in a proposed $250,000 subscription or charged in addition. Under the example's chosen basis of exactly $250,000, the fee is $2,500. If additional, the combined payment would be $252,500. If included, the total payment stays $250,000 and $247,500 remains after that fee alone.

The arithmetic cannot select the correct treatment. Morgan asks for the applicable schedule, the payer, the recipient, and the basis. The response supplies a matching schedule and confirms the included treatment. Morgan checks the referenced class and marks the narrow fee-treatment issue resolved. The example does not assume that $247,500 all reaches the property; other uses and costs would require their own review.

A second issue concerns the rent shown for one tenant. The invented rent roll uses $40,000 each month, or $480,000 a year. A signed amendment in the fictional file uses $38,000 each month for that same full twelve-month period, or $456,000 a year. The difference is $24,000 annually, equal to 5% of the rent-roll figure. The figures exclude reimbursements and other charges so they can be compared directly.

The first reply says the difference is small. That does not meet the closure test. Morgan seeks a source-based reconciliation and a corrected model, or an explanation of why the model uses another amount. The question stays open until its cause and effect are addressed. The log does not assume that the entire $24,000 difference flows directly to investor distributions.

A third issue asks whether a report can be reviewed by Morgan's adviser. A contact sends a document index showing that the report exists, but supplies no permitted access route. Morgan records “existence indicated; access not established.” The index answers a different question from whether the adviser can inspect and rely on the report.

Later, two additional issues satisfy their closure tests, bringing the resolved count from four to six out of eight. A new amendment then undermines the answer to one previously resolved issue. Reopening that issue leaves five resolved and three unresolved. The resolved rate is now 62.5%, not 75%. The lower count reflects a more current record, not necessarily worse work.

Prioritize Missing Evidence Without Inventing a Risk Score

A useful priority tells the team what to do first and why. It should not pretend to calculate the chance of loss from a few labels. Consider the effect on the decision, the time available to obtain evidence, and whether another task depends on the answer. Write the reasons beside the priority.

A question about the meaning of the planned exit may change the investor's view of liquidity. A missing page number may slow the review but have little economic effect once corrected. Both belong in a working file. They do not need equal attention merely because each occupies one row.

Distinguish a decision condition from a routine follow-up. A decision condition is something the reviewer says must be established before the proposed action can be supported. A routine follow-up may improve the file without changing the current conclusion. These are reviewer judgments within a stated scope, not labels the sponsor or software should assign on the investor's behalf.

Use a dependency note when a task is blocked. Suppose the debt calculation needs a confirmed amount and the reviewer has only a preliminary estimate. The calculation can remain “waiting on Q-04.” That shows why the work is delayed. It also prevents someone from treating an unstarted calculation as evidence that no debt concern exists.

Avoid combining unrelated unknown amounts into an apparent worst-case total. A potential fee, a possible rent adjustment, and a sale-price assumption may overlap or belong to different periods. If you build a scenario, state which effects can occur together and how each enters the cash model. Otherwise, keep them as separate unresolved exposures.

Priority can change as evidence arrives. A small difference may reveal a larger scope error. A serious concern may be resolved by a directly applicable source. Record why the order changed. The purpose is to guide the next useful action. It is not to defend the first label or keep a dashboard green.

Handle Conflicting Answers and Restricted Reports

When answers differ, preserve both before choosing one. Record the exact issue, each respondent's role, their source, and the date. Ask whether the answers use the same property, period, interest, and definition. A numerical conflict can disappear after those boundaries are aligned, but the alignment needs evidence.

A newer date does not always make a source controlling. A recent presentation may summarize an older agreement. A later signed amendment may change a specific term while leaving others intact. Have the appropriate reviewer assess which materials govern the question. The log can record that assessment without claiming to resolve legal document priority on its own.

Treat an interested source fairly. A sponsor may be the best place to obtain a record it created, yet the sponsor's explanation still needs the right support. Likewise, a paid outside reviewer may offer useful analysis while having limited scope or access. Identify the relationship and the claim being supported rather than labeling every paid source unreliable.

The SEC staff's August 3, 2022 conflicts bulletin explains that disclosure alone does not satisfy a firm's duty to act in a retail investor's best interest. Its guidance addresses broker-dealers and investment advisers, with different duties depending on the relationship. The bulletin is a staff statement, not a new rule. Recording a conflict in an investor worksheet does not settle those professional obligations. SEC staff conflicts bulletin.

If a report cannot be shared, ask what permitted information can address the specific question. That might include the report's date, subject, scope, stated limits, or a response from a person authorized to discuss it. Do not treat a summary as equivalent to reading the full report. State exactly which form of evidence was available.

“Unable to verify” is a useful outcome when access remains insufficient. It does not accuse anyone of wrongdoing. Explain what was requested, what was supplied, why the substitute did not meet the closure test, and what effect the limit had. An accurate access limit is better than an unsupported statement that the report cleared the issue.

Write the Decision Memo From the Evidence

The decision memo should explain the reasons a future reader would need. Start with the investment and review scope, the records available as of the decision date, and the action under consideration. Identify who made the decision and what professional input was used. Do not let a document list stand in for the conclusion.

Summarize the main findings in a few connected paragraphs. For each one, connect the fact to its evidence and its effect. If the evidence answers a narrow question, keep the conclusion narrow. “The fee basis was reconciled for this subscription class” is supportable where “all costs were verified” may not be.

List the unresolved issues that still matter. For each, describe the missing evidence, the assumption used if any, and how the conclusion could change. If the review cannot support the proposed action without that answer, state that clearly. A deadline does not make an unsupported assumption more reliable.

In the fictional Cedar Point case, Morgan can say that the fee treatment was reconciled but the rent-model difference remains open. Morgan should not offset the rent question with a count of other completed checks. The memo can explain which remaining evidence is needed and why the rent question affects the current view of the offering.

A decision to proceed should not rewrite an unresolved fact as verified. A decision to decline should not imply that the investment is fraudulent or unsuitable for everyone. Preserve the reason within the actual review scope. The file records one decision based on specified information, circumstances, and advice, rather than issuing a universal verdict.

Investor.gov encourages investors to understand the investment, read the disclosures carefully, and seek help when they remain confused. Its guidance supports asking for a clearer explanation before committing money. It does not promise that every request will produce enough information or that a completed worksheet establishes understanding. Investor.gov questions before investing.

Save the decision memo with the version of the log used to prepare it. Link each material conclusion to the relevant issue IDs. A reviewer should be able to trace each key sentence to its source and the reasoning behind it. Keep later updates separate so the original decision record remains understandable.

Reopen Questions When the Facts Change

A resolved issue may need another review when its supporting facts change. Define a practical reopening trigger when you close the row. A revised fee schedule, a new lease amendment, a changed debt term, or a different investment scope could affect an earlier answer. The trigger should identify the fact that mattered, not merely say “check again later.”

Reopening preserves useful history. Record the original resolution date and the evidence used, then add the new event and current question. Do not erase the prior conclusion to make the file look as though the issue was always open. Both versions show what was known at each point.

A scheduled review date is different from an event trigger. The date asks someone to check for changes. The event gives a reason to reassess a particular conclusion. Neither is automatic monitoring. If no one has agreed to watch for the event, the log should not imply that the team will learn of it promptly.

Use the same stable ID when the new evidence concerns the original issue. Use a linked new ID when it raises a separate question. For example, a corrected rent amount can reopen the model-input issue. A later question about who approved the original amount may require another row with a different respondent and closure test.

If the investment is no longer under consideration, record that scope change. The decision file may remain useful even though active follow-up ends. Clearly distinguish stopped review from resolved facts. A row marked “review ended because offering removed from shortlist” should not appear in a count of evidence-supported resolutions.

Keep the Log Useful During a Time-Sensitive Review

Clear writing matters even more when time is short. At each check-in, focus on what changed, what still blocks the decision, and who owns the next step. Avoid rereading every completed row. Keep a full history available while presenting a concise current view to the people making the decision.

Use a consistent cutoff for status reports. “As of 3 p.m. on the stated date” is more precise than “current” when replies arrive throughout the day. If a late answer changes the result, issue an updated snapshot. Do not silently combine an old completion count with a new document set.

Measure age carefully. If a question opened October 5 and remains open October 12, seven calendar days have elapsed when the opening date is excluded. That is an elapsed-age convention, not a business-day deadline. A question that has no opening date should be labeled undated rather than assigned zero days old.

Keep work status separate from the investor's transaction calendar. A requested reply date does not extend an exchange deadline, reserve an interest, bind a sponsor, or create a right to delay closing. The appropriate transaction professionals need to assess those constraints using the actual facts and documents.

Before the decision meeting, check the few fields most likely to mislead: stale statuses, missing source versions, replies without reviewers, and unresolved questions marked complete. Then confirm the current scope and evidence cutoff. The final test is whether another reader can explain why the decision was reached and what could change it.

FAQ

What belongs in a DST due diligence open-questions log?

Record specific uncertainties that could affect the review, with a source, follow-up owner, intended respondent, reply, and conclusion. Include the reason the question matters. A topic such as “fees” is too broad on its own; identify the amount, basis, recipient, or treatment that needs to be established.

Is a reply enough to close a question?

No. A reply may acknowledge the request, answer part of it, or offer a claim without support. Check it against the question's closure test. Record who assessed the evidence and why it answers the defined issue. Keep any remaining uncertainty visible rather than replacing it with a general complete label.

Can a question be resolved while investment risk remains?

Yes. You can establish a lease date, debt term, or fee amount without concluding that the resulting exposure is acceptable. Resolving the fact and judging its effect are separate steps. State the evidence-supported fact first, then record the investment judgment and its limits in the decision memo.

Should every open issue stop the investment decision?

The effect depends on the issue and the actual circumstances. A missing document label differs from an unresolved term central to the investment case. Identify which answers are conditions for supporting the proposed action and seek appropriate professional advice. A high completed-item count cannot decide that question for you.

What if a report is restricted and cannot be supplied?

Record the access limit and the alternative evidence offered. Ask what an authorized person can explain or provide for the specific question. Do not say you reviewed the report if you only saw an index or summary. If the available evidence is insufficient, preserve that limit and its effect on the decision.

Is this log a broker-dealer compliance record?

This article describes an investor research method. It does not establish a firm's required procedures, retention periods, approvals, or investigation duties. A regulated firm should apply its own applicable requirements and controls. Investor notes can support a discussion without certifying that the firm fulfilled its responsibilities.

How should an earlier conclusion be corrected?

Keep the earlier entry, add the new evidence and date, and explain what changed. Reopen the issue if its closure test no longer holds. Update the decision memo when the change affects its reasoning. Keep the sequence intact. Deleting the old answer would lose the record of what was known.

About Sequoia Research

Sequoia Research, LLC provides independent research on DSTs and other real estate investment offerings. This educational library helps readers organize evidence and prepare focused questions about investment claims and related services.

Sources

Sources inspected October 17, 2026.