Naming Conventions

Use clear, consistent names for Programs and Grant Cycles in GO Smart. Programs act as the folder for all of your cycles and a solid naming convention helps administrators stay organized and makes it easier for applicants to find the right opportunity.

Last updated on 12 May, 2026

👍 DO	👎 DONT
• Short and succinct • Cycle includes Program name • Same naming scheme every year • Add cycle details (quarter, year, reimbursement) after the program name	• Include agency name • Include ‘grant’ or ‘application’ • Include the date in the program title • Name programs and cycles differently • Put cycles in unrelated programs • Change where and how cycle appendation happens (ie. FY25)

🏷️ Program & Cycle Naming: Best Practices

1. Keep Program names short and clear

Avoid unnecessary words. Names should be easy to scan and understand at a glance.

Example:

✔️ General Operating Support
✖️ Denver Arts General Operating Support Grant

2. Use one program name across all cycles

Your Program name stays the same. Cycles build on it.

Example:

Program: General Operating Support

Cycles:

✔️ General Operating Support 2025
✔️ General Operating Support 2026
✖️ GOS 2025
✖️ Gen Ops 2026

📸 Click here for image alt-text.

An infographic titled "Program" and "Cycles" explaining their relationship. On the left, a Program is represented by a folder icon and defined as the top-level organizational "folder" used to group related funding opportunities, such as "General Operating Support." An arrow points to the right side, Cycles, which is represented by three stacks of papers labeled "General Operating Support" for fiscal years 2025, 2026, and 2027. Cycles are defined as specific, time-bound instances of a grant where individual administrative work occurs.

3. Follow the same format every year

Pick a naming structure for your cycles and stick with it year over year.

Example:

✔️ General Operating Support FY25 → General Operating Support FY26
✖️ Mixing formats like 2025, FY25, or ’25
✖️ Mixing placement like 2025 General Operating Support → General Operating Support FY26

4. Add cycle-specific details after the program name.

If a cycle includes multiple forms, such as reimbursements or quarterly check-ins, use the same program and year, then append a short qualifier to distinguish each form.

Format: Program Name + Year + (optional: qualifier)

Examples:

✔️ Program Support 2026
- This cycle will contain the application and optional intent, interim, or final report forms)
✔️ Program Support 2026 Q1 Check-in
✔️ Program Support 2026 Reimbursement
✖️ Check-in
✖️ Reimbursement (Program Support 2026)

🚫 Naming Practices to Avoid

❌ Program Names

Don’t include your agency name
Don’t use assumed words like “grant” or “application”
Don’t include a year or date (remember this folder should contain each year's cycles)

❌ Cycle Names

Don’t change placement of repeating elements like years (FY26 GOS vs GOS FY26)
Don’t mix year formats (FY25 vs 2025) or placement

🌟 Examples That Work Well

✅ Program Names

General Operating Support
Program Support
Project Support
Fellowship
Project Support Level 1 (Under $500K)

✅ Cycle Names

General Operating Support 2026
Program Support 2026 Q1
Program Support 2026 Reimbursement
Fellowship Spring FY26
Project Support Level 1 (Under $500K) FY26

Did you find this tutorial helpful?

New to GO Smart?