Senior Care Sale Timeline LOI to Close: Dependencies

Define the start and finish events

A useful sale timeline starts with a clear event and ends with a defined result. Signing a letter of intent, opening the data room and submitting an application are different starting points. Likewise, signing documents, releasing funds and gaining operating authority may occur at different times. Name each event before assigning dates.

Use the actual letter-of-intent guide to identify the parties' commitments and milestones. Read the signed terms rather than assuming every LOI has the same effect. Then create a schedule for the work those terms require. Keep obligations and planning estimates in separate fields.

The example below models internal preparation for an invented care-business transaction. It does not forecast how long a regulator or lender will take. Its finish is internal task readiness. Actual closing still depends on the required documents, funds and permissions for the particular business.

Assign one person to maintain the schedule and one owner to each task. Record when the schedule was last updated. A date without an owner or a defined deliverable is difficult to manage and easy to mistake for a commitment someone has actually made.

Classify notices before setting dates

Identify which events trigger a notice, application or other required action. Under 42 CFR 489.18, a provider contemplating or negotiating a covered ownership change must notify CMS. The regulation defines relevant ownership events and addresses assigned provider agreements. It does not provide a universal acquisition processing time. (Source: eCFR: 42 CFR 489.18)

CMS-855A distinguishes reporting paths and the information supplied by the parties. The form's CHOW section calls for different seller and buyer application content. It also addresses the bill of sale and final sales agreement. Confirm the applicable path before treating a generic application task as complete. (Source: CMS: institutional-provider enrollment application CMS-855A)

The Medicare CHOW guide explains the participation context. A task labeled “Medicare complete” is too vague for a schedule. Specify the application, response or other evidence that the particular milestone requires.

Turn deliverables into dependencies

Break broad workstreams into deliverables that another person can inspect. “Legal review” might mean a marked draft, a resolved issue list or approved signing documents. Those are different outputs. State which output must exist before the next task starts and who decides whether it is usable.

Separate a true dependency from a preference. Some document reviews can run in parallel once the common information packet is ready. Another task may need all three review results before it can begin. The schedule should show those relationships instead of placing every activity in one long sequence.

Record capacity limits as well. Two tasks cannot run in parallel merely because the diagram says so if the same person must perform both at the same time. Either allocate separate resources or add the real sequencing constraint. Keep that assumption visible when comparing alternative schedules.

The due-diligence timing FAQ addresses the broader question of how long review takes. The method here helps explain a particular plan: which deliverables exist, what depends on them and which unresolved inputs prevent the team from establishing a reliable date.

Identify the controlling internal path

When several tasks run in parallel, their durations should not all be added to elapsed time. The next shared task waits for the latest required finish. That branch controls the modeled completion date. Other branches may have some room to finish later without moving that date.

That room is called slack in this guide. It exists only within the stated model. A task may still have its own contract deadline or practical constraint. Finishing inside the model's slack does not excuse missing a separate notice, commitment or required action.

Test the network against the actual deliverables. A short task can control the schedule if it begins late because a predecessor is missing. A long task may have little effect on closing if it can begin well in advance. Duration alone does not establish priority.

Use closing contingencies to identify what evidence matters at the end. This guide calculates relationships among scheduled tasks. It does not replace the legal review of a condition or give the parties authority to waive a regulatory requirement.

Calculate a fictional readiness schedule

All durations below are invented scheduled internal work, measured in elapsed calendar days. Day 0 is the starting boundary. A six-day task beginning at Day 0 ends at Day 6. A successor starts at its predecessor's finish boundary. The model does not adjust for weekends, holidays or real staff availability.

Assume separate teams can perform the three middle reviews in parallel. The lender task means preparing the team's package, not obtaining lender approval. The property task concerns document work, not an inspection or permit decision. The final task is internal handoff practice, not permission to operate.

The calculation is six plus the largest of twelve, eight and ten, plus five, plus three: twenty-six days. Adding every duration would give forty-four days and incorrectly treat parallel work as sequential. Both the dependencies and separate-team assumption are necessary for the twenty-six-day result.

Test delay and available slack

In the base case, legal review finishes at Day 18 and controls the shared review's start. The lender package finishes four days earlier, at Day 14. Property documents finish two days earlier, at Day 16. Their modeled slack is four days and two days respectively.

