APS 10.13 requires that youth activities led by a non-UW third party or Registered Student Organization (RSO) that will take place on UW property be registered in the Youth Program Registration System (YPRS) by the venue or facility operator who reserves the room(s) for and enters into a facility use agreement with the third party/RSO.
Additionally, facility or venue operators are required to obtain an agreement in writing from the third party/RSO they are hosting that the third party/RSO will meet or exceed the requirements of the APS 10.13. This written agreement should be included in the facility use agreement or other contracts/formal agreements with the third party/RSO.
- View example language that can be incorporated into agreements [pdf].
- For more information view the Third Party FAQs.
What is a third party led youth activity?
- Any activity, event or program in which:
- youth are a primary audience,
- it is operated or sponsored by a third party (non-UW organization, business or group), and
- it takes place in University facilities or property
- A third party includes:
- Any non-UW entity or student-run organization (RSO) entering into a facility use agreement with a University department or unit.
- Please note: UW departments that sponsor a youth activity and contract or partner with a non-UW entity should review this guidance.
- If a youth activity involves contractors, consultants, vendors, or other non-UW entities that provide a service, on or off-campus, under the oversight or sponsorship of a UW department, it must be registered as a UW led youth activity.
Requirements for third parties/RSO’s operating youth activities on University property
Third party and RSO led youth activities that take place on University property must meet or exceed APS 10.13 requirements. Agreement in writing to meet or exceed the requirements should be included as part of the facility use agreement or other contract/formal agreement with the UW facility host. If a third party or RSO is unsure whether this has been included in their facility use agreement, they should contact the hosting department.
APS 10.13 includes requirements for:
- Registration [by the facility host] in the UW Youth Program Registration System.
- Background screenings for personnel with unsupervised access to, or responsibility for, youth.
- Personnel training on safely interacting with youth and reporting suspected child abuse and neglect.
- Personnel conduct expectations.
- Reporting violations of conduct expectations and suspected child abuse and neglect.
- Maintaining a safe environment.
- Emergency and safety planning and response.
- Privacy practices for handling youth data.
Registered Student Organizations (RSO’s)
Student-led organizations are considered third parties and must have their own policies that meet or exceed the requirements of Administrative Policy 10.13 Requirements for University and Third Party Led Youth Programs when they hold an activity involving youth on University property (see above). The Office of the Youth Protection Coordinator (OYPC) does not track these requirements for third parties. RSO’s can request help from someone in their department or their SAO advisor to determine how to get background checks run, and everyone is welcome to access the training and conduct code resources that OYPC has developed.
The HUB has an Interactions with Minors (Youth) webpage in their RSO Policy Guide that outlines additional requirements for RSO’s on UW Seattle campus. The facility host is responsible for registering the RSO activity in the YPRS.
OYPC created the form Special Events Involving Youth: Safety Planning Checklist and Risk Mitigation Plan to assist RSO’s with identifying and mitigating potential risks associated with youth engagement. RSO’s who are planning an on-campus event where youth are a primary audience may email the completed form to OYPC at uwminors@uw.edu to receive feedback and recommendations for risk mitigation.