Administrators
Coordinate the evaluation cycle and keep records current.
- Configure active periods and questionnaires
- Manage faculty, student, and account records
- Monitor completion and export aggregate reports
OLAC Faculty Evaluation System
Learn how the evaluation cycle works, what each role can do, how to resolve common issues, and where to ask for help during testing.
Start here
The Faculty Evaluation System gives each role a focused workspace for managing, completing, and understanding faculty evaluations at Our Lady of Assumption College.
Coordinate the evaluation cycle and keep records current.
See patterns in feedback about your teaching.
Share structured, thoughtful feedback.
Important context
This system is a thesis capstone prototype for demonstration and testing. Do not upload production records or sensitive personal information unless the supervising faculty member has approved it.
Read the full disclaimerStart here
Use these steps to get oriented, regardless of the role on your account.
Navigation cue
The breadcrumb in the top bar shows OLAC and the active period when period information is available.
Before testing
Role guide · Administrator
Administrators are responsible for preparing the data and questionnaire, opening the cycle, monitoring completion, and interpreting aggregate results.
Role guide · Faculty
The faculty portal is designed for reflection: start with the current period, then use history to see how results change across periods.
Your current-period view.
Your period-by-period view.
Read results responsibly.
Role guide · Student
Thoughtful, specific feedback is most useful when every response reflects your experience in the course.
Reference
These terms describe how a student assignment moves through the system and becomes reportable feedback.
| Stage | What it means | Who acts |
|---|---|---|
| Configured | People, questionnaire items, assignments, and a period are prepared. | Administrator |
| Pending | A student has an assignment that has not been submitted. | Student |
| Overdue | A pending assignment has passed the configured timing expectation. | Administrator follows up |
| Submitted | The student completed the response; it is final and available for aggregate reporting. | Student |
| Scored | Enough submitted responses are available for a faculty result or report row. | System / Administrator |
The exact availability of assignments and results depends on the active period, configured data, and the account’s role. A blank state can be a valid state when no cycle is open or no responses have been recorded yet.
Reference
Administrators can use the report filters to narrow the results shown for a period or department, then export a copy for academic review.
Reference
The system uses role-based access and essential account storage to keep the demonstration workflow usable and appropriately separated.
Help
Try the smallest relevant fix first. If the issue remains, record the details in the support checklist below.
Check that you are using the invitation email and current password for the correct role. If needed, use Forgot your password? and look for the reset email. Do not share your password with a support request.
Check your connection, reload once, and confirm that the service is available. If only one area is affected, note the page name and whether other navigation items still work.
Students only see assignments available to their account for the active period. Ask an administrator to confirm the active period, assignment, and student account status.
Review the progress count. Every active question needs a rating before the Review responses button is enabled. Also check that the page has not lost its connection.
Results appear after submitted responses are available for the period. Confirm the faculty account, period, and whether the administrator has received submissions.
Clear the period and department filters, then try again. No rows can be a valid result when no scored evaluations match the selected scope.
Open the navigation with the menu button, rotate or widen the viewport if possible, and use an up-to-date browser. Avoid zoom levels that hide form controls.
Help
Keep this section handy during thesis demonstrations and client testing sessions.
The documentation is public, but the workspaces require an authorized account and role.
No. Submission is final. Students can review before submitting, so they should take time on the review step.
No. Reports remove identity fields and release only thresholded aggregates, but comment wording can still identify a respondent. Use prepared, non-identifying sample comments during thesis testing.
A draft period is not available, an open period accepts submissions, a frozen period stops submissions without releasing results, and a closed period may release thresholded reports. This keeps cycles separate and supports safe incident response.
Archiving blocks sign-in while preserving account history. Permanent deletion removes the account and its related records. Administrators can reset a submitted response with a fixed reason category; the assignment becomes pending again and the action is recorded without copying response content into the audit trail.
The student form uses four choices: Strongly Disagree, Disagree, Agree, and Strongly Agree.
A blank state may mean there is no active period, no assignment, no submitted response, or no report row matching the current filters.
Contact the project team through the faculty adviser or department that provided your demonstration account, and include the details in the support checklist.
Help
There is no fabricated support mailbox in this prototype. Use the project’s approved communication channel so the right person can help with your testing session.
Reach out through the project team, your faculty adviser, or the department that issued the demonstration account. They can confirm whether the issue is related to account setup, test data, or the application.
Return to sign inHelp
A quick translation of the labels you will see in the workspace.