Technical Self-Intake

Last updated: August 28, 2026

A short set of questions to answer before the build starts. This self-intake is a quick way to ensure you have as many parts determined ahead of time, reducing barriers down the implementation process. The smoothest implementations settle these early — each item below is worth pinning down before it can hold up the build.

People & Ownership

Name an owner and a backup for each — implementations outlive vacations: IT / integration lead, SSO / SAML owner, SIS / data-extract owner, finance / business office, housing / res-life lead, and any downstream vendor contact.

SIS & Integration Path

  • Which SIS? (Banner / Colleague / PeopleSoft / Anthology / Workday / other)
  • Integration path per your contract? (Ethos — Ellucian only / SFTP / Public APIs)
  • In-scope data flows? (profiles, occupancy, transactions, meal plans, applications, keys)

Single Sign-On (SAML)

  • Identity provider? (Azure AD / Okta / Shibboleth / Google / other)
  • Can you share your IdP metadata XML?
  • Unique identifier for sign-in — email or sisId? (applies to everyone)

Data-Format Specifics

  • Can your loader preserve leading zeros (treat IDs/zips/dates as text)? Dates are yyyy-mm-dd.
  • What is your student ID called, and how long is it? (it's the join key across every file)
  • Phone numbers include a country code with a leading +?
  • Your charge codes are your SIS AR / detail codes (not housing-only labels)?
  • What is your term-code format (e.g. 202610)?

If You're Using SFTP

4096-bit RSA public key ready? Do you separate non-production and production keys? (if yes, you'll provide two). Can you allow-list our load-balancer IP 52.55.181.1? Can your loader parse timestamped filenames, or should we set a static filename?

If You're Using Ethos (Banner/Colleague)

  • Sandbox provisioning complete? Test + production API keys issuable?
  • Required endpoints + data access provisioned with the right HTTP methods?
  • Active room-rate tables have no end date (Ellucian bug); AR type available (Colleague)?
  • Banner only: GORICCR override = Y; statuses mapped in SLRMSCD?

Student Photos

Which method: a public URL in the profile file, a templated URL + key, or the REST API? (Are your images on a CDN with a consistent URL pattern?)

Downstream & Network

  • Downstream integrations in scope? (door access, dining, payments, admissions)
  • Any security stack that rewrites links (Safe Links, Proofpoint, Mimecast), or DKIM/DNS steps on your side?
  • Firewall or change-freeze windows we should plan around?

Key Dates

Immovable go-live event · first billing / charge-post date · any registration or selection window · blackout / change-freeze periods.