Korus
Five-Week Onboarding

Implementation: built around Test & Validate.

Five weeks from kickoff to go-live, with a structured validation step before any email ever reaches a student or faculty member. Onboarding follows a checklist so your team can work through it as makes sense for your institution.

Our implementation goal

A system that deploys surveys to the right students on the right dates, notifies faculty, and gives administrators visibility into what is happening. We achieve this through structured onboarding with a Test & Validate step before any live deployment. Implementation is led by the Korus team — the same people who build the product.

The onboarding checklist

  1. 1
    Connect CSV & map fields
    Configure SFTP pathway and map core data fields to the Korus schema.
  2. 2
    Configure campuses
    Define campuses with timezones; map to the data source's location field.
  3. 3
    Import historical data & instruments
    Import your historical course-evaluation data and survey instruments.
  4. 4
    Validate org hierarchy
    Review the organizational structure derived from your data; adjust as needed.
  5. 5
    Review default template
    Confirm or modify the default instrument based on the most recent import.
  6. 6
    Configure date rules
    Set up survey open/close date rules by session, term, or any data field.
  7. 7
    Set up email templates
    Configure student and instructor notification templates with piped course data.
  8. 8
    Configure automation rules
    Set up survey lifecycle email automations.
  9. 9
    Test & Validate
    Validate the full configuration against a representative slice of your data before live deployment.
  10. 10
    Go live
    Enable deployment for the first live survey cycle.

What Test & Validate actually does

Date rule validation

Verifies open/close dates calculate correctly across configured rules.

Email content review

Generates previews of outbound emails with real piped data so your team can confirm content before any email reaches a student or faculty member.

Pipeline test

Sends rendered emails to your test addresses to validate end-to-end delivery.

Instrument display preview

Previews the survey as it would appear to a student, including conditionally triggered questions.

Permission validation

Confirms access appointments produce correctly scoped views for each user role.

Five-week timeline

PhaseActivities
Week 1: DiscoveryKickoff, IT coordination, data source assessment, org hierarchy mapping.
Week 2: ConfigurationCSV pathway setup, field mapping, campus/timezone configuration, org hierarchy validation, historical data import.
Week 3: SetupDate rule configuration, email template setup, automation rule configuration, question library review.
Week 4: ValidationTest & Validate execution, configuration refinement, permission testing.
Week 5: Go liveProduction deployment, live monitoring, immediate support availability throughout the first deployment window.
Post-launchFirst-semester check-ins, optimization, Discover/Reports/Sense training.

Role-specific training

Program Administrator

Full platform onboarding — Admin Command Hub, exception management, email automation, monitoring. Recorded session for unlimited asynchronous reference.

Faculty

Dashboard orientation, survey preview, results interpretation. Short recorded overview and optional live Q&A.

Department Chairs & Program Directors

Focused on Korus Discover and Reports — topic analysis, program-level trends, program review documentation.

Center for Teaching and Learning

Advanced Discover and Sense training — institution-wide pattern detection, workshop design from data, intervention tracking.

New features and refreshed training videos are included with ongoing support — no charge.

Ongoing support

  • Dedicated admin-level customer success contact for the duration of the contract
  • Support via email with scheduled video-call consultation, Monday–Friday, 9am–5pm ET
  • Response time: critical issues (survey deployment failure) within 2 hours; standard issues within 1 business day
  • All platform updates, security patches, and new feature releases included (SaaS standard)
  • Proactive outreach at the start of each survey cycle to review configuration and confirm readiness
  • Quarterly product-team meetings for early partner institutions to share operational needs and shape the roadmap

Ready to talk about an implementation timeline for your institution?

Schedule a DemoApply for a Pilot