The DE Program Coordinator Role

Program Coordinators are the faculty, instructors, and/or staff responsible for documenting and submitting annual Distance Education (DE) Program Effectiveness information in HelioCampus.

The “Program Coordinator” designation refers to system access in HelioCampus and may not reflect an individual’s official job title. Multiple individuals may be assigned to a DE program; however, only one person is required to submit the form at each step of the workflow.

Discussion Facilitation Guides

These guides help structure departmental conversations about Distance Education (DE) effectiveness and support clear, thoughtful reporting in HelioCampus.

Chronological Due Dates (CY 2026)

April 24

Submit 26-27 Sources of Data

(Step 1 to Step 2)

October 16

Submit DRAFT 25-26 Findings & Implications

(Step 3 to Step 4)

December 5

Submit FINAL 25-26 Findings & Implications

(Step 5 to Step 6)

Full Cycle Due Dates

 

2025-26 Cycle Due Dates
Workflow Step Role Due Date
(Submit to next step by...)
1. Sources of Data  Program Coordinator Apr 25, 2025
2. Internal Feedback College DE Liaison May 23, 2025
3. Findings & Implications Program Coordinator Oct 16, 2026
4. Internal Feedback College DE Liaison Nov 13, 2026
5. Finalize Report Program Coordinator

Dec 4, 2026

6. OIEE Comments OIEE

Jan 29, 2027

7. Acknowledge Comments Program Coordinator

Feb 5, 2027

 

2026-27 Cycle Due Dates
Workflow Step Role Due Date
(Submit to next step by...)
1. Sources of Data  Program Coordinator Apr 24, 2026
2.College Feedback College DE Liaison May 22, 2026
3. Findings & Use of Results Program Coordinator Oct 15, 2027
4. College Feedback College DE Liaison Nov 12, 2027
5. Finalize Report Program Coordinator Dec 3, 2027
6. Department Approval Department Head/Final Approver Dec 17, 2027
7. OIEE Comments OIEE Jan 28, 2028
8. Acknowledge Comments Program Coordinator Feb 4, 2028
As of the 2026-27 cycle, Department Heads will review final DE reports before submission to OIEE for end-of-cycle comments. This accounts for the difference between the two workflows seen above.