Plan composition
Build a term-by-term degree plan from the SUNY Empire course catalog. Transfer credit, planned coursework, and prior learning all compose against the same record.
See how plans composePreparing workspace
Loading IDDT workspace
Individualized Degree Design Tool
The Individualized Degree Design Tool is the workspace where you and your advisor compose the degree that fits your work, your goals, and your life. Plans build against transfer credit and prior learning, validate against program rules, and route through advisor and committee review — with an audit trail at every step.
Made for and with SUNY Empire University. Built and operated by Never Ending Solutions.
What IDDT does
From first draft to registrar handoff — plan composition, advisor review, program validation, and audit trace are all part of the same record. Nothing falls through the cracks.
Build a term-by-term degree plan from the SUNY Empire course catalog. Transfer credit, planned coursework, and prior learning all compose against the same record.
See how plans composeAdvisors review plans inline, leave threaded comments, request revisions, and approve or escalate. The conversation lives in the plan, not in email.
See the review workflowApproved plans hand off to the registrar with a clean Degree Works scribe payload. Banner stays the source of record; IDDT is the workspace on top.
Read the integration FAQBuilt against WCAG 2.2 AA, Section 508, and NYS ITS S-13. Every release runs the same axe-based gate as feature and security work — no exceptions.
Read the accessibility statementTenant theming is token-driven and server-resolved on the first paint — no flash, no client hop. Routing, support, and SSO config live in a single registry.
See institutional commitmentsEvery decision — comment, approval, override — emits an audit event. Reports export the same events end-to-end so registrars can reconstruct any plan.
Read the data-privacy FAQThe program model
At SUNY Empire, an individualized degree means you and your advisor design what fits your work, your goals, and your life. IDDT supports that conversation term by term — and gives every audience the view they need without losing the shared record everyone else relies on.
Student
Pick your program and concentration. Place your courses term by term. See your transfer credit, prior-learning evidence, and remaining requirements update live as you plan — and submit when you and your advisor are ready.
Advisor
Open a submitted plan and see the Banner baseline, the catalog evidence, the validation report, and the student's notes side by side. Leave inline comments. Approve, request a revision, or escalate to committee — all in one workspace.
Administrator
Configure approval workflow and SLA timers. Monitor Banner, Degree Works, and ETHOS integration health. Export the same audit events the registrar uses. Add a new tenant by editing a single registry entry.
Inside the workspace
The student dashboard, plan builder, and advisor queue all read from the same plan. A change in one view is the same change everyone else sees.
Institutional commitments
Operating an institution on IDDT means signing off on these five anchors. Each card links to the surface that proves it.
Conformance verified against axe + manual review every release. Public statement and conformance matrix.
Accessibility statementBuilt against the same federal accessibility standards SUNY ITS expects across its portfolio.
Conformance matrixServer-side access enforcement. Attachments are bound to the requirement they support. No "anyone with the link" mode.
How attachments workNew York State Information Technology Services accessibility policy alignment, verified release-over-release.
Read the auditIn production at SUNY Empire State University. Maintained on a weekly cadence with quarterly major releases and prior-notice change windows.
Release cadenceHelp and access
Sign in to the workspace built for your role, or go straight to the support material written for your audience. The right starting point is one click away.
For students
Sign in to your workspace to continue your active plan, review your Banner baseline, and submit when you are ready.
For advisors
Triage the day from the queue, open a plan with full Banner context, and approve, request revision, or escalate to committee.
For administrators
Configure workflow, monitor integration health, export audit-ready reports, and manage access governance for your tenant.
Common questions
Answers to the questions students, advising staff, and registrars ask most — how plans work, who can see what, and what the platform signs off on every release.
An individualized degree is a SUNY Empire program model where you and your advisor design what fits your career, prior learning, and life context — rather than picking a fixed curriculum. The plan still maps to a recognized program and concentration, but the term-by-term path is yours.
Banner is the source of record for your transcript. IDDT composes a plan against the same record, and on approval emits a clean Degree Works scribe payload so the registrar can audit and post the degree without re-keying anything. Integration health is monitored live by the operations team.
All access is enforced server-side and tied to your signed institutional session — there is no "anyone with the link" mode. Attachments are bound to the requirement they support and only visible to the student, their advisor, and review committee. The platform is FERPA-aware and audited release over release.
Yes. Once you submit a plan version, your advisor sees it in their queue with the Banner baseline, the catalog evidence, and the validation report side by side. Comments and revisions live inside the plan record — not in email — so the conversation stays with the work.
Plan versions are immutable once submitted, but you can create a new version at any time. Existing transfer credit and prior-learning evidence carry forward; the new version validates against the updated program rules and routes through the same advisor review.
IDDT is built and tested against WCAG 2.2 AA, Section 508, and NYS ITS S-13. Every release runs the same axe-based accessibility gate as feature work — accessibility regressions block release the same way security regressions do. The public statement lists known issues and their remediation status.