Junipa connects student support, school curriculum and learning delivery

A school curriculum is rarely born inside one system. It starts with an official syllabus, becomes a teaching and learning plan, grows into units, weeks, lessons, assessments and resources, and is changed again by the teacher who knows the class in front of them.

Student support often sits beside that work rather than inside it. A strategy may be carefully recorded against a disability category or adjustment level, but the teacher still has to work out whether it matters for this subject, this week, this task and this student.

Junipa now connects those two bodies of work.

Programs, the Curriculum Calendar, timetable delivery, assessments, resources and the Strategy Library form one pathway from school planning to a student's record. This extends Junipa further into learning delivery while retaining its core purpose: helping schools make support visible, reviewable and accountable.

The program supplies the teaching context. The Strategy Library supplies relevant support options. A staff member decides what was used before it becomes part of the student record.

One connected path, with clear boundaries

The new workflow keeps four related ideas separate.

• A program is the reusable school definition of what will be taught.
• A program delivery is that program placed in time for a teacher, timetable class and cohort.
• The Strategy Library is the school's reusable collection of support approaches.
• A student record contains what staff actually recorded for that student, including the context in which it was used.

That separation matters. A Year 9 Mathematics program used in 2026 should not silently become the same record as its 2027 delivery. A teacher may change the time allocated to a topic, replace a resource or adapt an assessment for the next cohort. Those changes belong to the delivery until a curriculum leader deliberately brings them back into the reusable program.

The same principle applies to strategies. Matching a strategy to a student does not prove that it was delivered. Junipa can surface a relevant strategy and explain why it appeared. A staff member still reviews it, decides whether it fits the lesson and records its use.

Bring existing teaching plans with you

Schools do not need to abandon the documents they already use.

A program can begin as:

1. A blank program created in Junipa.
2. A Microsoft Word document exported from Word or Google Docs.
3. A class discovered through an imported timetable. An LMS connection can also be arranged where the school's integration supports it.

When a document is uploaded, Junipa proposes a structure for review. It can identify the material that commonly makes up a teaching and learning plan, including program details, units, rationale, overview, objectives, learning sequences, weeks, lessons, assessments and resource references.

The original source document remains attached to the program. The activity history records who uploaded it and when. This means the structured program does not replace the provenance of the school authored document.

Document formats vary greatly, so the review step is intentional. Junipa does not claim that every heading or table has one universal meaning. Staff can correct the proposed structure before the program is relied on.

The Programs page keeps the reusable definition visible while showing which programs have entered delivery and where strategy activity exists.

A program becomes a document staff can keep working with

Inside Junipa, the imported plan becomes more than a preview of the Word file. The available unit rationale, overview, objectives and learning sequence remain readable as one continuous document, and sections the school has not completed remain visibly undefined.

Weeks can contain lessons, focus and content, resources and assessments. Staff can make changes through the program editor without turning the page into a spreadsheet of unrelated fields. The source documents and activity history remain available at the bottom when somebody needs to understand where the content came from.

The definition is reusable. It does not require a teacher, class or start date before the school is ready to schedule it.

A reusable unit keeps its school-authored sections together and makes an incomplete section obvious rather than inventing content.

Official curriculum stays beside the school program

The source that informs a program depends on the school and jurisdiction. A Queensland senior subject may be informed by a QCAA syllabus. Another school may use an Australian Curriculum source, a state curriculum authority, an endorsed course or a school authored framework.

Junipa uses the school's jurisdiction and selected subject to present the most relevant official sources first. The program can retain more than one source link when the authority provides both a landing page and a specific syllabus document.

The syllabus mapping opens beside the school program. It can suggest where the subject, unit identity and subject matter align, then let staff move between the official source and the corresponding school content.

This is a comparison aid, not an approval stamp. Curriculum leaders remain responsible for confirming the current official version, the sequence the school will use and whether the program satisfies local requirements.

The source, version and match checks stay visible beside the school-authored unit so leaders can verify the comparison in context.

See the year before it becomes a timetable problem

The Curriculum Calendar gives leaders a curriculum map across the selected calendar year. Programs and units can be viewed in compact two month columns, by school term, by week or in a more detailed vertical view.

Assessment and strategy overlays are optional. With them off, the map stays focused on the shape of the year. With them on, staff can see where an assessment or concentration of student support sits inside the planned sequence.

Selecting a unit opens its program in context. The drawer brings the relevant part of the program into view rather than forcing the user to open a long document and scroll from the beginning.

The calendar is a map of what is planned. The timetable remains the source of who teaches the class and which students are enrolled.

Program delivery connects planning to people

Scheduling a program creates a delivery. The delivery records the date range, teacher, timetable class and students while retaining the link to the reusable program revision.

This is the point where the school definition meets the real class. A teacher can see the unit and week they are responsible for, the students in the class, the relevant resources and any strategies that may need professional attention.

