Pathways help your team define the structure you use to track a participant's progress through a program, service, course requirement, milestone plan, or support workflow. Each pathway lives in the Pathway Library and can be configured as a simple one-step pathway or as a multi-step workflow with separate phases.
Equip may use your organization's participant label, such as student, client, member, or resident. The setup process is the same across CRP, Higher Ed, and other program models.
đ How It Works
Start by deciding whether the pathway needs one trackable step or multiple steps. This choice controls how team members will track progress later.
Single Step works best when the pathway is one service, requirement, or milestone. Equip uses the pathway name and description as the step details.
Multiple Steps works best when team members need to track separate phases, services, courses, milestones, or requirements within the same pathway.
âď¸ Create a Pathway
Open Pathway Library from the Pathways area.
Select Add Pathway.
Choose a Step Configuration: Single Step or Multiple Steps.
Enter the pathway Name and optional Description.
Add any Categories your team uses to organize pathways or report on groups of pathways.
If you chose Multiple Steps, complete Configure First Step with a Step Name, optional Code, and optional Step Description.
If authorization or billing tools are enabled for your account, use Billable, Price, and Price By when the step should support billing-related workflows.
Select Create Pathway.
After the pathway is created, open it from Pathway Library. For multi-step pathways, use Add Step to add the remaining steps in the workflow.
â Benefits
Clear program structure â define the services, milestones, phases, or requirements team members should follow.
Consistent progress tracking â give team members a shared way to see where each participant is in the pathway.
Segment flexibility â support CRP workflows, Higher Ed student support workflows, and other structured program models without changing the setup process.
Reporting-ready data â use pathway names, steps, categories, dates, and custom fields in pathway reporting.
đ§ Customization Options
Categories organize pathways for filtering and reporting.
Codes can be used for internal references, billing codes, course or service identifiers, or reporting needs.
Custom Fields capture structured information on each participant's pathway or step progress.
Billable, Price, and Price By appear when pathway authorization or billing features are enabled for your account.
đĄ Best Practices
Use pathway names that match the language team members already use for the program, service, course sequence, or support plan.
Choose Single Step when team members only need one progress record. Choose Multiple Steps when each phase needs its own status, dates, forms, billing details, or custom fields.
Keep step names short and specific so they are easy to scan in progress views and reports.
Add Categories before team members begin using pathways if your team plans to report by program area, service type, or cohort.
Review the pathway setup before assigning it to participants, especially if the pathway uses billing fields, required forms, or custom fields.
â FAQs
Can Higher Ed programs use Pathways?
Yes. Higher Ed teams can use pathways to track student support workflows, program milestones, course or service requirements, or other structured progress plans.
Can CRPs use Pathways?
Yes. CRPs can use pathways to track services, steps, authorizations, billing-related fields, forms, and participant progress when those tools are enabled for the account.
What is the difference between a pathway and a step?
A pathway is the overall structure. A step is a specific phase, service, milestone, requirement, or activity inside that pathway.
Can I add steps after creating a pathway?
Yes. Open the pathway and select Add Step to add more steps. Review active progress before making major changes to a pathway that team members are already using.
Do all pathways need billing fields?
No. Billing fields only apply when your account uses pathway authorization or billing workflows.