Junipa plans empowers educators to focus on the work that matters, removing the the need to perform manual, repetitive tasks on student plans. With Junipa plans’s in-built workflow, your school or college can handle the most complex plan management scenarios.

This guide will outline the key concepts you need to know to get started, help you set up your first plan, and will outline the common use cases you can apply to your school and well-being team.

A referral is an observable event that has an impact on a student. A referral is often the starting point of adjusting plans for a student within the Junipa plans ecosystem.

After a staff member has raised a referral, that referral will be moderated by a triage officer. The triage officer will typically approve and progress the referral to a Case Conference or may reject the referral.

A case conference typically follows a triage of a referral, and is a digital record of the physical meeting where stakeholders meet to discuss a student’s referral(s). A case conference may then progress to the Plan and Blueprint stage, whereby tasks are assigned to staff and individual plans are assigned to that that student.

Junipa plans defines a blueprint as the culmination of:

For a referral and blueprint to work it is critical that each plan has been designed with consideration.

The smallest building block of any student plan is a data field. A data field can be an input text field, a date field or any other of Junipa plan’s supported data fields.

A collection of data fields is a data point. Junipa plan’s workflow becomes increasingly more powerful when a data point can be re used amongst numerous plans. Data points are only stored once per student, introducing the powerful data sharing capability of the system.

Once a collection of data points have been added to a plan design, and the necessary plan approver is assigned we have a plan. Add those plans together with student details and we have a blueprint.

In this page