Changes made for that delivery remain identifiable. A school can later compare deliveries, see what changed for a cohort and decide whether a useful change should inform the next reusable version.

The delivery keeps its period, cohort and strategy matches together and shows clearly when changes or effectiveness reviews have not yet been recorded.

The Strategy Library becomes useful in the moment of teaching

A strategy can be organised through several kinds of context:

• Curriculum, subject, program, unit, week or lesson.
• Disability category.
• Adjustment level.
• Medical condition.
• A named student.

These are facets of the same library, not separate lists that staff have to search one by one. When a program delivery has a timetable cohort, Junipa can compare the program context with the student context and surface the strategies that match.

The teacher can see the reason for the match. One suggestion may apply because of the subject and unit. Another may apply because a student has a recorded adjustment level or condition. A student specific strategy remains visibly student specific.

This makes the recommendation explainable. It also protects against a dangerous shortcut: treating every strategy associated with a diagnosis as suitable for every student with that diagnosis.

The library stores reusable guidance. The class and program provide the context that determines what staff should review first.

Staff confirm what happened

A recommendation is not evidence and it is not a completed adjustment.

The staff member delivering the class can review the strategy, record it for all students or select the relevant student, and keep the program, unit, week and lesson context attached. Manual strategies added by the teacher remain distinguishable from suggestions surfaced automatically.

That distinction gives leaders two useful views:

• What the school's existing rules and library suggested for the cohort.
• What staff actually selected or recorded during delivery.

The counts help a curriculum or inclusion leader find where a large number of suggestions exists, where teachers are adding their own strategies, and where a delivery may need closer review. They are not a score of teacher performance.

Assessments and resources belong in the same context

An assessment is part of the unit, not a disconnected result column. Junipa can retain the assessment objective, conditions, due point and linked resources beside the learning sequence.

Schools can define a grading model that matches the assessment. This may be A to E, a percentage, a score such as one to ten, achievement descriptors, or a school specific scale. The result remains attached to the student while the assessment instrument remains part of the program.

Resources can be linked or uploaded and associated with the relevant unit, week or lesson. That gives staff one place to understand what is being taught, what material supports it and what will be assessed.

Assessment details remain inside the unit, with the grading approach and resources visible beside the due point.

The student profile is the durable destination

The program explains what the school intended to teach. The delivery explains who taught it, when and to which class. The student record explains what support was actually recorded for one person.

Bringing those together means a future reviewer can answer more useful questions:

• Which strategy was used?
• Which student was it for?
• What program, unit and week was being delivered?
• Was the strategy suggested by the library or added by the teacher?
• Who recorded it and when?
• Was its effectiveness reviewed?
• Should the school consider using it again?

This is the practical value of the connection. The curriculum provides context to the adjustment. The adjustment provides a support history to the curriculum. The student record keeps the final professional action accountable.

In the class, the recommendations stay beside the students and teaching weeks that give them meaning; staff still decide what was used.

Effectiveness is a review, not a universal score

Different schools and activities need different ways to review effectiveness. A ten point scale may suit one evaluation. A short set of descriptors may suit another. A school may have an established rubric it wants to preserve.

Junipa therefore keeps the grading model configurable and separates the score from the staff member's written observation. A number alone cannot explain whether a strategy was delivered consistently, whether the student accepted it, or whether the task itself changed.

The review can be completed during delivery or after a unit finishes. Every update remains part of the activity history. That allows useful strategies to be considered again without turning one successful use into a permanent rule for every future class.

What Junipa is not doing automatically

It is worth making the limits explicit.

• Importing a document does not guarantee that every school format has been interpreted perfectly.
• Linking a syllabus does not certify curriculum compliance.
• Matching a strategy does not mean the strategy was delivered.
• A suggested strategy does not become evidence until a staff member records what happened.
• Program delivery changes do not silently rewrite historical versions.
• A grade does not translate itself into another school's grading model.

Those limits preserve professional judgement and the audit trail. Junipa's role is to connect the information, make the relevant context easier to see and keep the resulting decision attached to the right record.

A practical way to begin

Start with one current program rather than the whole curriculum archive.

1. Open Curriculum, then Programs.
2. Add a blank program or upload the current Word version.
3. Review the proposed units, weeks, resources and assessments.
4. Select the subject and confirm the relevant syllabus source.
5. Place the program on the Curriculum Calendar.
6. Connect the correct timetable class and confirm the teacher and students.
7. Open the Strategy Library and review which strategies are relevant to the subject and cohort.
8. Ask the teacher to record one strategy from the class curriculum view.
9. Confirm that the student record carries the program and delivery context.

The Curriculum programs guide covers the school workflow. The Adjustment strategies guide explains what staff see and when a strategy becomes part of a student record.