Many care pilots are judged too quickly and too simply. If results are good, leaders may assume the model itself is strong. If results are poor, they may conclude the model failed. In reality, pilots often succeed or fail partly because certain operating conditions were present or absent from the start. Referral quality may have been stronger in one county than another. Staffing continuity may have been unusually good in one site. Partner response times may have made rapid handoff possible in one area and nearly impossible in another. Strong pilot evaluation and learning loops therefore need more than outcome tracking. They need explicit identification of pilot preconditions: the minimum service, system, and governance conditions that must exist if a model is to perform as intended. For organizations developing new service models, this is one of the clearest ways to separate model weakness from context weakness.
In U.S. community services, preconditions matter because pilots are often launched into uneven systems. County commissioners, Medicaid partners, hospital systems, philanthropy, and provider boards increasingly expect leaders to explain not only what happened in the pilot, but under what conditions it happened. They also expect providers to show whether a model needs specific staffing, partner, referral, or data arrangements before it can be judged or scaled responsibly. A preconditions approach makes that visible. It allows leaders to say, with greater honesty, whether the pilot tested the model fairly or exposed it to constraints that would have undermined almost any service design.
Why pilots need explicit preconditions instead of vague assumptions
Every pilot begins with assumptions about what the service will need in order to work. Yet those assumptions are often left implicit. Leaders may believe referral partners will send complete information, that staff capacity will be stable enough to support fidelity, or that key handoff agencies will respond within required windows. When those assumptions fail, the pilot can look weak for reasons not fully internal to the model. Without explicit preconditions, these failures are later described as “implementation challenges” rather than recognized as absent foundations that materially affected performance.
Two explicit oversight expectations should guide this work. First, funders and commissioners increasingly expect providers to show the practical conditions required for a pilot to generate interpretable and scalable evidence, especially where public money or large-system decisions are involved. Second, boards, quality committees, and regulators usually expect leaders to identify where safety, continuity, equity, or rights protections depend on external or operational conditions that must be in place before the model can be regarded as viable. Preconditions analysis meets both expectations by turning tacit dependency into a governed part of pilot design and review.
What counts as a pilot precondition
A precondition is not the same as a hoped-for benefit. It is a condition that must exist or be strong enough for the model to operate fairly and safely. Preconditions may include adequate staffing depth, reliable referral data, clearly defined eligibility, partner response times, usable escalation routes, interpreter access, documentation capability, or minimum supervisory support. The point is not to make the pilot artificially easy. It is to define which conditions are essential enough that, without them, the pilot is no longer a fair test of the model being considered.
Operational example 1: Defining referral-quality preconditions in a discharge support pilot
What happens in day-to-day delivery
A discharge support pilot establishes a precondition review before treating early performance as meaningful. The service manager, analyst, and hospital liaison identify four referral-quality conditions that must be met: timely transmission of discharge notifications, accurate contact information, medication detail sufficient for reconciliation, and named ward contacts for urgent clarification. During the first six weeks, the analyst measures how often these conditions are present by hospital unit and day of discharge. The governance group does not interpret timeliness and follow-up performance in isolation. Instead, it reviews whether the pilot is operating on top of referral conditions strong enough to support the model’s core workflow in the first place.
Why the practice exists and the failure mode it addresses
This practice exists because discharge pilots often appear weaker than they really are when the referral pathway is unstable. The failure mode is judging the service as if it were underperforming internally when, in fact, it is spending a large share of its effort compensating for late, incomplete, or poorly structured referrals. If leaders do not define referral quality as a precondition, they risk mistaking upstream system weakness for model weakness.
What goes wrong if it is absent
Without explicit referral preconditions, the pilot may be described as slow, inconsistent, or unable to deliver its early intervention promise. Staff become frustrated because they are held accountable for gaps created before the case even enters their workflow. Hospital partners hear generic concerns but not specific evidence of what must improve for the model to function as designed. Later evaluation then struggles to show whether weak results reflect service design limits or a flawed launch environment.
What observable outcome it produces
When referral preconditions are defined and monitored, the pilot gains a stronger interpretive base. Observable outcomes include clearer partner discussions about what referral quality must look like, faster correction of weak discharge pathways, more accurate explanation of why performance varies by unit, and a more defensible case for continuation or redesign because leaders can show whether the pilot was operating under conditions that made fair testing possible.
Preconditions should be reviewed across safety, workforce, and partner dependence
A strong preconditions framework does not stop at referral quality. Some models depend on minimum workforce continuity, others on fast external response, and others on specific safety controls being embedded from the start. By reviewing preconditions across several domains, leaders can avoid the common error of assuming that because one part of the environment is strong, the pilot as a whole is ready to be judged. In practice, many models stand or fall on a small number of operating foundations that must all be visible.
Operational example 2: Establishing workforce preconditions in a caregiver respite pilot
What happens in day-to-day delivery
A caregiver respite pilot defines workforce preconditions before judging its continuity and family-trust outcomes. Leaders identify three required conditions: a minimum level of rota stability, supervisory capacity to manage continuity risks, and sufficient geographic clustering to avoid excessive travel disruption. These are measured fortnightly alongside family outcomes and repeat-booking patterns. Rather than assuming low continuity reflects weak staff engagement or family expectations, the governance group checks first whether the workforce preconditions needed to deliver continuity were actually present in each period and location. When one locality repeatedly fails to meet the geographic clustering threshold, the team flags that site as not yet operating under valid continuity conditions.
Why the practice exists and the failure mode it addresses
This practice exists because some pilot benefits depend on workforce conditions that are more foundational than leaders sometimes admit. The failure mode is claiming that the model “works” or “doesn’t work” for continuity and trust without first testing whether the staffing environment made continuity realistically deliverable. If the service cannot maintain basic rota stability or manageable travel design, then poor continuity may reveal an absent precondition rather than a failure of the underlying service concept.
What goes wrong if it is absent
Without workforce preconditions, the pilot can become trapped in unfair interpretation. Staff may be judged against an outcome they could not reliably deliver under the staffing and geography conditions provided. Families experience avoidable inconsistency, and leadership may still treat that inconsistency as proof that the model itself lacks value. Future funders may also receive an inaccurate picture, either of a model that looks unsustainable in principle or of a service that appeared more robust than it would under ordinary staffing conditions.
What observable outcome it produces
When workforce preconditions are reviewed explicitly, leaders can distinguish between a model that needs redesign and a context that needs strengthening first. Observable benefits include better staffing and travel rules, clearer explanation of where continuity results are valid, more realistic commissioner discussions about what permanent operation would require, and stronger evidence that the provider understands the minimum conditions needed for family-facing trust outcomes to hold.
Preconditions analysis helps explain why one site or subgroup succeeds while another struggles
Many cross-site and subgroup differences make more sense when seen through the lens of preconditions. A site may perform well not because the staff are uniquely talented, but because the partner pathway is strong and the caseload is structured appropriately. Another may struggle because key preconditions such as interpreter access or provider acceptance are too weak. Preconditions analysis therefore improves both fairness and scale judgment. It stops leaders from copying superficial success while missing the enabling conditions underneath it.
Operational example 3: Testing partner-response preconditions in a youth follow-up pilot
What happens in day-to-day delivery
A youth follow-up pilot identifies one core precondition for success: receiving providers must be able to accept or meaningfully respond to same-week handoffs for a defined proportion of cases. The program office measures acceptance timing, callback rates, provider-slot availability, and confirmation of next-step ownership across counties. These data are reviewed alongside family engagement and repeat crisis-contact measures. In one county, the pilot appears weaker on follow-up completion, but the deeper review shows that the receiving-provider pathway repeatedly fails the minimum response precondition. The steering group therefore records that the pilot is not yet testing the model under valid partner conditions in that county and pauses any broader interpretation of comparative performance until the partner pathway is improved or redesigned.
Why the practice exists and the failure mode it addresses
This practice exists because many follow-up and care-navigation models rely on partner response conditions so strongly that outcomes cannot be interpreted fairly without them. The failure mode is treating low completion or weaker family experience as evidence against the model when the pilot never had the external response conditions needed to complete its intended intervention. Preconditions analysis protects against judging the model for the absence of a dependency it explicitly requires.
What goes wrong if it is absent
Without partner-response preconditions, one county may be labeled underperforming and another successful even though the difference sits mainly in external provider availability. Staff may become blamed for low completion rates they cannot control, and county leaders may underinvest in the partner pathway that actually needs attention. The final evidence then overstates local execution differences and understates the importance of system readiness.
What observable outcome it produces
When partner preconditions are defined and monitored, the pilot can interpret site differences more honestly and plan expansion more responsibly. Observable outcomes include clearer partner-readiness criteria, more accurate cross-county comparison, stronger commissioner understanding of what the model requires to work, and better protection against scaling the service into environments where the minimum external conditions still do not exist.
What leaders should ask about pilot preconditions
Leaders should ask which conditions must be true before the model can be judged fairly, how those conditions are being monitored, where they are absent, and whether poor performance reflects the model itself or a failure to meet one of its essential foundations. They should also expect the pilot to distinguish between preconditions that are negotiable and those that are non-negotiable for safety, fidelity, or meaningful evidence.
The strongest U.S. pilots do not assume that a live service environment is automatically a fair test. They identify the conditions the model actually needs, examine whether those conditions exist, and interpret results in light of that reality. That is what makes preconditions analysis so valuable. It prevents avoidable misjudgment, sharpens redesign and scale decisions, and helps organizations present a much more defensible account of what their pilot truly showed.