Working with Cognosic
Built to plug into the cycle you already run
A Cosmos engagement starts as a scoped pilot, runs on the course documentation your staff have already written, and fits the quality cycle your institution already follows, with no new system to maintain and no disruption to existing tools.
The team replies within one business day.
Fit with institutional processes
Cosmos supports every stage of the review cycle
Universities already run a quality cycle. Cosmos is built to slot into it, not to replace it with a new process.
Self-assessment
Coverage, alignment, and progression analytics on your actual programme structure: the evidence base for self-assessment, available continuously.
Committee and internal review
Committees work from one shared, visual model of the programme instead of competing documents and recollection.
External evaluation
Traceable, documented outputs ready when evaluators ask, not reassembled in the weeks before the visit.
Action and follow-up
Decisions feed back into the living model, so the next cycle starts from the current state, not from scratch.
Not a new system for stretched staff to maintain
Cosmos works from the course descriptions, learning outcomes, and course content your staff have already written. There is no parallel database to feed and no new reporting routine to learn.
- Programme leaders and coordinatorsShare existing course descriptions and learning outcomes. A one-time effort to provide access to information that already exists.
- Individual instructorsNo additional work required. No new tagging, logging, or data entry.
Data governance
Institutional data, handled with institutional rigor
GDPR-aligned
Cognosic is a Norwegian company operating under EU/EEA data-protection law, aligned with GDPR requirements for student and staff data.
Data stays local
Hosted within institutional or EU infrastructure; no student data leaves institutional control without agreement.
No individual tracking
Cosmos analyses programme structure, not individual student behaviour or performance.
Transparent by design
Traceable, defensible outputs, with a documented evidence trail available as a report.
Questions about data handling in your context? Raise them in a demo, and see our privacy policy for how we handle personal data on this site.
The first step
What a first step looks like
A pilot is a flexible arrangement, typically three months to a year, scoped to an agreed set of programmes. No institution-wide rollout, and no long-term commitment required to see whether it's useful. An example pilot, built around first-order programme visualisation and analytics:
Bring in what you have
Existing course documentation and learning outcomes for the agreed scope; nothing new is written for the pilot.
See your programmes in Cosmos
Cognosic builds the first visualisations and generates analytics per the pilot agreement.
Review and decide together
Look at the results with the team and decide together whether to go further, and how.
How an engagement is scopedBeyond the pilot
Low-friction onboarding, no disruption to existing systems
Following a successful pilot, implementation is a straightforward, staged process.
01 · Data handover
Existing course descriptions and programme structure carry over, keeping what faculty already know.
02 · Configuration
Cognosic builds the overview together with a programme coordinator, typically over two to three working sessions.
03 · Review & training
A short walkthrough session for programme leaders and faculty. No certification courses, no train-the-trainer programme.
04 · Ongoing support
A named point of contact at Cognosic for updates, questions, and ongoing support: a person, not a ticket queue.
What institutions ask about working with us
Common questions
Typically three months to a year: a flexible arrangement scoped to an agreed set of programmes, with a joint review at the end.
No. A pilot involves no institution-wide rollout and no long-term commitment; you see whether it's useful on a contained scope first.
A programme coordinator for the data handover and two to three configuration sessions; a short walkthrough for programme leaders and faculty. Individual instructors have no additional work.
Programme structure, not individual student behaviour, is what Cosmos analyses; data is hosted within institutional or EU infrastructure and handled under GDPR. See our privacy policy for details.
A named point of contact at Cognosic for updates, questions, and ongoing support, and the team replies to enquiries within one business day.
Scoped per institution: a pilot and an institution-wide rollout are different engagements. See how an engagement is scoped.
Wondering how it would run at your institution?
Start with a pilot, not a rollout
A contained pilot on your own programmes, running on documentation your staff already have, then a joint decision about what comes next.
Won by the founding team: the National Education Award (2023).