Build a program curriculum
The Curriculum Builder is on Programs → a program → Curriculum. It holds a three-level plan: a curriculum, its units, and each unit's sessions, plus a fourth level inside every session for activities, materials and assessments.
Three of those four levels can be created from the screen. The fourth cannot, and nothing at any level can be renamed or reordered once created. Read What you cannot do here before planning around it.
Every tab of a program first loads the program's own detail, and that check refuses the role before any tab, including this one, ever renders.
Create a curriculum
- Open the program and choose the Curriculum tab.
- In the left sidebar, press +.
- Enter a Curriculum name, an optional Description and an optional Est. hours.
- Press Create.
The name is capped at 200 characters and the description at 2,000, both matching the underlying storage, so an over-length value comes back as a message naming the field rather than a plain server error. Estimated hours must be zero or greater and is stored to two decimal places.
Correcting a curriculum's name, description or estimated hours is built correctly and reachable from no screen. Whatever you type here is the curriculum's name for as long as it exists. If it is wrong, the only remedy is to delete it and start again.
Add units and sessions
- Select the curriculum in the sidebar.
- Press Add Unit at the bottom of the outline.
- Expand the unit with the chevron, then press Add Session inside it.
Add Unit always sends the same fixed values: the name "New Unit", zero estimated hours, no description and no learning objectives. Add Session always sends the fixed title "New Session", 60 minutes and the type Workshop.
The actions that would let a real name be typed into either afterward are built correctly and reachable from no screen. So every unit in every program is called New Unit, every session is called New Session, every session is a 60-minute Workshop, and no unit has learning objectives.
The outline is therefore a count of items, not a plan anybody can actually read.
Publish a curriculum
- Select the curriculum.
- Press Publish.
Publishing sets a flag and increases the version number. It is one-way: there is no unpublish action and no control that would call one. Nothing else in PTRS actually reads whether a curriculum is published in any way that matters: a published curriculum can still be deleted, cloned, and have units and sessions added to it exactly as a draft one can.
Clone a curriculum
- Select the curriculum.
- Press Clone.
The copy is created immediately, named after the original with "(Copy)" added, as a fresh draft at version 1, inside the same program.
Unlike the program-level Clone, which claims to copy curricula and does not, this one is a genuine deep copy: every unit, every session, and every activity, material and assessment inside every session.
Delete a curriculum, a unit or a session
Each level has a bin icon, and each asks for confirmation first.
None of these deletes can be undone, and every relationship cascades:
- deleting a curriculum removes its units, their sessions, and those sessions' activities, materials and assessments;
- deleting a unit removes its sessions and their contents;
- deleting a session removes its activities, materials and assessments.
Nothing is recoverable, and nothing is kept for a later audit beyond the one line in the activity log naming what was deleted. The confirmation on the curriculum bin reads "Delete this curriculum and all its contents?", which is accurate.
What you cannot do here
Reorder anything by dragging
Units and sessions are shown in a drag-and-drop list with grab handles. Dragging one always fails.
The screen and PTRS disagree on the wording of what is being moved, so PTRS refuses the request with a message naming the wrong term for it.
What you see: the row moves, a red message carries that wording mismatch, and the list reverts to its saved order on the next screen refresh. Nothing is saved.
Each item's position therefore only ever holds the value it was given at creation, the number of items already in the list, so units and sessions stay permanently in the order they were added.
Put anything inside a session
Selecting a session opens a panel with three tabs, activities, materials and assessments, each showing a count and a list.
All three lists are read-only. There is no add control on any of them, and the three actions that would let something be added are all reachable from no screen. Every session in every program shows "No activities yet", "No materials yet" and "No assessments yet", and the counts in the session row stay at zero activities, zero materials, zero assessments.
This is also why nothing can be attached to the resource library: the only thing that can attach a library item to a session is one of these same three unreachable actions.
Attach a session to a date
A curriculum session is meant to link to a real, dated meeting. The action that would set that link is reachable from no screen, and separately, no session can be created at all. So a curriculum is never connected to a calendar.
See a curriculum anywhere but here
No other screen in PTRS reads a curriculum. It does not appear on the program overview, in Analytics, in Attendance, or on a child's record, and the program-level Clone dialog says it copies curricula and does not.
For someone integrating directly
The three session sub-actions are complete, validated, and replace-all: send the full list you want, and the previous contents are removed first. All three check the type field you send against a fixed vocabulary, matching its exact wording.
The two actions that would let a unit or a session be given a real name are the only way to do so, and both work when called directly.
Full list with roles and reachability: Who can do what with curriculum, staffing, goals, assessments and surveys. Field-by-field rules: Curriculum and goal fields.
Where to go next
Checked against PTRS on 7 September 2026.