Understand your enrolled base
Read stages, the funnel, and what’s blocking progress
In the Texture dashboard, open Programs → Enrollments. Use the program selector in the page header to view every program or one program.
Stages#
Each enrollment sits in a stage of the program’s enrollment lifecycle. Default stages:
| Stage | Meaning |
|---|---|
| Intake | Application and contact information are being collected. |
| Qualification | Eligibility and program requirements are being checked. |
| Enrolled | Active in the program. |
| Not Enrolled | Did not qualify, or withdrew before becoming enrolled. |
| Unenrolling | Was enrolled; removal requested and still processing. |
| Unenrolled | Was enrolled; now removed. |
Your program may use these names or custom stage names from its enrollment flow.
Reading the list#
Scan the Blocking column to find who needs attention. It tells you why an enrollment isn’t moving: whether a member hasn’t completed required fields, whether a system condition is unresolved, or whether the enrollment is ready to advance. The Requirements column gives a count (for example, 2/3 met) so you can triage at a glance without opening each record.
Enrollment funnel#
When a single program is selected and the funnel is enabled for that program, Enrollment Funnel shows cumulative counts through the stages: how many reached each stage or any later stage. A sharp drop between two stages usually points to a friction point: a required field that’s hard to complete, a qualification step rejecting too many members, or an integration that’s stalling.
Opening an enrollment#
Click a row when the list view isn’t enough. The detail page shows the full lifecycle timeline, submitted data (Instance Data), and an audit trail of every stage and data change. Use it to find the exact missing requirement, review what a member submitted, or trace how an enrollment moved between stages.
What to follow up on vs escalate#
Resolving what you find here usually requires action outside the Texture platform: following up with the member, checking an integration, or escalating to Texture.
| What you see | Typical next step |
|---|---|
| Missing: [field slugs] | Follow up with the member to complete the enrollment form or supply the missing information. The slugs map back to the fields you configured in the enrollment flow. |
| Waiting for data | The stage is waiting on a condition or system input that isn’t a simple form field; check whether a device connection or partner step is still pending, and escalate if it stays stuck. |
| Ready → [stage] | Requirements are met and a transition is ready to fire. Transitions process automatically; if this state persists without the enrollment advancing, escalate. |
| Stuck in Qualification / Intake with no clear missing fields | Often eligibility, OEM, or utility integration. Escalate to Texture (or your implementation contact) with the enrollment and instance ID from the detail page. |
| Enrolled, but device won’t dispatch | That’s a readiness issue, not an enrollment stage issue. See Check device readiness before an event. |