Product roadmap
What we are building, and when
We go live August 15, 2026. This is the order everything else is released into the running product, derived from a full teardown of the platform this replaces, so the sequence reflects what institutions actually used rather than what was easiest to demo. Every item says what it unlocks, and several say what they deliberately do not include.
Launching August 15, 2026. We go live on August 15, 2026. Institutions sign up, onboard and run their branded instance from that day. Everything below is the order further capabilities are released into the live product, published so you can see what lands when instead of finding out later.
27% 3 of 11 milestones live at launch, the rest released into the running product
- We go live
- August 15, 2026
- Roadmap updated
- July 27, 2026
Build log
Subscribe by RSS to the build logDated entries for every status change, including the ones where a date moves. We publish slips here rather than quietly editing a window above.
-
shipped Public roadmap and build log
The roadmap is live with twelve milestones, and this build log starts today. Every status change from here gets a dated entry, including the ones where a date moves. Subscribe by RSS if you would rather not check.
-
shipped Trust center published
HECVAT 4.1.5 response across all seven domains including AI/ML governance, a VPAT 2.5 accessibility conformance report, and a signature-ready data processing agreement with a FERPA school-official addendum. Free, no NDA, no form, no call.
-
Public trust center and legal documents
Everything a security review normally requires an NDA and a sales call to obtain, published in full and free.
What this unlocks
- HECVAT 4.1.5 response across all seven domains, including the AI/ML governance domain
- VPAT 2.5 accessibility conformance report against WCAG 2.2 AA, Section 508 and EN 301 549
- Data processing agreement with a FERPA school-official addendum, ready to sign
- Privacy policy, terms, accessibility and security statements
What it does not include
- No SOC 2, no ISO 27001, no completed third-party penetration test, no cyber liability insurance. All stated on the trust center rather than omitted.
Why hereBuilt first because it is the cheapest thing that removes the largest obstacle. An institution can rule us in or out today, without waiting for a single feature.
-
Launch: institutions can sign up
We open. Institutions sign up directly, onboard, and stand up their own branded instance without a call or a procurement cycle.
What this unlocks
- Self-signup for any college or university, free, no demo call and no purchase order
- Your institution set up with your logo, colors and your own subdomain
- A place in the first pilot cohort
- Direct input into sequencing while the order is still cheap to change
What it does not include
- Assessment, 360 rater feedback and reporting are released on the dates below. Institutions that sign up at launch get each one as it lands, in the instance they are already running.
Why hereLaunching on onboarding rather than on features means real institutions are configuring real instances while the assessment engine is still being written, and the cheapest time to hear that something is in the wrong order is before it is built.
-
Institution accounts and your branding
The tenancy layer: your institution, your people, your roles, your logo and colors, on your own subdomain.
What this unlocks
- Self-signup for an institution, with roles and permissions for staff
- Your logo, colors and institution name throughout, with live preview
- Your own subdomain, and a custom domain if you want one
- Tenant isolation enforced in the data layer and covered by automated tests
Why hereShips with launch. Multi-tenancy is not a feature you retrofit, and isolation is enforced so an unscoped query fails rather than quietly returning another institution's records, and that has to be true from the first table.
-
The NACE competency instrument
All eight NACE competencies as a versioned instrument, plus your own custom competencies alongside them.
What this unlocks
- The full eight-competency NACE set, not a subset
- Versioned instruments, so changing wording does not silently invalidate last term's data
- Custom competencies for programs with their own outcomes
Why hereVersioning is here rather than bolted on later because the single most common way longitudinal assessment data becomes unusable is an instrument that changed without anyone recording that it changed.
-
Student assessment
Rosters, cohorts, terms and the student-facing assessment with save and resume.
What this unlocks
- CSV roster import, organized into cohorts and academic terms
- The student assessment, saveable and resumable part way through
- One scoring implementation, with tests, used everywhere a score appears
What it does not include
- No mobile app in v1. The interface is responsive and the API stays clean so an app remains possible.
Why hereOne scoring service is a direct lesson from the teardown of the previous platform, which had fourteen scoring implementations that disagreed with each other.
-
360 employer and supervisor feedback
Students invite the people who actually watched them work, and those people respond without creating an account.
What this unlocks
- Single-use, expiring, cryptographically signed rater links, no password and no signup
- Custom rater fields per institution
- Automated reminders, because response rate is the binding constraint on any 360 program
- Self versus observer gap analysis, which is the part students actually act on
- Anonymity thresholds you control
Why hereRequiring an employer to register is the single largest cause of response-rate collapse, and a pile of half-created external accounts is a security liability in its own right.
-
Student dashboards and reports
What the student sees, and the PDF they keep.
What this unlocks
- Student dashboard with competency visualizations
- A report as real HTML first, with the PDF generated from it
- Queued batch generation for a whole cohort
- Private storage, so a report URL is not a public URL
Why hereHTML first, PDF second. The previous platform generated PDFs that silently fabricated content when batch generation failed, which is worse than producing nothing at all.
-
Cohort analytics and accreditation exports
The reporting an assessment office actually has to produce, and the evidence a reviewer actually asks for.
What this unlocks
- Filter by cohort, major, term and your own custom fields
- Exports built for AACSB, ABET and regional review rather than for a dashboard
- Competency to program-learning-outcome mapping, with partial mappings marked as partial
- Response rates, which reviewers do ask about
- Term-over-term comparison on a stable instrument
- Peer benchmarking with minimum group sizes, and an institution-level opt out
What it does not include
- No platform can produce accreditation evidence on its own. This supplies the data and the mapping. The analysis, the curricular response and the narrative are the program's work.
Why hereThe teardown showed accreditation is what schools were really buying, judged by what they configured rather than what they said. This is the payload, not a reporting afterthought.
-
AI development narratives
A written development narrative generated from a student's competency results, with the governance stated up front.
What this unlocks
- Narrative generation from scores, clearly labeled as AI-generated
- Regeneration on request by a student or an administrator
- An institution-level off switch, with the rest of the platform fully functional without it
- Spend caps, so an AI feature cannot quietly become the largest line item
What it does not include
- No model makes or influences any decision about a person. Scoring, aggregation, benchmarking and access control are deterministic code. Our provider agreement prohibits training on submitted content.
Why hereDeliberately late. An AI feature is the easiest thing to demo and the least important thing to get right first, and putting it before the instrument would be building the wrong product impressively.
-
Campus single sign-on
SAML 2.0 and OpenID Connect, configured per institution, optional, and settable to required.
What this unlocks
- SAML 2.0 and OIDC, tested against Shibboleth, InCommon, Microsoft Entra ID and Google Workspace
- Published SP metadata, so your identity team can configure their side first
- Just-in-time provisioning
- A staged rollout, so nobody is locked out during a cutover
Why hereThe build is short. The coordination is not: each campus identity team is measured in weeks, so outreach starts long before this bar does. This is on the critical path more than its size suggests.
-
Independent security review and audit
Independent penetration test, load testing, and the trust documents re-issued against the running system rather than the planned one.
What this unlocks
- Independent penetration test, with the summary letter published
- Full audit logging and retention controls
- The VPAT re-issued to cover the application, not only the website
- The HECVAT response re-issued against the shipped system
- The full feature set complete, still free, still self-signup
Why hereThe current trust documents describe a system being built. They are dated and scoped for exactly that reason, and they get re-issued here against something an auditor can actually poke.
Nothing matches that combination.
This roadmap is a plan, not a contract, and dates move. When one does we change it here rather than quietly leaving the old one up. If something you need is missing or in the wrong order, that is worth telling us while the order is still cheap to change.