Day-30 Acceptance Package

Inspect a simulated package before evaluating pilot fit.

This artifact shows the structure a Day-30 package can make inspectable: cohort baseline, coverage, missing data, known limitations, roles, training, and acceptance controls.

Review pilot structure Evidence status

Simulated data. Not resident results.

Cohort baseline across eight dimensions

Simulated community, N=52. Dimension values are illustrative and not resident results.

Physical

Coverage: High

Emotional

Coverage: Medium

Social

Coverage: Medium

Intellectual

Coverage: Low

Spiritual

Coverage: Medium

Occupational

Coverage: Low

Environmental

Coverage: High

Financial

Coverage: Low

Simulated data. Not resident results.

Coverage and missing-data table

Source	Status	Coverage	Limitation
Resident-authorized check-ins	Received	41 of 52 simulated residents	Seven-day response gaps remain visible.
Class/event attendance export	Partial	28 of 52 simulated residents	Two activity categories are not mapped.
Dining attendance export	Missing	0 of 52 simulated residents	Source not received in this synthetic package.
Environmental/weather feed	Received	Community-level only	Not resident-identifiable.

Simulated data. Not resident results.

Known-limitations report

Synthetic package for inspection only; it is not resident results.
Coverage varies by simulated source and is shown beside the baseline.
The package does not diagnose, treat, monitor emergencies, or predict resident outcomes.
The simulated baseline can support review questions only when paired with source coverage and missing-data limits.

Simulated data. Not resident results.

Role/access document

Resident account

Access is limited to data permitted by the SOW, Data Addendum, consent, and any activated BAA.

Authorized family viewer where in scope

Access is limited to data permitted by the SOW, Data Addendum, consent, and any activated BAA.

Partner staff dashboard

Access is limited to data permitted by the SOW, Data Addendum, consent, and any activated BAA.

NextGen support role

Access is limited to data permitted by the SOW, Data Addendum, consent, and any activated BAA.

Simulated data. Not resident results.

Training and acceptance controls

Source: Pilot SOW template Exhibit A §§4-6, internal draft reviewed 2026-08-04.

Confirm agreed roles can authenticate.
Review what each role is permitted to see.
Walk through the cohort baseline, coverage table, and limitations report.
Confirm support contact and rejection/cure process from the SOW.
Hand over the administrator guide named in the SOW deliverables.

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.

Simulated data. Not resident results.

Responsibility matrix

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.