Welcome to Agentic Survey Administration thatcoordinates every instrument on one campus calendar.

Survey fatigue is self-inflicted. Five offices ask the same first-years in the same month, and half the questions ask what the record already knows. Risely's agents run one calendar and merge the asks, and the IR director approves every instrument that fields.

The survey calendar · October · first-years

asks arriving

Orientation follow-upHousing pulseLibrary intakeAdvising check-inWellness screensame students, same month

Instrument one · merged from three asks

shared demographics collected once

Instrument two · merged from two asks

fielded after a quota-safe gap

Questions the record already answers · 31 → 0

class year, major, housing status · answered from the record, never asked again

Response, against the close date

opens soon

opensclose date

Every planned ask lands on the calendar first.

Five offices' October instruments become two merged ones. The calendar holds every planned ask on campus, so the collision gets caught in a planning view instead of in a first-year's inbox.

October · planned asks on first-years

collecting

Orientation follow-upHousing pulseLibrary intakeAdvising check-inWellness screen

Instrument one · from three asks

Instrument two · from two asks

The calendar sees the collision before the students do.

Questions the record can answer come out.

Every question the student record already answers gets deleted before the instrument fields. What remains is the part only a student can say, which is the part worth their time and the office's.

The instrument is edited

reviewing

What is your class year?
What is your major?
Do you live on campus?
How is the transition actually going?

The instrument gets shorter, and the data gets better at the same time.

No population gets over-asked.

Each population carries an ask quota for the term, enforced mechanically. A request that would break it gets held to the next window with the reason attached, and response rates recover because the quota holds.

Ask quotas, enforced mechanically

First-yearsasked twice this term · at quota
Seniorsasked once · one ask open

A third ask at first-years · held to next term, with the requester told why

The quota is policy, and response rates recover because it holds.

One collection serves every office that asked.

Each merged instrument's askers get their own slice with the shared demographics attached. Five needs ride one ask, and no student pays for the same answer five times.

One merged collection closes

shared demographics gathered once

·Orientationgets its slice with the shared context
·Housinggets its slice with the shared context
·Librarygets its slice with the shared context
·Advisinggets its slice with the shared context
·Wellnessgets its slice with the shared context

Five needs got served by one ask, and no student paid for it five times.

One ask arrives. The calendar re-runs.

A dean wants a survey in the field next month. The calendar already knows who is being asked, what the record can answer, and what can merge. Every request runs the same way.

  1. A new survey request lands

    a dean wants first-years in November

  2. The calendar checks the load

    that population is already at quota

  3. The overlap merges

    shared questions join an instrument already going out

  4. Record-known questions come out

    answered from the record instead

  5. The IR director approves the field date

    one ask where three were headed

What changes, and how it runs.

Two instruments where five were headed

One calendar sees every planned ask before students do.

Shorter surveys, better data

Nothing asks what the record already knows.

A response rate worth deciding on

34% answered where 11% used to.

The technical read

Connects read-only to your SIS and survey platform to start

The IR director approves every instrument that fields

Every action lands on an append-only log

SOC 2 Type IIFERPAGDPR

Runs alongside what you have. Nothing rips out.