UniversiTools Schedulers
Deterministic, 100% conflict-free academic scheduling supported by forecasting, workflows, role-based access, integrations, dashboards, and AI Analytics and Insight.
Explore UniversiTools SchedulersProduct updates
Use this page to identify current capability areas, then confirm version, configuration, deployment, licensing, integration, and implementation details through the appropriate WMT channel.
Current portfolio
These cards describe present capability areas at portfolio level and link to the current product pages.
Deterministic, 100% conflict-free academic scheduling supported by forecasting, workflows, role-based access, integrations, dashboards, and AI Analytics and Insight.
Explore UniversiTools SchedulersHigher-education information management across admissions, records, planning, teaching, finance, campus operations, portals, workflows, analytics, and integration.
Explore UniversiTools SISK-12 school management and student information capabilities spanning administration, academics, engagement, finance, operations, portals, mobile access, and integrations.
Explore SkooleeCorporate learning administration, courses, examinations, assessments, certification, collaboration, analytics, costing, and organizational structures.
Explore BaseCampContract lifecycle management covering records, documents, obligations, alerts, dashboards, reporting, and integration.
Explore PactKeeperUpdate standard
Release communication should help a customer understand relevance, conditions, risk, testing, timing, and action.
What changed, in which product area, and for which users or processes.
Version, licensing, deployment, feature flag, or configuration conditions.
Data, integration, security, browser, infrastructure, workflow, or migration requirements.
Testing, training, communication, deployment, validation, or support steps required.
Confirmation paths
Public pages explain the portfolio. Customer-specific channels confirm applicability and controlled delivery.
Use Product pages and Book a Demo to evaluate current fit against your requirements.
Use the agreed project governance, requirements, issue, change, testing, and checkpoint process.
Use Support for version-specific applicability, prerequisites, release planning, and operational impact.
Questions
No. It provides a public portfolio-level view. Version-specific release notes, deployment instructions, and customer-impact detail should be delivered through the appropriate customer and support channels.
No. Availability can depend on product, licensed scope, version, configuration, deployment model, integrations, data readiness, and implementation status.
Customers should use their established support and project channels to confirm applicability, prerequisites, testing, deployment, training, and timing.
Start with the relevant current product page, then use a demo or sales discussion to test fit against operating requirements and dependencies.
Confirm the right detail
WMT will help identify what is current, what applies, what depends on configuration or implementation, and what should happen next.