[Link to Decision Document]
These are the primary steps required to complete a project ban. It's important to create one single thread, with all accountable to ensure that completion of each steps triggers the next.
Account | System | Accountable | Action Completed? | |
---|---|---|---|---|
- Collect a list of all areas where this person is known to participates.
- Report back to the group email on completion.
- Based on the above, create a checklist of systems, accountable people, and status using this document.
- Draft an email to system administrators to send on step 4. Here's a template
- Draft an email for 'needs to know steaff and contributors' Here's a template
- Draft an ban email Here's a template
- Report back to the group email on completion.
STEP 3: Communicate the ban to the individual, and those who need to know about the ban (but are not directly involved in this decision)[Accountable Name]
- Email ‘needs to know staff and contributors’.
- Email ban letter.
- Report back to the group email on completion.
Note: systems ban always comes after notification, if there is any chance there will be a delay between notification and systems which can confuse, or even panic those involved.
- Request/complete action according to our systems document, and ensure completion for each. [Here's a Template]
- Report back to the group email on completion.
- Before closing this case, a quick check in with everyone involved (stakeholders, and system adminstrators). [Template Here]
- Report back to the group email on completion
- Case Closed
- Report back to the group email on completion