Cancelling events and occurrences
Cancelling an event keeps the record but marks it as withdrawn. That’s almost always preferable to deleting — it gives staff, parents and students visibility that something was meant to …
Cancelling an event keeps the record but marks it as withdrawn. That’s almost always preferable to deleting — it gives staff, parents and students visibility that something was meant to …
Events change. Times shift, locations swap, audiences expand. PortalHQ lets you edit any field on an event, but some changes are significant enough to need fresh approval. Who can edit …
Events often involve more than one venue and more than the organiser alone. The Locations and Additional staff sections let you record both, and additional staff can endorse their involvement …
Beyond the basic event details, most events need some kind of operational support — meals, microphones, table layout, transport. PortalHQ tracks these as structured requirements per location, so the canteen, …
When an event is submitted, it appears in the approval dashboard of everyone in the first approval group. As an approver, you decide whether the event moves on, returns to …
A new event starts as a Draft. It’s visible only to you and doesn’t notify anyone. Submitting it moves it to Pending and starts the approval workflow. Before you submit …
A recurring event is a single event record with a rule that generates many occurrences — for example, every Wednesday at 3 pm for Term 2. Individual occurrences can be …
A one-off event is a single occurrence on a specific date and time. This is the most common workflow when a staff member wants to put something on the school …
All events run by the school are entered into this module and go through one or more steps of approval before being plotted on the calendar. The event organisers are …