Skip to content

Commit

Permalink
Merge branch 'comp-teams-no-show-process'
Browse files Browse the repository at this point in the history
  • Loading branch information
PeterJCLaw committed Nov 8, 2024
2 parents e9e769b + 7270dbb commit 7d65f85
Show file tree
Hide file tree
Showing 2 changed files with 31 additions and 0 deletions.
1 change: 1 addition & 0 deletions comp/main.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -54,4 +54,5 @@ dependencies:
- comp/banner
- comp/ops/compbox
- comp/team-checkup
- comp/teams-no-show
- comp/retro
30 changes: 30 additions & 0 deletions comp/teams-no-show.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,30 @@
summary: Define a process for teams which don't turn up to $SRYYYY events

priority: should

component: Competition

milestone: $SRYYYY Competition

area-owner: teams

description: >-
While we do confirm with teams ahead of time whether they're going to turn
up to our events, inevitably some don't turn up or are late arriving.
We should have a process for reacting to this, both in terms of how we'll
communicate with the team and how we'll communicate and respond internally.
This could be that we'll call the supervisor a few times, though defining things like:
- how we'll know they're absent (e.g: check with reception)
- how long to wait after the start of the event
- how much to try to get in contact with the supervisor (if e.g: the call goes to voicemail)
- what triggers contacting the secondary contact
- if/when we drop them out of the competition (if applicable to the event)
This procedure might be the same for all events or might be different by event.
Required actions:
- [ ] Define process for Kickstart
- [ ] Define process for Tech Days
- [ ] Define process for Competition

0 comments on commit 7d65f85

Please sign in to comment.