Event operations
Event operations
Loading the fictional workflows…
What the compact model has to work around
These constraints belong to the program, not to any one event, so every workflow below inherits them.
Event
Event
Decision gate
What has to be true before the rest of this workflow exists.
Planning sequence
The event is not the day. It is the deadlines that lead to it.
Run of show
Every time carries its own certainty: exact, estimated, a range, relative to a slot, or not yet known.
Entries
Event codes, not people. A whole day can be scheduled and published without a single name.
| Code | Entry | Assignment | Equipment | Status |
|---|
Groups and role codes
Who does what, expressed as codes the director assigns.
Overlays and audiences
The family view
Shorter on purpose. It is a different document, not a filtered copy of the staff run sheet.
Documents this workflow produces
Closeout
What this workflow shows
Adult operations only. Every person here is a role or candidate code the director assigns; Program Core holds no learner records, and this demo cannot open a live organization.