The Senior Policy Council and the President approved several University Policies.
Author: Quiles, Anida
Division of Athletics Business Meals Policy
| Title: | Division of Athletics Business Meals Policy |
|---|---|
| Policy Owner: | Vice President for Finance and Chief Financial Officer |
| Applies to: | University Workforce Members, Students, Prospective Student-Athletes and External Guests |
| Campus Applicability: | All UConn Campuses, except UConn Health |
| Approval Date: | October 5, 2026 |
| Effective Date: | October 26, 2026 |
| For More Information, Contact: | Associate Vice President for Financial Operations and Controller |
| Contact Information: | travel@uconn.edu |
| Official Website: | https://travel.uconn.edu |
BACKGROUND
The University of Connecticut (University) recognizes and supports the need for the Division of Athletics to provide Business Meals in connection with athletic competition, practice, Team Travel, local team events, and the Recruitment of Prospective Student-Athletes and other purposes in support of Student-Athletes and consistent with the University’s mission. Athletics Business Meals may involve current Student-Athletes, Prospective Student-Athletes and their families, coaches, assistant coaches, support staff, and External Guests.
PURPOSE
To establish rules that balance the Division of Athletics’ Business Meal needs for Team Travel, competition, practice, and Recruitment and other National Collegiate Athletic Association (NCAA) compliant activities with the responsible stewardship of public resources, and to support adherence to NCAA regulations regarding Team Travel and Recruitment, which promote fair competition and Student-Athlete welfare.
Because Athletics Business Meals may involve University funds and may also be subject to National Collegiate Athletic Association (NCAA) rules, this policy establishes Athletics-specific requirements for Business Meal purchases and reimbursements while maintaining appropriate stewardship of University resources.
This policy supplements the University Business Meals Policy and the Division of Athletics Travel and Entertainment Policy for Team Travel and Recruitment Business Meals.
APPLIES TO
This policy applies to University Workforce Members, University Students, Prospective Student-Athletes, and External Guests representing or participating with the University’s Division of Athletics as it relates to team Business Meals, recruiting Business Meals, and Business Meals associated with Team Travel, competition, practice, and local Athletics events and other NCAA compliant activities.
DEFINITIONS
Business Meals: Any food or beverage purchased for an approved University Business Purpose. This includes but not limited to entrees, light refreshments, snacks, catered food, Dining Services orders, and groceries or similar supplies purchased for preparation or service of food and beverages for authorized Athletics Team Travel, competition, practice, or recruitment activities.
Business Purpose: A Business Purpose exists when the meeting or activity is essential to conducting official University business and must directly support the University’s mission/objectives and be indispensable for the completion of a specific task or duty.
External Guest: Individuals external to the University who include but are not limited to donors, recruits and external or visiting students.
Prospective Student-Athlete: An individual being recruited to participate in University Athletics, consistent with NCAA rules, including family members or other guests whose participation in a recruiting Business Meal is permitted under NCAA and University requirements.
Recruitment: On-campus or off-campus recruitment of a prospective student-athlete and/or the prospective student-athlete’s family or permitted guests.
Student-Athlete: A current University student participating as a member of an intercollegiate Athletics team.
Team Travel: An official Athletics competition, practice, mandatory team training, team meeting integral to competition or practice, team travel, local team event, or similar Athletics activity related to team operations, including excursions and team building.
POLICY STATEMENT
The University permits the purchase or reimbursement of Athletics Business Meals when such expenses are reasonable, necessary, appropriate, directly related to official Athletics business, , and compliant with NCAA rules. University funds may not be used for Business Meals at social functions, routine staff meetings, or events held primarily for convenience rather than a valid Athletics business purpose.
All Athletics Business Meals, whether incurred during Team Travel, at a local Athletics event, or at the primary work location, must meet the standards in this policy and associated procedures to qualify for payment or reimbursement.
The Division of Athletics will adhere to the University’s Business Meals Policy, Travel and Entertainment Policy, and Division of Athletics Travel and Entertainment Policy, except where this policy outlines specific provisions for Athletics Team Travel and Recruitment Business Meals.
This policy complies with NCAA rules and regulations and adheres to the requirements of the Division of Athletics Title IX policies.
Individual meal per diem reimbursements for travelers are governed by the University Travel and Entertainment Policy and the Division of Athletics Travel and Entertainment Policy. Team Travel Business Meals, and Recruitment Business Meals described in this policy are governed by this policy.
University Workforce Members and Students may be subject to additional or differing Business Meal reimbursement requirements under a collective bargaining agreement (CBA) or provisions in their employment agreement. In the event of a conflict between this policy and an applicable CBA or employment agreement, the CBA or employment agreement shall control.
PRE-APPROVAL
The following Athletics Business Meals do not require pre-approval:
- Business Meals associated with Team Travel.
- Business Meals associated with Recruitment where a Prospective Student-Athlete and/or the Prospective Student-Athlete’s family or permitted guests are present
- Employee-only Business Meals that occur immediately before or immediately after a competition or approved team activity and are time-sensitive and operationally necessary.
Any Business Meal type not mentioned above is under the purview of the University Business Meals Policy
EXPENSE LIMITS
The cost of a Business Meal for each person, including beverages, taxes, delivery or service charges, and gratuities may exceed two (2) times the applicable GSA Meal Rate for the location for Business Meals relating to Recruitment or Team Travel that is in compliance with NCAA rules.
TEAM TRAVEL STAFF BUSINESS MEALS
Team Travel staff may receive more than three Business Meals per day, not inclusive of per diem, if additional Business Meals are provided to Student-Athletes, such as snacks or pre-game and post-game Business Meals, in accordance with the Division of Athletics Travel and Entertainment Policy.
EXCEPTIONS TO POLICY
Requests for exceptions to this policy must demonstrate business necessity, comply with NCAA rules, and be approved by the Director of Athletics.
PROCEDURES/FORMS
REFERENCES
NCAA rules and regulations can be obtained through the Athletic Compliance Office.
- University Business Meals Policy
- University Travel and Entertainment Policy
- Division of Athletics Travel and Entertainment Policy
- Alcoholic Beverage Sales and Service Policy
POLICY HISTORY
Policy created: 10/05/2026 (Approved by the University Senior Policy Council and President)
Revisions:
Summer 2026 Policy Update
The Senior Policy Council and the President approved the following University Policies:
Payment Card Industry Data Security Standards (PCI DSS) Compliance, Policy on
| Title: | Payment Card Industry Data Security Standards (PCI DSS) Compliance, Policy on |
|---|---|
| Policy Owner: | Office of the Bursar Cash Operations, UConn Information Security Office |
| Applies to: | Workforce Members |
| Campus Applicability: | All UConn Campuses, except UConn Health |
| Approval Date: | June 17, 2026 |
| Effective Date: | July 1, 2026 |
| For More Information, Contact: | Director of Cash Management & University Bursar, Chief Information Security Officer |
| Contact Information: | cashoperations@uconn.edu |
| Official Website: | https://bursar.uconn.edu/departments/cash-operations/ |
PURPOSE
To provide requirements for safeguarding Customers’ payment card data and cardholder information. Failure to protect this information may result in financial loss for Customers, suspension of credit card processing privileges, fines, and damage to the reputation of the University.
APPLIES TO
Workforce members involved with payment card handling which includes but is not limited to collection, processing, transmission, or storage of payment card data in any form on behalf of the University.
DEFINITIONS
Attestation of Compliance (AOC): A formal document certifying an organization’s compliance with Payment Card Industry Data Security Standards (PCI DSS).
Cardholder Data (CHD): Elements of payment card information that must be protected, including the primary account number (PAN), cardholder name, expiration date, and security code.
Customer: Any individual or entity conducting a financial transaction with the University that involves the collection, processing, transmission, or storage of their payment card data.
Department: A University unit approved by the PCI Team to accept payment cards without maintaining a designated unique merchant identification number.
Merchant: A department or unit approved by the PCI Team in accordance with University policy to be assigned a designated unique merchant identification number for payment card acceptance.
Payment Card Industry Data Security Standards (PCI DSS): Technical and operational requirements set by the Payment Card Industry Security Standards Council to protect cardholder data. The standards globally govern all merchants and organizations that store, process, or transmit this data. Compliance with the PCI set of standards is mandatory and enforced by the major payment card brands who established the Council.
Payment Card Industry Security Standards Council (PCI SSC): A global forum that brings together industry stakeholders to develop and drive adoption of data security standards and resources for safe payments worldwide.
PCI Responsibility Matrix: A framework that clearly defines and allocates specific PCI DSS tasks and requirements among different parties, such as a merchant and its service providers. It maps each PCI DSS requirement to the responsible party, which can be the merchant, a service provider, or a shared responsibility.
PCI Team: Group composed of representatives from Office of the Bursar Cash Operations and the UConn Information Security Office.
PCI Violation: Any action, inaction, or condition that results in non-compliance with PCI DSS requirements.
Point of Interaction (POI) Devices: Any hardware used to capture payment card data (e.g., card readers, PIN pads, kiosks)
Point-to-Point-Encryption (P2PE): A PCI-listed solution that cryptographically protects cardholder account data from the point where a merchant accepts the payment card to the secure point of decryption.
Point-to-Point Encryption Self-Assessment Questionnaire (P2PE SAQ): Reporting tool used to document self-assessment results from an entity’s PCI DSS assessment specific to PCI-validated Point-to-Point Encryption (P2PE) solutions. The P2PE self-assessment document is maintained by the PCI Security Standards Counsel.
Self-Assessment Question (SAQ): Validation tool to assist merchants report the results of their self-assessed PCI DSS compliance.
Third Party Service Providers: Business entities that are not a payment brand, directly involved in the processing, storage, or transmission of cardholder data and/or sensitive authentication data on behalf of another entity. This also includes companies that provide services that control or could impact the security of cardholder data.
POLICY STATEMENT
The University of Connecticut is committed to protecting Cardholder Data (CHD) and maintaining compliance with the Payment Card Industry Data Security Standards (PCI DSS). All payment card activities conducted on behalf of the University must be performed in a manner that minimizes risk to cardholders and the institution, limits the handling of Cardholder Data, and ensures consistent compliance with PCI DSS requirements.
Storing of CHD
University workforce members must never record or store Cardholder Data in any physical or electronic format, including paper or electronic documents.
Appropriate Use of Payment Channels
Electronic Payments
Customers must be directed to complete electronic payments online using their own device and must not be directed to use a University device to enter CHD. CHD must not be entered by staff on University computers or workstations.
In-Person Payments
The cardholder must always maintain their physical card when making payment in-person. University workforce members must never take possession of the Customer’s physical card.
Mail Order Payments
Usage of mail order forms is prohibited unless otherwise approved by the PCI Team. If usage of mail order forms is approved, all CHD must be physically destroyed in a manner that renders the data un-recoverable immediately after processing such as cross-cut shredding. The remaining portion of the mail order form must be retained in compliance with University retention requirements.
Telephone Payments
Accepting card payment over the phone is prohibited unless otherwise approved by the PCI Team. If acceptance of phone payments is approved, they must be taken over a physical phone only and cannot be accepted via Voice Over IP (VOIP) software.
Receiving and processing CHD via email is prohibited. If CHD is received via email, the CHD must be deleted immediately from all Outlook folders including the deleted folder and the card payment must not be processed.
Point of Interaction (POI) Devices
All in-person, mail order, and telephone payment card transactions must be processed exclusively through PCI-validated Point-to-Point Encryption (P2PE) Point of Interaction Devices. POI Devices must be listed on the PCI Security Standards Council (PCI SSC) list of validated P2PE solutions.
Exceptions must be approved by the PCI Team and will only be granted for Merchants who have a business need to use a vendor that does not offer P2PE POI Devices.
Merchants and Departments, using POI Devices must meet the requirements outlined in the current Point-to-Point Encryption Self-Assessment Questionnaire (P2PE SAQ), including but not limited to:
- restricting physical access;
- provide training for awareness of POI Device tampering;
- following POI Device log procedures; and
- completing POI Device inspections, with frequency of inspection determined by a targeted risk assessment of the device environment.
Annual Self-Assessment Questionnaire (SAQ) Submission
All Merchants must submit an SAQ annually. The SAQ type must align with the Merchant’s payment processing method(s) and business environment. The PCI Team will coordinate with Merchants on the completion and submission of the annual SAQ.
Third Party Service Providers
Merchants and Departments may have a need to use Third Party Service Providers to provide functionality for processes such as event registration, non-credit programming, ticketing, and other services that cannot be accommodated through the University’s centralized e-commerce platform.
Using a Third-Party Service Provider does not transfer PCI DSS responsibility from the University. All Third-Party Service Providers must:
- be contracted through the University’s procurement process;
- be approved by the PCI Team;
- demonstrate PCI DSS compliance through vetting and monitoring;
- provide a PCI Responsibility Matrix and a current Attestation of Compliance (AOC).
Merchants and Departments must request the AOC annually as part of ongoing service provider management. The AOC must be submitted to the PCI Team for the annual SAQ submission.
Annual Training
Workforce members involved with the acceptance and processing of CHD must complete annual training on PCI DSS compliance and information security awareness in accordance with University policy. The PCI Team is responsible for providing training to required workforce members.
Annual Policy & Procedure Review
Merchants and Departments must review all payment card processing policies and procedures on an annual basis.
Incident Response Reporting
Any actual or suspected unauthorized access or disclosure of Cardholder Data must be reported immediately to the PCI Team by emailing security@uconn.edu and cashoperations@uconn.edu. The UConn Information Security Office shall assess all reported events and when appropriate activate the University Incident Response Plan.
ENFORCEMENT
Failure to meet the requirements outlined in this policy may result in suspension of the physical and, if appropriate, electronic payment capability for the responsible Department(s) or Merchant(s). In the event of a PCI Violation, the payment card brands may assess penalties to the University’s merchant services bank, which may be passed on to the University. The responsible Department or Merchant will be financially accountable for any such penalties assessed and passed on to the University.
Violations of this policy and any related procedures may result in appropriate disciplinary measures in accordance with University By-Laws, General Rules of Conduct for All University Employees, applicable collective bargaining agreements, and the University of Connecticut Student Code.
PROCEDURES/FORMS
POI Device Inspection Procedures
REFERENCES
Data Classification Policy
Incident Response Plan
Opening a Merchant Account for Credit Card Acceptance
PCI SSC Validated P2PE Solution Listing
P2PE SAQ
Records Management Policy
Security Awareness Training Policy
POLICY HISTORY
Policy created: June 17, 2026 (Approved by the University Senior Policy Council and President)
Software Asset Capitalization and Tracking Policy
| Title: | Software Asset Capitalization and Tracking Policy |
|---|---|
| Policy Owner: | Accounting Office, Controller’s Division |
| Applies to: | University Workforce Members |
| Campus Applicability: | All UConn Campuses, except UConn Health |
| Approval Date: | June 17, 2026 |
| Effective Date: | June 30, 2026 |
| For More Information, Contact: | Associate Controller and Director of Accounting |
| Contact Information: | accountingoffice@uconn.edu |
| Official Website: | https://accounting.controller.uconn.edu |
BACKGROUND
The State Property Control Manual states that agencies must report software inventory annually to the Office of the State Comptroller on the Annual Inventory Report of all Real and Personal Property (CO-59) form.
PURPOSE
To ensure accurate records of Capitalized Software assets, which are essential for compliance with the State of Connecticut Property Control Manual and for proper valuation in the University’s financial statements. To support this, a Software Librarian will maintain a software asset library for tracking Capitalized Software and will ensure an annual inventory is completed prior to the end of each fiscal year in accordance with Section 4-36 of the Connecticut General Statutes.
APPLIES TO
University workforce members on all campuses except UConn Health
DEFINITIONS
Capitalized Software includes any of the following:
- Software with initial purchases, upgrades, or renewals of software application programs or licenses with a cost of $5,000 or more and a useful life of three or more years. These assets are categorized as intangible assets.
- Software subscription contracts greater than 12 months requiring total payments over the contract term of $100,000 or more in exchange for the right to use a vendor’s information technology software. Such assets are categorized as right-to-use assets and are tracked and accounted for under GASB 96, Subscription-Based Information Technology Arrangements (SBITAs).
- Software projects where the total budget is $1 million or more and require substantial internal labor to develop, test and bring a software application into service. Such assets are tracked and accounted under GASB 51, Accounting and Financial Reporting for Intangible Assets.
Software Librarian: Individual(s) within the Accounting Office assigned to maintain a software asset library which allows for the annual inventory of Capitalized Software assets, provides a means for concise reporting on the status of such software assets, and is the point of contact for software audits and for submitting updated copies of the policy for review to the State Comptroller if the policy is modified.
Software Tracking System(s): One or more systems where Capitalized Software assets are tracked. Such systems serve as the software asset library.
POLICY STATEMENT
Capitalized Software must be tracked in the Software Tracking System(s) to produce a software asset library, and an inventory must be completed annually prior to each fiscal year end, June 30th. Workforce Members in university departments are responsible for assisting in this process through the proper coding of purchase orders and through tracking internal labor on software projects, when applicable as outlined within the project scope.
The Software Librarian is responsible for maintaining the software asset library, and for recording additions, disposals and retirements. Each software record within the Software Tracking System(s) shall contain (when possible/applicable):
- Assigned Identification Number
- Description – software name or functional application
- Manufacturer/Vendor
- Acquisition Type – purchased, leased or donated
- Purchase Order Number or Donation source
- License Term
- Number of licenses
- License identification number
- Cost and/or payment amounts
- Disposal method
- Disposal date
The Software Librarian is responsible for reporting software inventory annually to the Office of the State Comptroller on the Annual Inventory Report of all Real and Personal Property (CO-59) form and for reporting any known losses on form CO-853, Adjustments to State Owned Assets as per the State Property Control Manual.
ENFORCEMENT
Violations of this policy and any related procedures may result in appropriate disciplinary measures in accordance with University By-Laws, General Rules of Conduct for All University Employees, and applicable collective bargaining agreements, and the University of Connecticut Student Code.
PROCEDURES/FORMS
UConn Knowledge Base for Capital Software Object Codes (under Equipment Category)
REFERENCES
State of Connecticut Office of the State Comptroller, Property Control Manual
POLICY HISTORY
Created on: June 17, 2026 (Approved by the University Senior Policy Council and President)
May Policy Update
The Senior Policy Council and the President approved several University Policies.
Hazardous Materials Donations Policy
| Title: | Hazardous Materials Donations Policy |
|---|---|
| Policy Owner: | Environmental Health and Safety |
| Applies to: | University Workforce Members and Students |
| Campus Applicability: | All UConn Campuses, except for UConn Health |
| Approval Date: | April 30, 2026 |
| Effective Date: | June 1, 2026 |
| For More Information, Contact: | Environmental Health and Safety |
| Contact Information: | (860) 486-3613/ ehs@uconn.edu |
| Official Website: | Environmental Health and Safety |
PURPOSE
To ensure Hazardous Materials Donations (i.e., biological, chemical, radioactive, or other regulated materials) are evaluated and authorized by Environmental Health and Safety (EHS) prior to acceptance by workforce members to protect workers, ensure compliance with federal and state regulations and University policies, conform to building and fire codes, and minimize disposal costs to the University.
APPLIES TO
This policy applies to workforce members who accept Hazardous Material Donations at all campuses, except UConn Health.
DEFINITIONS
Hazardous Material Donation: The voluntary, unconditional transfer of hazardous materials (i.e., biological, chemical, radiological, or other regulated materials) from any external organization to a college, department, school, or workforce member at the University of Connecticut.
POLICY STATEMENT
Colleges, departments, schools, or workforce members must receive written approval from Environmental Health and Safety prior to accepting Hazardous Material Donations.
If Hazardous Material Donations do not receive written authorization from EHS prior to delivery or receipt, the costs associated with shipping unsafe, non-compliant, or nonessential hazardous materials back to the external organization will be covered by the college, department, or school who authorized the shipment.
ENFORCEMENT
Violations of this policy and any related procedures may result in appropriate disciplinary measures in accordance with University By-Laws, General Rules of Conduct for All University Employees, applicable collective bargaining agreements, and the University of Connecticut Student Code.
PROCEDURES/FORMS
Workforce members must complete the Hazardous Materials Donation Form on the EHS Website prior to accepting any donation.
The appropriate EHS team(s) will assess Hazard Material Donations prior to approval. The assessment may include, but is not limited to, reviewing the following:
- Material type and characteristics
- number of containers or items
- quantity of material
- physical form(s) (e.g., solid, liquid, gas)
- condition of materials (e.g., age, opened vs unopened, etc.)
- procedures in place to use the materials
- storage location(s)
- control measures in place (e.g., fume hoods, local ventilation, etc.)
- any required permits or licensing
- costs associated with disposal.
EHS may also contact UConn’s Fire Marshal, Building Inspector & Security Technology office, when appropriate, to ensure compliance with applicable building and fire codes.
Following the assessment, EHS will either authorize the Hazardous Material Donation, request more information, or deny the donation in writing. If the donation is authorized and involves laboratory chemicals, the workforce member must contact EHS to barcode the chemicals upon arrival to comply with the Laboratory Chemical Inventory Program.
REFERENCES
Environmental Health and Safety Website
Hazardous Materials Donation Form
Laboratory Chemical Inventory Program
POLICY HISTORY
Policy created: April 30, 2026 (Approved by the University Senior Policy Council and President)
Revisions:
Notice of Privacy Practices
March Policy Update
The Senior Policy Council and the President approved several University Policies.
Registered and Trustee Student Organizations, Policy on
| Title: | Policy on Registered and Trustee Student Organizations |
|---|---|
| Policy Owner: | Division of Student Life & Enrollment |
| Applies to: | All University Workforce Members, Students, Guests and other Third Parties that engage with student organizations |
| Campus Applicability: | All UConn Campuses |
| Approval Date: | March 4, 2026 |
| Effective Date: | March 9, 2026 |
| For More Information, Contact: | Associate Vice President for Student Life |
| Contact Information: | solid@uconn.edu or studentactivities@uconn.edu |
| Official Website: | https://studentlife.uconn.edu/ |
BACKGROUND
The University of Connecticut recognizes the longstanding role of student organizations in fostering student engagement, leadership development, and community building across all campuses. Student organizations operate in a variety of forms, funding structures, and engage regularly with University resources, employees, and third parties.
This policy formalizes the University’s definitions, oversight, and relationship with Registered Student Organizations and Trustee Student Organizations.
PURPOSE
To establish a clear and consistent framework as it relates to the University’s working relationship with student organizations across its campuses.
APPLIES TO
All students, workforce members, and third parties that engage with student organizations.
DEFINITIONS
Registered Student Organization (RSO): A student-run entity voluntarily formed by University of Connecticut students, with a common interest, for a lawful purpose, and registered with their respective campus-based Student Activities office.
Trustee Student Organization (TSO): A Registered Student Organization formally recognized by the University’s Board of Trustees and separately funded through student-fees in accordance with Connecticut General Statutes. TSOs are student-governed and student-managed with operational and editorial autonomy (where applicable).
Advisor: A full-time University employee, including faculty and staff, or a graduate assistant where permitted, who is officially designated through the student organization registration process or assigned as part of their University role to provide guidance and support to a RSO or TSO.
The following individuals are not eligible to serve as an Advisor for UConn Campuses:
- Part-time employees
- Special payroll employees
- Student employees (except approved graduate students holding an assistantship)
- Volunteers, alumni, contractors, or external affiliates
Only external affiliates may serve as Advisors for RSO’s at UConn Health as may be permitted by UConn Health’s specific policies or processes.
POLICY STATEMENT
Formation and Registration
The University recognizes the right of students to form voluntary organizations for any lawful purpose. Student organizations that wish to receive access to University resources and services must register with their campus-based Student Activities office. To register, a student organization must meet all minimum requirements established by the University’s Blueprints manual and, when applicable, their campus-based Student Activities office.
RSOs shall be designated into a Tier-system in accordance with University guidance and oversight from the Division of Student Life & Enrollment. TSOs shall be established in accordance with the Student Service and Activity Fee Advisory Committee (SASFAC) process.
University Oversight and Organizational Autonomy
RSOs at the University are independent entities. The University assumes no responsibility for an RSO’s decisions, operations, contracts, events, or activities, nor does it provide insurance coverage or liability protection. The actions, viewpoints, publications, invited speakers, or initiatives of RSOs are solely the responsibility of the organization and their members.
The University’s role is not to approve or disapprove of such views, but rather to uphold its educational obligation to support free expression and open discussion consistent with the constitutional rights of students and the regulations of the University.
The University does not regulate RSO’s use of independent and non-university funds raised or collected. RSOs may independently enter into contracts or agreements with external parties using these independent funds. The University does not review, approve, or assume responsibility for such agreements unless explicitly stated in University policy otherwise.
A TSO receives financial oversight and administrative support from the University. However, a TSO retains control over their internal governance, operations, and student-led initiatives, except where University intervention is required to ensure compliance with law or policy.
Advisors serve in a supportive role while TSOs and RSOs retain full authority over their organization’s actions and decisions. Advisors do not bear responsibility for the actions or conduct of organization members when fulfilling their role appropriately and in good faith.
All students remain subject to the Student Code, and thus, a TSO or RSO may be referred to the University’s Student Organization Conduct process when their activities violate University policies.
ENFORCEMENT
Violations of this policy and any related procedures may result in appropriate disciplinary measures in accordance with University By-Laws, General Rules of Conduct for All University Employees, applicable collective bargaining agreements, and the University of Connecticut Student Code. If violated, individuals and/or Organizations may be personally liable.
PROCEDURES/FORMS
Blueprints Manual
Trustee Student Organization Manual
REFERENCES
Connecticut General Statute § 4-52 – 57a.
Conn. Gen. Stat. § 4-165
Conn. Gen. Stat. § 5-141d
The Student Code
Student Service and Activity Fee Advisory Committee (SASFAC) Guidelines for Student Activity Fee Creation, Elimination, and Change (2025)
POLICY HISTORY
Policy created: March 4, 2026 (Approved by the Senior Policy Council and President)
Revisions: