Tool & guide

Best DST 1031 Exchange Companies: Transaction Readiness Tracker

Transaction Readiness Tracker

Users enter professional-confirmed deadlines, required documents, reservations, and responsible parties. The tracker shows incomplete prerequisites and upcoming actions without deciding whether an exchange qualifies for tax treatment.

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 tracker for the work needed during a proposed DST exchange. You enter tasks, responsible parties, confirmed dates, and the earlier tasks each item depends on. The tracker shows open work, approaching dates, and conflicts in the reported task status. It helps you organize a discussion with the people handling the transaction without deciding whether the exchange qualifies for tax treatment.

Table of Contents

What the Transaction Readiness Tracker Does

The tracker organizes up to forty tasks for one defined transaction scope. Each task can have an owner, a reported status, supporting evidence, a confirmed due date, and links to prerequisite tasks. You enter every fact. The tool does not retrieve records, contact a provider, or monitor changes after you leave.

People comparing the best DST 1031 exchange companies may want to understand who handles each step. This tool helps describe that work in a specific file. It does not rank companies, measure their overall service, or choose an investment. A well-organized task list can still omit important work.

Its main feature is the link between tasks. A document request may have to finish before a packet can be sent. A reservation follow-up may depend on a funding question being answered. The tracker follows those links and shows which earlier tasks remain open, including tasks several steps back.

It also keeps timing separate from reported progress. A task can be open without a due date, due today but blocked by earlier work, or marked complete despite unfinished prerequisites. Each condition calls for a different question. The tracker preserves those differences instead of reducing them to one readiness score.

Set the Exchange Scope and Review Date

Give the tracker a label and describe the transaction. State which investor, proposed interests, and coordination steps belong in the file. General labels are enough if you do not need to store private details. Do not enter account credentials, wire instructions, or sensitive identification numbers.

The label and scope lock after the first saved task. They stay locked even if you later remove every task. Start new tracker clears the file and lets you set a new scope. This keeps saved work from being quietly reassigned to a different transaction.

Enter a review cutoff using a real calendar date. It cannot be later than today in UTC. The tracker compares dates with that cutoff, so a saved October 16 review does not automatically become an October 17 review overnight. You must change the cutoff and run the review again.

Status evidence, completion dates, and deadline confirmations cannot fall after the cutoff. Due dates may be in the future. The accepted calendar range is 1900 through 2100. Dates are whole days; the tracker has no time-of-day, location, holiday, or business-day settings.

Record Documents, Reservations, and Responsible Parties

Each task needs a clear title and one of three categories: Document, Reservation follow-up, or Other action. Use the title to define the work and its scope. “Get document” is less useful than “Obtain the current signed exchange instructions for this file.”

Enter the responsible party and role if known. You can save a task without an owner, but an open task without one receives a flag. A named owner is still an entered claim. The tool does not confirm that the person accepted the assignment or has authority to perform it.

Choose Not started, In progress, Reported complete, or Reported not applicable. The first two are open statuses. The last two are closed for this worksheet's dependency checks. Closed does not mean a professional approved the transaction or that every requirement has been met.

For either closed status, enter a detail or reason, a source reference, and the date the evidence was checked. Reported complete also needs the actual reported completion date. That date cannot follow the evidence check. Reported not applicable needs a reason in the status-detail field and must not contain a completion date.

Open tasks can include evidence too. A source reference and checked date must appear together. You can also leave both blank. Keep the next-action field for unresolved questions, the work to request, and details that do not fit another field. The tool stores references as text and does not open them.

A reservation follow-up is a task, not a determination that an investment has been allocated or accepted. Write the action precisely. For example, “Ask the broker to confirm the current written reservation status” describes work you can track. Marking that inquiry complete says nothing by itself about acceptance of a subscription.

Enter Professional-Confirmed Dates

Only enter a due date in the timing section when you have a confirmation to record. Supply the confirming professional and role, the source, and the date of confirmation. The tool requires these fields but cannot verify the person's credentials, the source, or the date's legal effect.

If timing is unresolved, leave all four timing fields blank. Put the question in Next action. The output will show that no confirmed due date has been entered. It will not assume there is no deadline or select a date from a standard exchange formula.

