Mercy College of Ohio · Office of Institutional Effectiveness
Turnaround: Requests are typically completed within two weeks. For an urgent request, please contact the Director of Institutional Effectiveness directly.
Who's asking, and what you need.
The department or program this is for (or that will benefit from it).
After you pick one, a short set of questions for it opens below.
Summarize this request in 5–7 words.
Why this matters institutionally.
For example: HLC, ACEN, CCNE, ODHE, the U.S. Department of Education, a state board, or a grant requirement.
A quick plan for how this turns into action — the goal, how you'll use it, who's responsible, and the projected timeframe.
In three to five sentences, walk us through what you'll do with what we give you and the goal or purpose behind it. The more context you can give us about the problem you're trying to solve, the better we can shape the request to actually get at it.
Most requests are completed within about two weeks, depending on workload. If it's urgent, see the note at the top.
These specifics are what let us pull the right thing once, instead of guessing. You've already told us the goal up top — here we just need the particulars.
Check any that apply. Ideally you've already talked with these areas before submitting — this just helps us see who's involved and coordinate so the work doesn't overlap with what others are doing.
Please include all three, so we can pull it right the first time:
1. The exact data or metrics — e.g., headcount vs. FTE, duplicated vs. unduplicated.
2. Who or what it covers — a population, program, cohort, or department.
3. Any grouping you need — by program, term, or student-level vs. aggregate.
It also helps to note any of these that apply: enrollment status (full-/part-time), student type (first-time, transfer, continuing), demographics (age, gender, race/ethnicity, Pell, first-generation), or a comparison or trend over time. The more you can give us, the better.
A quick privacy check — pulling data to reach out to people is handled differently than pulling it to report on.
A state report, grant template, accreditation table — whatever the data goes into, so we can enter it exactly where it belongs.
Leave blank if it's ongoing.
If we've pulled something similar, we can reuse it instead of starting over.
Anything that helps us find it — roughly when, who completed it, or what it was called. A best guess is fine.
Anything we should know or watch out for.
Attach anything that helps us understand the request — a prior version, a sample layout, or related context (blank templates only). You can add more than one.
Whether you're starting fresh or changing something you already run, we'll ask only what fits — so a small tweak doesn't get the full design treatment.
New survey — tell us what you're thinking and what you need help with. We'll review and set up a planning meeting with you through Teams.
Check any that apply. Ideally you've already talked with these areas before submitting — this just helps us see who's involved and coordinate so the work doesn't overlap with what others are doing.
Check all that apply.
Who you're surveying — e.g., current students, alumni, employers, faculty, a specific program.
A recurring survey we'll build to be reusable and comparable over time.
Leave blank if it's ongoing.
A new link starts a clean set of responses each round — good for comparing one cycle to the next. Keeping the same link lets responses build into one dataset — good for tracking trends over time.
For our records and to plan it right — the final call is something we'll confirm together. "Not sure yet" is a fine answer.
SurveyMonkey can generate one for posters, handouts, or in-person.
If you've made a start, share what you have — no need to have it figured out. Rough bullets are fine, and "not sure yet" is a perfectly good answer.
Anyone on your team who should join — so we invite the right people in Teams. If it's just you, say so.
Attach anything that helps us plan — a draft, a similar survey, related context. You can add more than one.
After you submit, we'll review what you've shared and reach out through Teams to schedule the planning meeting.
Revision — tell us what's changing. If you need to see the current survey first, we'll send it to you.
Name it, paste a link if you have one, or describe it well enough that we can find it.
If you'd like to re-read it before deciding on edits, we'll send you the current version.
We'll send you the current survey to review. Email your edits to your IR analyst — or ask for a consultation if you'd rather work through them together. Either way, you'll get a preview to approve before it goes live. No need to come back to this form.
Questions added, removed, or reworded; a different audience; new timing — whatever's different this time.
A marked-up version or a Word doc with your changes, if you have one. You can add more than one.
No problem — we'll work through the changes together. A quick note on what's prompting the change (below) helps us prepare.
Context helps us revise it well rather than just mechanically.
Tell us where you are with the changes above, and we'll let you know what to expect.
Not everything fits a neat category. Tell us what you need and we'll figure out the best way to help.
Describe the request in your own words — what you're after, and anything that helps us understand it.
Attach anything relevant. You can add more than one.
We'll review what you've shared and follow up to sort out the best way to help.
No problem — not every request is ready to scope on a form. Give us the gist and we'll set up a short Teams meeting to figure out what you actually need before anyone starts pulling or building.
A rough idea is all we need — vague is completely fine. We'll work out the details together.
Anyone who should join the Teams meeting — so we invite the right people. If it's just you, leave it blank.
We'll review what you've shared and send you a Teams invite for a short consult to talk it through.