Programme Setup & Project Assignment
A focused path from the operational list to programme creation, review, programme detail, and intake-scoped assigned projects.
Create flow
Use a TOA stepper wrapper only for the multi-step task. The stepper is not an official PRIZM primitive.
Details
Programme title, education level, application form preview, and description.
Intakes
Application and internship windows, intake capacity, and relevant scheduling data.
Review
Read-only summary with clear edit links and final confirmation.
Programme Detail
Open the created object with compact metrics, metadata, intakes, and assigned projects.
Programme Detail IA
Follow a stable information hierarchy rather than repeating create-form sections as equally weighted cards.
| Order | Section | Content |
|---|---|---|
| 1 | Header | Programme name, one primary lifecycle status, and actions. |
| 2 | Summary metrics | Intakes, assigned projects, shared projects, and placements. |
| 3 | Programme details | Education level, application form, description, and stable metadata. |
| 4 | Intake windows | Application period, internship period, and the project relationship. |
| 5 | Assigned projects | Projects shown inside the selected or expanded intake. |
| 6 | Timeline and preview | Programme timeline and read-only application form preview. |
Project assignment
Projects belong to intakes. Keep assignment and placement configuration close to the selected intake context.
Recommended split view
- Left: intake overview and selection
- Right: matching projects for the selected intake
- Drawer or detail panel: placement configuration after assignment
Alternative accordion
- Expand one intake at a time
- Keep assigned and matching projects inside the intake
- Suitable when the programme contains many intakes
Do not rename the section “Confirmed Projects.” Avoid repeating the intake date range beside the section heading when the selected intake is already clear.
Key rules
Use
- Breadcrumb and one page title
- Semantic surfaces, borders, and PRIZM button variants
- Read-only application form preview modal
- Compact metadata typography
Avoid
- Presenting TOA wrappers as official PRIZM components
- Duplicating lifecycle status across sections
- Oversized body copy inside cards
- Projects shown outside their intake context