This distinction matters because exchange timing has legal rules. The IRS's 2025 Form 8824 instructions describe identification within 45 days after the property given up is transferred. Receipt must occur by the earlier of the 180th day after that transfer or the tax-return due date, including extensions, for the year of the transfer. Your actual facts and applicable rules must be reviewed by the appropriate professionals. IRS Form 8824 instructions.

The tracker does not calculate those dates, decide whether relief applies, or extend any deadline. It accepts the date you entered with its stated confirmation. A date-passed flag is a reason to follow up, not a tax conclusion. A date that has not passed is not proof that every timing requirement is satisfied.

Use the source note to preserve details about time of day or delivery rules. Discuss those details directly with the people responsible. The calendar flag will still operate only at the day level. Do not use it to decide whether a same-day filing, transfer, or submission was timely.

Connect Tasks With Prerequisite IDs

Each saved task receives a stable ID such as K1 or K2. To show that a task depends on earlier work, enter the saved IDs separated by commas. Every referenced task must already exist. A task cannot refer to itself, repeat an ID, or create a circular chain.

For example, K3 can depend on K2, and K2 can depend on K1. When reviewing K3, the tracker checks both K2 and K1. It follows all entered links, even through a task marked complete or not applicable. This helps reveal a closed task whose earlier work is still reported open.

The tracker does not decide which links are correct. Ask the team to confirm them. Some steps can happen in parallel, and others have conditions that a simple link cannot capture. Add those limits in the task text rather than treating the software's graph as a legal or operational rule.

To change a dependency, edit the task that contains the reference. You cannot delete a task while another task refers to it. Remove or correct the reference first. This prevents a deleted prerequisite from silently disappearing from the work list.

Task IDs are not reused after deletion within the same tracker. The remaining tasks keep their identifiers, and a new task gets the next number. Titles and categories stay fixed when editing. If the work's identity changes, add a new task and deliberately update the links that should point to it.

Read the Fictional Exchange Example

Load fictional example replaces the current file after confirmation. It contains six invented tasks reviewed as of October 16, 2026. All people, evidence, confirmations, dates, and transaction details are made up. They are not suggested dates for a real exchange.

K1 concerns collecting current instructions and is reported complete. K2 concerns obtaining funding confirmation, is in progress, and depends on K1. Its entered due date is October 15, one calendar day before the review cutoff.

K3 asks for a reservation status reconfirmation and depends on K2. It is not started and is due on the review date. K4 concerns sending a complete packet, depends on K1, K2, and K3, and has no assigned owner. Its entered date is October 19, three calendar days after the cutoff.

K5 concerns an optional outside review that is reported not applicable for the invented assignment. Its reason and evidence are recorded. That fictional scope decision does not establish whether an actual investor needs outside advice.

K6 is a coordinator handoff check reported complete on October 15. Yet it depends on K4, which remains open. Following K4's links also reveals open K2 and K3. The tracker keeps the reported completion and flags the unresolved prerequisites. It does not silently reopen K6 or assume the earlier tasks were finished.

The summary contains six tasks: two reported complete, one reported not applicable, and three open. Two open tasks have unresolved prerequisites. One closed task has unresolved prerequisites. One open task lacks an owner. Among open tasks, one date has passed, one falls on the cutoff, and one falls within the next seven days.

K4 refers to K2 directly and also reaches it through K3. K2 appears once in K4's list of unresolved prerequisites. The tracker counts distinct task IDs, so repeated paths do not create extra unfinished tasks. That makes the chain easier to discuss without inflating the work count.

Understand Timing and Dependency Flags

Open tasks are grouped into five timing states: date passed, due on the review date, due within the next seven calendar days, due later, and no confirmed date. The seven-day group covers one through seven days after the cutoff. It excludes tasks due on the cutoff itself.

The day difference uses calendar dates in UTC for arithmetic. It is not an elapsed-hour measure. October 16 to October 19 is three calendar days whether a weekend falls between them or not. The tool makes no adjustment for a provider's hours or a document's delivery terms.

