> For the complete documentation index, see [llms.txt](https://help.verkada.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.verkada.com/incident-response/~/revisions/7I3tEQ8Z5Fam4stqRJc6/getting-started/running-drills-with-incident-response/best-practices-for-running-reunification-exercises.md).
# Best Practices for Running Reunification Exercises
The *I Love U Guys* Foundation's **Standard Reunification Method - Reunification Exercise** ([SRM-REx](https://iloveuguys.org/Reunification-Exercise.html)) gives schools a proven way to train staff on student reunification. Schools can adapt the SRM-REx framework to run their own trainings with Verkada Incident Response. Using sample student and guardian cards, schools can give every staff member hands-on practice.
#### Key Outcomes
* **Run a proven exercise**: simulate an end-to-end reunification using your own Response Template, aligned with ILUG Foundation’s SRM-REx framework.
* **Train every role**: have staff carry out their reunification responsibilities hands-on using printed cards of sample students and guardians.
* **Measure performance**: after the exercise, review analytics to see exactly where your workflow holds up and where to improve.
***
## Before you begin
In order to use the *I Love U Guys* sample roster, an Incident Response site must have the following configured:
1. A Response Template that tracks [students as evacuees](https://help.verkada.com/incident-response/configuration/create-response-templates#people)
2. [Workplace Employees](https://help.verkada.com/incident-response/getting-started/get-started-with-incident-response#workplace-employees)
Ahead of time, Download and cut out the sample student & guardian data.
***
## Exercise setup
Dedicate a space to run the exercise and consider dividing the space for a student assembly area and a guardian check-in area to model a real reunification.
{% hint style="danger" icon="wifi" %}
Confirm that every participating staff member has a phone or computer with an internet connection to access the [Incident Response portal](https://help.verkada.com/incident-response/getting-started/incident-response-portal).
{% endhint %}
Ahead of the exercise, assign reunification roles to your staff: accountants, checkers, and reunifiers. Distribute student cards evenly between accountants, and distribute guardian cards between checkers.
***
## Running the exercise
To begin the reunification exercise, launch [a drill from Incident Response using the **sample roster**](https://help.verkada.com/incident-response/~/revisions/zAH7cnAUQ838oJGWPSGd/getting-started/running-drills-with-incident-response). If notifications are enabled, staff will receive notifications with magic links to the Incident Response portal. If notifications are disabled, staff can still login at [unite.my.verkada.com](https://unite.my.verkada.com).
### Key Roles
#### Accountants
Accountants are responsible for tracking their students in Incident Response. For each student, they must assign a status and location from the [People Status](https://help.verkada.com/incident-response/getting-started/incident-response-portal#people-status-page) page.
#### Checkers
Checkers are responsible for signing-in and verifying guardians. From the[ Sign in Guardians](https://help.verkada.com/incident-response/getting-started/incident-response-portal#sign-in-guardians-page) page, checkers will fill out a form for each guardian card.
#### Reunifiers
Reunifiers are responsible for pairing eligible students and guardians, one at a time. Using [Reunify Students + Guardians](https://help.verkada.com/incident-response/getting-started/incident-response-portal#reunify-students-and-guardians) page, reunifiers will:
{% stepper %}
{% step %}
**Claim a student and guardian pair**
{% endstep %}
{% step %}
**Retrieve the corresponding student & guardian cards**
{% endstep %}
{% step %}
**Mark the pair as reunified**
{% endstep %}
{% endstepper %}
***
## After the exercise
When the exercise has finished, and admin should [end the Response from Command](https://app.gitbook.com/o/bkNVNKmzsORLGDsma54Q/sites/site_gHpgU/s/n49pz7ZddUdVxNdz2EFE/~/edit/~/changes/9/getting-started/running-drills-with-incident-response#end-a-drill). This will prevent staff from making changes to the Response.
Admins can review [analytics from the exercise](https://help.verkada.com/incident-response/~/revisions/Z6YVAeBAAl5UVz1iUSfx/analytics/review-responses-from-command) to assess:
* **Overall performance**: incident duration, updates over time, percentage of students reunified, median guardian wait time, and more.
* **Individual performance**: students tracked, guardians signed-in, and reunifications completed by staff member.
For any students or guardians who weren't reunified, use the History tab to see which staff members interacted with their cards and identify any incorrect updates.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://help.verkada.com/incident-response/~/revisions/7I3tEQ8Z5Fam4stqRJc6/getting-started/running-drills-with-incident-response/best-practices-for-running-reunification-exercises.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.