Resident Wellness Intelligence Pilot

A bounded 90-day evaluation with an objective Day-30 Acceptance Package.

The pilot is designed to answer whether WIS can produce a useful, governed wellness baseline for your agreed cohort before you make a longer-term commitment.

Evaluate pilot fit Review senior-living fit

Fit readiness

Good pilot conditions are the published dependencies already on this page.

This pilot is built to inform one decision: which resident-wellness programs you continue, change, or cut at your next annual budget cycle. That is also the test for the fee and for the internal capital of running a pilot at all. If a governed wellness baseline for your agreed cohort would not change how you make or defend that call, the honest answer is to wait.

Good pilot conditions

Signed agreement, SOW, data/security terms, and any activated BAA is ready or scheduled.
Selected deployment model, approved consent materials, and a completed data-flow review is ready or scheduled.
Named partner lead, authorized users, cohort recruitment, and timely decisions is ready or scheduled.
Credentials, exports, vendor approvals, and contacts for every agreed source is ready or scheduled.

Reasons to wait

Signed agreement, SOW, data/security terms, and any activated BAA is not ready, not selected, or cannot be dated.
Selected deployment model, approved consent materials, and a completed data-flow review is not ready, not selected, or cannot be dated.
Named partner lead, authorized users, cohort recruitment, and timely decisions is not ready, not selected, or cannot be dated.
Credentials, exports, vendor approvals, and contacts for every agreed source is not ready, not selected, or cannot be dated.

Pilot days

From confirmed go-live

Acceptance deadline

Adjusted only for documented partner delay

100%

Fee credit

Applied under the continuation terms below

What the fee buys

Three checkpoints, each with a decision purpose.

The exact scope follows the signed SOW. These are the standard milestone categories, not a promise that optional features or every data source are included.

By Day 7

First-signal preview

A configured cohort workspace, at least one agreed source connected or imported, an available-data preview, and a written dependency and quality exceptions list.

By Day 30

Acceptance Package

The in-scope experiences and staff reporting surface, a cohort wellness baseline with coverage and limitations, role/access documentation, training, and a known-limitations report.

By Day 90

Decision readout

A comparison of available Day-30 and Day-90 patterns, leadership readout, agreed report exports, closeout choices, and an optional continuation proposal.

Risk reversal, precisely stated

The guarantee is about delivery, not outcomes.

Day-30 acceptance is tied to objective criteria in the signed SOW. A valid rejection has a cure period. If NextGen fails to cure a failure within its control, the standard agreement provides termination and a refund of pilot fees paid.

What is not guaranteed

Resident participation, engagement, adoption, clinical outcomes, occupancy, retention, revenue, emergency response, or any particular wellness signal.

What moves the deadline

Only a documented dependency or partner action that prevents scheduled work, and only to the extent it caused the delay. Unaffected work continues.

SOW controls

Day-30 acceptance checklist and responsibility matrix.

Source: Pilot SOW template Exhibit A §§4-6, internal draft reviewed 2026-08-04. The standard pilot ties Day 30 to an objective acceptance package; the signed SOW defines scope, dependencies, and cure terms.

URLs authenticate and load for each agreed role.
Each role sees only data permitted by the SOW, Data Addendum, consent, and BAA.
At least one agreed data source displays its successfully received data.
Baseline identifies cohort size, reporting period, source coverage, methodology version, and material missing-data limitations.
No Severity 1 defect remains open.
NextGen has delivered the training and documents listed in the SOW.
Package materially matches the SOW deliverables, even if participation or data volume is lower than hoped for reasons outside NextGen's control.

Phase	NextGen owner	Partner owner	Required input	Decision date	Dependency
Day -14	NextGen lead.	Partner lead named in the signed SOW.	Signed Agreement, SOW, Data Addendum, and any activated BAA.	Kickoff and Go-Live dates set in the signed SOW.	Required before Day 0 can be confirmed.
Day -7	NextGen lead.	Partner lead and authorized users.	Selected deployment model, completed data-flow review, and approved resident consent and privacy materials.	Consent-materials approval date set in the project plan.	Required before resident data may be processed.
Day 0	NextGen lead confirms Go-Live in writing.	Partner lead.	Critical dependencies complete against the SOW dependency list.	Go-Live date, confirmed in writing.	First business day after signed exhibits and confirmed dependencies.
Day 7	NextGen lead.	Partner source owners.	At least one in-scope source connected or imported, plus a written dependency and quality exceptions list.	Source-ready date, tracked per source.	Credentials, exports, vendor approvals, and a technical contact for each in-scope source.
Day 30	NextGen lead.	Partner lead and agreed reviewing roles.	Day-30 Acceptance Package contents as listed in the signed SOW.	Day-30 acceptance deadline, measured from the Go-Live date.	Written acceptance or rejection window and cure process, per the signed SOW.
Day 90	NextGen lead.	Partner leadership.	Day-90 readout, agreed report exports, closeout choices, and any continuation proposal.	Day-90 end date and continuation decision date, set in the project plan.	Continuation decision criteria agreed before Go-Live.

Inspect the simulated Day-30 package

Before Day 0

Dependencies are part of the commercial truth.

A credible timeline starts only after the legal, consent, access, and operating inputs needed for the agreed scope are ready.

Signed agreement, SOW, data/security terms, and any activated BAA
Selected deployment model, approved consent materials, and a completed data-flow review
Named partner lead, authorized users, cohort recruitment, and timely decisions
Credentials, exports, vendor approvals, and contacts for every agreed source

Continuation is optional

If the pilot earns a next step, the fee can move with you.

Under the standard structure, the $35,000 pilot fee credits against the first subscription fees when a post-pilot WIS subscription starts within 60 days after the Day-90 readout. The credit is nonrefundable, has no cash value, and the onboarding fee is waived.

Evaluate pilot fit

A fit conversation reviews cohort, deployment model, dependencies, timing, and decision criteria. It does not create a booking or contract by itself.