For a reported-complete task, the tool can flag a completion date later than the entered due date. It does not decide whether an exception, extension, or different interpretation applies. A not-applicable task does not receive that late-completion flag because it has no completion date.

Flags can overlap. K4 is open, lacks an owner, has unresolved prerequisites, and is due within seven days. Those are four observations about one task. Adding the flag counts together would overstate the number of tasks. Use the task IDs to see which issues belong together.

An open task with no unresolved linked prerequisites is not automatically ready for action. The list may omit a requirement or contain an incorrect status. The output only describes the links and records you entered. Likewise, zero open tasks does not establish that the proposed purchase or exchange is approved.

Update the Record and Download a Snapshot

Save or cancel an unsaved task before reviewing the file or changing another task. Any input change clears results and disables downloads. This prevents old output from appearing to reflect a new cutoff, source note, or task status.

Failed saves leave the earlier saved tasks in place. Read the message and fix the entry. For example, a completion date after its evidence check is rejected. A new circular dependency is also rejected. The tracker will not silently remove the conflicting link to make the save succeed.

Editing replaces the saved task's current snapshot. It does not retain a version history. Download before you change a record if you need to keep the earlier state. The JSON file preserves the entered tasks and calculated flags; the text file presents the same source details and results in a readable report.

Downloads do not create a shared workspace or notify anyone. The tracker has no import function or automatic storage. Leaving or reloading the page can discard your work. Keep a downloaded file where you normally maintain the transaction record, and share it only through your own authorized process.

Use the Tracker in a Coordination Call

Start with open tasks whose dates have passed or fall soon. Then review owners and unresolved prerequisites. Ask whether the record is correct before treating a flag as a service failure. A missing status update and genuinely unfinished work require different responses.

Use the contradiction flag to ask a focused question. In the example, the question is why K6 is marked complete while K4 remains open. Perhaps the dependency is wrong, the completion report is wrong, or a task needs a narrower title. Resolve the source record rather than simply changing whichever status removes the warning.

Processing progress also remains separate from investment risk. The SEC's private-placement bulletin, updated September 21, 2026, discusses limited information, resale difficulty, and potential losses. Finishing a document checklist does not resolve those issues. SEC private-placement bulletin.

At the end of the call, agree on who will confirm each material change and what evidence will support it. Update the cutoff when appropriate, rerun the review, and save the new snapshot. That creates a usable work record without turning a task count into an investment or tax judgment.

Frequently Asked Questions

Does the tracker calculate my 45-day or 180-day exchange deadline?

No. Enter dates confirmed for your situation by the relevant professionals, along with the source and confirmation date. The tool compares entered dates with a review cutoff. It does not apply tax rules, exceptions, return deadlines, or relief provisions.

Does a completed reservation task mean my DST purchase was accepted?

No. It means the particular task is reported complete with entered evidence. Confirming a reservation's status is different from an accepted subscription or completed purchase. State the work precisely and keep the actual transaction status in the appropriate documents.

Why can a completed task still have an unresolved-prerequisite flag?

The tracker follows all entered links, including those behind closed tasks. If a linked earlier task is still open, the conflict remains visible. The software preserves both facts and asks you to reconcile them. It does not assume either record is correct.

Can I save a task when I do not know its owner or deadline?

Yes. An open task without an owner is flagged. A task without a confirmed date stays in a separate timing group. Leave all deadline-confirmation fields blank and put the timing question in Next action. Missing information is not treated as no requirement.

Does the tracker send reminders or keep my work after I leave?

No. It works in the current page and has no automatic storage or ongoing alerts. Review and download the current file before leaving. The saved export is a snapshot, and the tool does not import it back into a new session.

Can I remove a prerequisite that another task uses?

You must first edit the tasks that refer to it. A removal with live references is rejected, keeping the saved list intact. Correct the links deliberately, then remove the task if appropriate. Remaining IDs stay the same, and deleted IDs are not reused within that tracker.

About Sequoia Research

Sequoia Research creates educational articles and tools for evaluating real estate investments and related services. We explain source limits, calculations, and questions to raise with the professionals involved. This tracker organizes user-entered work records and does not provide personalized investment, legal, or tax advice.

Sources