OSU Qualtrics Guide for Surveys Research and Teaching

What this platform is and why you are using it

OSU Qualtrics is the university supported survey platform provided to faculty staff and students at Ohio State. You use it to collect structured information in a way that meets institutional data standards. It replaces ad hoc tools that store data in unknown locations or lack proper controls.

You are likely here because you need to gather responses. That might be for research coursework program review event feedback or internal decision making. The tool exists to solve one core problem. It lets you collect data securely while staying aligned with university policy.

Unlike public survey tools this one is licensed at the institutional level. That gives you features and protections you would not get on a free account. It also means you are expected to use it correctly.

Who should use it and when

This platform is not limited to researchers. Many roles across the university rely on it.

You should use it if you are

• Running academic or social research
• Teaching a course that requires student surveys
• Collecting feedback for a department or program
• Managing internal assessments or evaluations
• Hosting events that require registration or follow up

If your work involves human responses and those responses influence decisions or records this tool fits the job. It is especially important when collecting identifiable or sensitive information.

Access and account setup

Access is tied to your university credentials. You log in using your Ohio State name number. There is no separate account creation process.

Once logged in you are inside a shared but segmented environment. Your projects are private to you unless you share them. You can collaborate with others by granting access at the project level.

You do not need technical knowledge to start. The interface is visual and menu driven. Still you should plan before you build.

Example
If you want to survey students in a class outline the questions first then build the form. This avoids rewrites later.

Designing a survey that works

Good surveys start with intent. You need to know what decision the data will support. That guides question choice and structure.

Key design principles to follow

• Ask one idea per question
• Use clear neutral language
• Limit required questions
• Group related questions together
• Test the survey before sending

The platform offers many question types. Multiple choice text entry matrix and ranking are common. Use advanced logic only when needed. Complexity increases error risk.

Example
If you want to know satisfaction do not ask why in the same question. Ask satisfaction first then follow with an open text prompt.

Logic and flow

Skip logic display logic and branching let you control what each respondent sees. This improves relevance and reduces fatigue.

Use logic when

• Different groups need different questions
• You must hide questions based on prior answers
• You want to shorten the survey for some users

Avoid nested logic unless required. Simple flows are easier to test and explain.

Distribution and response collection

You can distribute surveys in several ways. Email links anonymous links and QR codes are common.

Choose your method based on your goal.

Anonymous links are best for open feedback. Email distribution works when you need to track completion or send reminders.

Be aware that anonymity settings affect what data you can see. Decide this before sending the survey. Changing it later can invalidate results.

Example
For course feedback use anonymous links. For required training confirmation use tracked links.

Data handling and export

Collected data stays within the platform until you export it. You can view responses in real time or download them for analysis.

Export formats include CSV Excel and statistical packages. Choose based on how you plan to work with the data.

Before exporting consider data minimization. Only export what you need. Store files in approved university locations.

This is where OSU Qualtrics matters most. The tool supports compliance but only if you use it with care.

Collaboration and permissions

You can share projects with colleagues. Permissions range from view only to full edit access.

Grant the least access needed. This reduces mistakes and protects data integrity.

When a project ends remove access. Old collaborators do not need ongoing entry.

Example
A teaching assistant may need view access. A co investigator may need edit rights.

Common mistakes to avoid

Many issues come from speed rather than complexity.

Avoid these patterns

• Sending surveys without testing
• Overusing required questions
• Collecting identifiers without need
• Ignoring mobile layout
• Changing settings after launch

Each of these creates risk or reduces response quality.

When to seek help

If you are unsure about data sensitivity or research rules ask before launching. Support teams exist to help with platform use and compliance questions.

Do not rely on past experience with other tools. Institutional rules differ.

FAQ

Is this tool only for research studies

No. It is used for teaching administration feedback and internal assessments across the university.

Can students use it for class projects

Yes when access is provided through their university role and the project meets course guidelines.

What happens to surveys after I leave the university

Account access ends. Data retention follows university policy. Plan exports and handoffs before departure.

Used correctly OSU Qualtrics helps you collect reliable information with less friction. It rewards planning clarity and restraint.