Student death protocol

Summary
Description of actions taken at Fontys ICT in the event of a student's death as a supplement to the Fontys protocol.

Introduction

The death of a student has a huge impact on everyone involved. Fontys has developed a protocol (which is also accessible via the Fontys ICT Portal) to act appropriately on an organisational and administrative level in the event of this event. For the Fontys ICT community, some additional assistance is provided below.

First responsible

A case manager will be appointed as the first person responsible. This is responsible for the entire process and communication when a student dies. In principle, the case manager is a Operations Manager (UM) from the location to which the student belongs.
Back up to the case manager is the location substitute UM, or a People Manager (PM) from the relevant location.

The case manager ensures that the Fontys protocol is implemented and as well the possible additional actions below, as shown in Figure 1.

Figure 1
Possible additional actions to the Fontys 'Protocol on Student Death' and its implementer at Fontys ICT.
Action Implementation
Reporting to the Student Desk (SD); The SD can check with the Student Facilities Service whether death has been reported.
Setting up memorial site. Semester coach (SC)
Agree with the class to send a card or other notice of sympathy. SC
Having flowers delivered on the day (or before the day) of the funeral. Marketing & Communication (M&C)
At the in memoriam message, offer the opportunity to respond. After a few weeks, hand over the responses to the parents. SC
Allowing parents to come on site and visit. SC
Fontys protocol states that an obituary can be placed if the family's response to it is positive. However, a Fontys obituary is additional to that of the family. Therefore, the ads should be placed at the same time. In contact with the parents, it is nice to agree on this at once.
Parents support for deregistration (Studielink) and student grants/OV (DUO). The Student Facilities Service notifies DUO that the student concerned has died, but this does not stop the student grant/OV. If the parents apply the death to the municipality, this is passed on to DUO via the GBA (Municipal Personal Records Database), after which DUO will deregister the deceased student for the student grant/OV. Transmitting this to parents can help them deregister from DUO.

More info related to death, see the Fontys Protocol_death_student

Accounts

Fontys. The Fontys protocol on the death of a student includes the accounts of the following systems:

  • Progress
  • Content Manager
  • Email

Account management by Student Desk.
At Student Desk, a report is made on behalf of:

  • StudentFollow1).
    • The class name with the student should be removed
    • Remove parts
    • Remove SC and assessors
    • Verify that student is known to Student+; report to/action by PL Student+

Account management by II&A
Applying to II&A. Unlike regular changes carried out by each functional administrator, when a student dies, the following is picked up by II&A.

  • Active directory: delete account (Sharepoint profile page disappears).
  • StudentFollow2).
    • Delete account
  • Aura
    • Checking whether items are still on loan. Assess whether these are still requested back or written off. Record this so that reminder emails or letters are no longer sent.
    • Remove student from Aura
  • Feedpulse: block account and delete data; apply by II&A; action by Functional Control Canvas.
  • StudyCoach: block account and delete data; apply by II&A; action by Functional Control Canvas.
  • Portflow: block account and delete data; apply by II&A; action by Functional Control Canvas.
  • CanvasDbCore: delete history.

Accounts align with PLOU and/or coach
For the following systems, it must first be coordinated whether the account can be blocked, as this may involve group work. Coordinate with the PLOU.

  • Canvas: delete account.
  • GitLab: block account and delete data.
  • Webservers: block account and delete data.

Account details Student+.
When a student has been in contact with Student+, there may be notes and data on Student+'s Sharepoint environment. These should be deleted.

1) , 2)
Ensuring that students who are set to inactive are not visible in any reports