Use the Amilia class, registration, capacity, participant, and policy pages you are already signed into to prepare an administration review around the actual programme context. It stages cases instead of changing enrolments, schedules, refunds, or participant messages, because an unchecked write can alter someone’s booking, attendance, or payment.
01
Programme briefs can be prepared from what is live.
Participants are affected by small administrative decisions, so coordinators need the actual programme context first. Strawberry can package that context for review.
02
Member-service cases keep the relevant context together.
For Amilia, the selected browser pages can become a reviewable work packet that separates visible facts from decisions still owned by a person.
03
Schedule checklists should be checked before an external action.
For Amilia, the useful outcome is a clear draft or investigation record rather than an unattended change in a live account.
04
Administration review queues can arrive on a dependable cadence.
Every Wednesday, the pass reads the saved programme and registration pages, groups capacity, schedule, and policy exceptions, and prepares the cases that need an administrator. It never enrols or moves a participant, issues a refund, or sends a message: an unchecked write can change attendance or money owed.
It can use the signed-in Amilia pages you open to prepare programme briefs, member-service cases, and review-ready handoffs.
No. In Amilia, any external message, publication, record change, or spend requires explicit approval.
Yes. A Wednesday pass can bring capacity conflicts and incomplete registration cases into one queue. Enrolments, schedule moves, refunds, and family messages remain a staff decision.
No. Amilia remains the operational workspace; Strawberry helps your team prepare and review work around it.
Amilia Strawberry