Institution Pilot Pathway

A structured pilot for universities, colleges and institutions.

Tell us the basics. A named DKAM contact will respond personally to agree pilot scope, success measures and a short data handling note before any technical work begins.

What a pilot covers

A DKAM pilot is intentionally bounded. We agree the scope with you up front so you can evaluate value with minimum risk.

  1. 1. Scoping conversation

    30 to 45 minutes. Confirm your context, current systems, decision-makers and what success looks like.

  2. 2. Pilot agreement

    A short, plain-English pilot scope document. Defines cohort, timelines, named contacts and a data handling note.

  3. 3. Controlled enablement

    Stand up your workspace. Verify the named admin. Optional sandbox before any live activity.

  4. 4. Run and observe

    Deliver the agreed pilot scope to a defined cohort. Observe uptake, verification activity, and any operational friction.

  5. 5. Review and decide

    Joint review against the agreed measures. Extend, expand, or close cleanly.

What we ask of you
  • A named sponsor inside your institution.
  • Agreement on the cohort and outcomes in scope for the pilot.
  • A short review of the data handling note with your DPO or equivalent.
Named contacts

Pilot conversations are routed to a named contact at DKAM. You will not be passed between anonymous inboxes. Submissions are answered by a person, usually within five working days.