Campus Polls & Quick Surveys for Universities

Both configurations are available and set at the poll level. For formal committee votes where an audit trail matters (academic calendar decisions, curriculum approvals, policy ratifications) authenticated voting records who voted and when, producing an exportable tally that can be cited in governance minutes. For advisory or sentiment polls where honest input matters more than attribution, faculty rating a proposed schedule change, students evaluating a housing policy, anonymous voting protects respondents while still producing an accurate aggregate count. The poll creator selects the anonymity setting at creation and it cannot be changed after the first vote is submitted, preventing retroactive unmasking of responses.

The system records the first submission and locks the respondent out of resubmission. If the poll is in authenticated mode, the system links the vote to the user's account and prevents a second submission from the same account. This eliminates the double-voting problem that plagues email-based committee votes, where a member can send a correction that is ambiguous about whether it replaces or supplements their original response. If a committee member made a genuine error, the poll administrator can reset that specific respondent's vote within the voting window. The reset action is logged with a timestamp and administrator identity for the audit trail.

Polls and formal surveys serve different purposes and occupy different cognitive slots for respondents. Formal surveys request 10 to 30 minutes of structured reflection on a semester's worth of experience. Polls ask one to four questions about a specific current proposal and take under 90 seconds to complete. The key discipline is scope: polls work when the question is specific, the decision is near-term, and the response window is short. Institutions that see fatigue with polls are typically running them too frequently on topics that are too general, or leaving polls open for weeks rather than 48 to 96 hours. The platform does not enforce a poll frequency limit, but the analytics dashboard shows response rate trends across polls, a declining response rate on consecutive polls from the same office is a visible signal that poll frequency needs adjustment.

Yes. Every poll exports to CSV and PDF at any point in its lifecycle, while active, after it closes, or from the archive months later. The export includes the question text, all response options, vote counts per option, total respondent count, response rate against the targeted audience size, and (for authenticated polls) a timestamped voter log. For accreditation submissions that require evidence of constituent input in governance decisions, the export shows the poll question, the date it was active, the audience it targeted, the response count, and the result distribution. Archived polls are searchable by date, creator, target group, and title, so retrieving a poll from two semesters ago for a program review document takes under a minute.

Yes. You can create a recurring poll schedule that re-publishes the same question to the same audience group at defined intervals, monthly, quarterly, or at the start of each academic term. Each instance is a distinct poll record with its own response set, so the results do not aggregate across iterations by default. The analytics view places recurring poll instances on a timeline, allowing you to see how the response distribution changed from one period to the next. A dining satisfaction question asked at the start of each semester produces a four-point trend line per academic year without any manual setup after the initial schedule is configured.