Skip to Login Skip to Content Skip to Secondary Navigation

Jennifer Rosko
Aug 6, 2014

Registered Campus Organization (RCO) Important Updates :: Please Read

Aug 6, 2014 by Jennifer Rosko

After a comprehensive review of current policies and practices of Registered Campus Organization (RCO) registration requirements, event approval process, alcohol requests, space reservations, funding requests and resource allocation, new updates to policies and practices will be implemented starting September 2014.

Please take a moment to review the updates below. If you have any questions, please contact Student Life at

Any volunteer organization whose membership is comprised predominately of UCSF students, faculty, and/or staff may apply for registration. During the registration process, each RCO will be given a classification tied to its organization administrators and membership roster.

  • Interprofessional Student RCO – organization administrators who pay student services fees from 3 or more schools/programs
  • School-specific Student RCO – organization administrators who pay student services fees from 1 or 2 schools/program
  • Staff RCO – organization administrators who do not pay student services fees, such as faculty, staff, postdocs, trainees, residents

Please review the RCO classification chart to view the various benefits of registering as s RCO.

Starting September 2014, registration will require:

  1. Organization name & acronym ** Name may not begin with UCSF
  2. Description & purpose of RCO ** Similar RCOs will be asked to merged
  3. Five organization administrators
  4. Organization portal profile & cover photo
  5. Completing an online orientation ** By all five organization administrators

Registration is required annually. Registration will be open twice a year: September & January. Please review all questions required for registration prior to renewing your registration or requesting to apply for a new organization. An email will be sent out to all RCOs in September indicating that registration for the 2014-15 academic year is open.

Please note that organizations will be asked to merge with similar organizations that have overlapping missions and purposes. Additionally, starting in September 2015, registration renewals for organizations will depend on the RCO’s activity level throughout the previous academic year. Any RCO that does not hold at least one organizational meeting or event per quarter through the previous academic year will be required to provide an explanation when they renew their registration.

All RCO events on- or off-campus must be approved by Student Life. Event approval is obtained by submitting an event request in OrgSync. Depending on the nature of your event, your RCO may be required to secure liability insurance. Please remember that RCOs should not sign any contracts for off-campus events without consulting with Student Life.   

Student RCOs may reserve tables and chairs through Student Life. Starting in September 2014, there will be a 2-table and 4-chair limit per event request. If a RCO needs more than the allotted amount, a fee may be charged.  

Educational Technology Services (ETS) has implemented a “no-show” policy. RCOs may be charged if they reserve a room and do not utilize the space. Cancellation must be provided 48 hours in advance.

Funding guidelines are still under review. Please be on the look out for a future email detailing the implementation of new funding guidelines.

In July, OrgSync launched a new user interface. It’s more modern, intuitive, and easier to use than ever before. They shifted components around to be better organized, simplified navigation, and added functionality to enhance the platform. We recommend attending one of Student Life’s OrgSync trainings or visiting the OrgSync help section online. The iPhone app is available for download in the app store.

If you have any questions regarding RCOs, the registration process, or OrgSync, please call, email or stop by the Student Life office.



Timothy H Schmidt

Thank you for this post! It is quite helpful.