Skip to content

Guardians and Emergency Contacts

Applies to: roles with Students.Create (capture at registration) and Students.Edit / Students.View (view on the edit page). Last reviewed: 2026-11-18.

This page explains what DriveFlow stores about a student's parent or guardian and emergency contact, where it is captured, and the current gaps.

Guardian details cannot be changed on the web

Read the Limitations and notes section before relying on this feature: at present guardian details can be captured once at registration and viewed, but not changed through the web application.


1. What is stored

Guardian

Field Notes
Full name
Relationship Free text, for example Mother, Father, Brother
Mobile number
Alternative number
Email
Occupation
Physical address
Use as emergency contact Yes / No

Emergency contact

Field Notes
Full name
Relationship
Phone number

Medical information (no screen)

The database also has a medical information record per student (wears glasses, has a disability and details, has a medical condition and details, allergies). There is no screen for it anywhere in the web application. It can only be read or written through the API.


2. When a guardian is required

Never, as far as the system is concerned. The Guardian panel on the registration page is marked Optional, and its only guidance is the note "Complete this section if the student is under 18 or if an emergency contact is required."

  • The system does not check the student's age against the guardian fields.
  • None of the guardian fields is compulsory, and none is validated (the email and phone are not format-checked).
  • The registration age rule means a student must be older than 16 in any case; see Student registration.

Tip

If your school requires a guardian for students under 18, that has to be a manual office rule.


3. Capturing a guardian at registration

Who: users with Students.Create.

  1. On the Register Student page, click the Guardian Information panel heading to open it (it is closed by default).
  2. Fill in what you have:
    • Guardian Full Name
    • Relationship (placeholder "Mother, Father, Brother...")
    • Mobile Number
    • Alternative Number
    • Email
    • Occupation
    • Physical Address
  3. Tick Use as Emergency Contact if this person should also be the student's emergency contact.
  4. Complete the rest of the page and click Register Student.

Screenshot to be added

Screen: Register Student, Guardian Information panel. Should show: the panel opened, with the fields filled in and "Use as Emergency Contact" ticked.

What is saved:

  • One guardian record with all the fields above.
  • If Use as Emergency Contact was ticked, one emergency contact record as well, copied from the guardian's full name, relationship and mobile number. (The alternative number, email, occupation and address are not copied.)

The emergency contact is a copy made at that moment. It is not linked to the guardian afterwards.


4. Viewing a guardian

The guardian is not shown on the student profile. To see it:

  1. Open the student's actions menu and click Edit (needs Students.Edit; not available for Licensed students, and the save is refused for Inactive students).
  2. Scroll to Guardian Information. The first guardian saved for the student is shown.
  3. Click Cancel to leave without saving.

The emergency contact record cannot be viewed anywhere on the web: no page displays it.


5. Changing a guardian or emergency contact

Not currently possible on the web.

The Update Student page shows the Guardian Information panel and lets you type in it, and its description says "Update the student's personal, contact and guardian information." However, when you click Update Student, the guardian fields are not saved. You still see "Student updated successfully." because the other fields were saved. Reopen Edit and the old guardian details are back.

There is also no way on the web to:

  • add a second guardian,
  • remove a guardian,
  • add, change or remove an emergency contact after registration,
  • record medical information.

What the API offers (for developers)

API endpoints for guardians, emergency contacts and medical information

The server has working endpoints for all of this; no screen calls them yet. All are under api/Students/{id}/ and need Students.Edit to change and Students.View to read.

Purpose Endpoints
Guardians GET guardians, POST guardians, PUT guardians/{guardianId}, DELETE guardians/{guardianId}
Emergency contacts GET emergency-contacts, POST emergency-contacts, PUT emergency-contacts/{contactId}, DELETE emergency-contacts/{contactId}
Medical information GET medical-info, POST medical-info, PUT medical-info/{medicalInfoId}, DELETE medical-info/{medicalInfoId}

Notes on these endpoints:

  • The guardian add and update endpoints only accept full name, relationship, phone number and email. Alternative number, occupation, address and the emergency-contact flag can only be set at registration.
  • Deleting is a soft delete (the record is hidden, not erased).
  • Messages returned: "Guardian added successfully.", "Emergency contact added successfully.", "Medical information added successfully.", "Guardian not found.", "Student not found."
  • These commands have no field validation.

6. Limitations and notes

  • Guardian edits on the Update Student page are discarded (StudentEdit.razor shows the panel; UpdateStudentCommand has no guardian fields).
  • A guardian record is created for every student, even when the panel is left empty. The registration form always sends a guardian object, so students registered without guardian details have a blank guardian record. If Use as Emergency Contact is ticked on an empty panel, a blank emergency contact is created too.
  • Guardian and emergency contact are not shown on the profile. The guardian is only visible through Edit; the emergency contact is not visible anywhere.
  • Only the first guardian is ever shown, even if more were added through the API.
  • Guardians do not receive notifications. No notification, invoice email or portal access goes to the guardian's email or phone; all messages go to the student. (See Notification settings.)
  • Guardians cannot sign in. There is no guardian or parent account type.
  • Medical information has no user interface (StudentMedicalInfoFeatures.cs, StudentsController.cs).
  • No under-18 rule. Nothing forces or prompts for a guardian based on age.