How to Title Your Service Request
When submitting a service request, your title should follow a clear and consistent format. A strong title helps our team quickly understand what’s needed and who is affected
Title Format
Product: Institution Name: Headline (Records Impacted)
1. Product
Select the product your request relates to:
- 
VZO 
- 
VZA 
- 
VZE 
- 
IFMIS 
2. Institution Name
Use the short name of your institution, taken from your homepage URL.
- 
Example: www.baylor.edu→ Baylor
- 
Example: www.berkeley.edu→ Berkeley
- 
Example: www.csuchico.edu→ CSUChico
3. Headline
Describe the request briefly using this formula:
Feature/Function + What You Need or What Happened + Who/What is Impacted (e.g., number of records, students, events, etc.)
Examples:
- 
VZO: Baylor: Replace Name Badge PDF Template (All Records) 
- 
VZO: Berkeley: Enable Level Type Filter for Event/Task List Filtering (All Records) 
- 
VZO: CSUChico: Create Student Group Logic First Gen (251 Records) 
4. Records Impacted
The (Records Impacted) section shows how many users/records are affected by your request.
Users may include students, supporters, or administrators —include all groups impacted.
Use clear, simple language:
- 
(All Records)— affects all users or records.
- 
(250 Records)— affects a specific group or total count.
- 
(20% Records)— use a percentage if the exact number isn’t known.
- 
(1 Record)— affects one user or record.
Tip: If your request is part of setup or maintenance, estimate how many users will be impacted once it’s active to help assess its scope and importance.
Why This Format Helps
- 
Clarity – Easy to understand at a glance 
- 
Consistency – Every request looks the same, so nothing gets missed 
- 
Efficiency – Helps the service team route and look into requests faster 