Each row changes only one base-case assumption. Do not add the three results together. If several tasks change at once, recompute their actual finish boundaries and take the latest required one. Also check whether the changes create new work or alter a dependency.

Slack can disappear as the plan changes. A lender-package delay that seems harmless today may matter after legal review finishes early. Update the network when a material duration or relationship changes. A fixed list of “critical tasks” can become outdated even when the overall project remains the same.

Keep external permission outside invented durations

The fictional twenty-six days do not establish a closing date. Suppose the required operating permission has no confirmed effective date. The internal tasks can finish while that external condition remains open. Record “date not established” rather than filling the gap with a familiar market estimate.

Actual notice rules can also set boundaries that the internal model does not address. Washington's adult family home rule requires written notice sixty calendar days before the proposed ownership change. It specifies recipients and contents, including the resident's choice to stay or move. That is a scoped notice requirement, not a licensing turnaround guarantee. (Source: Washington WAC 388-76-10106: ownership notice)

Florida section 408.807 separately requires a transferor's advance notice under its applicable licensing framework. It also retains transferor responsibility for lawful operations and client welfare until the transferee is licensed. These requirements should be reviewed for the actual provider; they are not inputs to the fictional task durations. (Source: Florida Legislature: section 408.807 ownership changes and responsibilities)

The state licensing overview helps identify the relevant process. Have the appropriate reviewer confirm dates and prerequisites. An attractive internal schedule cannot shorten a statutory requirement or grant operating authority.

Track expiry and rework

Keep a separate register of document expirations and dated commitments. Record the actual document, its effective period, required conditions and responsible contact. A planned closing move may require an extension, refreshed evidence or a revised approval. Do not assume every commitment moves with the spreadsheet.

Track rework as a real task. If the purchasing entity changes after document review, identify which completed outputs need another review. Mark the affected versions clearly. Leaving the old task as complete while silently replacing its inputs makes the schedule look more reliable than it is.

Maintain a short decision history explaining why dates changed. Distinguish added scope, missing information, capacity limits and external responses. Those causes require different actions. A general “delay” label does not tell the team whether to supply a record, allocate help or await a decision.

The owner-training guide helps define handoff work with specific deliverables. Practice can expose missing access or unclear responsibilities before closing. It should not be treated as authority for the buyer to begin regulated operations early.

Run a short decision-focused schedule review

At each review, ask what changed since the last version, which finish now controls the next shared task and which external conditions remain open. Focus on decisions that someone can make. Avoid spending the meeting restating completed tasks while a missing input has no owner.

Check the evidence behind claimed progress. A draft package is different from a submitted package, and submission is different from acceptance. Use a few clearly defined statuses rather than a percentage that nobody can reproduce. Identify exactly what remains before the next task can start.

Review the proposed finish against funds, documents and operating authority. The closing guide addresses that release decision. Internal readiness is one useful input. It cannot substitute for the final evidence required by the parties, lender or responsible authorities.

Send a concise updated schedule with changed assumptions highlighted. Include the unresolved external dates and decisions needed. A reader should be able to see why the date moved without comparing dozens of old spreadsheet cells or interpreting an unexplained colored status.

Common mistakes

One mistake is adding every task duration even when work can run in parallel. Another is assuming parallel work without enough people to perform it. State the dependencies and resource assumptions together, then calculate the latest required finish at each joining point.

A further mistake is treating notice days as agency processing time. The Washington and Florida examples apply to their stated scopes. They do not establish a national sale timeline. Confirm the actual rule, trigger and required evidence rather than borrowing a number from another transaction.

Do not confuse a completed internal schedule with permission to close. The fictional model ends at Day 26 while an external condition may remain unresolved. Keep that gap visible and resist turning an unknown response date into a promise to the seller, buyer or people receiving care.

Summary

A useful LOI-to-close schedule names the start and finish events, defines inspectable deliverables and connects them through real dependencies. It models parallel work only when resources permit it. It also shows how a changed task can consume slack or become the new controlling branch.

Keep legal notice boundaries, external decisions and expiring commitments separate from invented internal durations. Use the senior-care resource library to connect the schedule with diligence, licensing and handoff work. The result should explain what the team can manage and which evidence is still needed before a closing date can be relied on.