Partner readiness

Responsible private partnerships for Kenya.

DASKEREL welcomes carefully scoped support that improves learner access, skills, career readiness and trusted employer connections. Every relationship must preserve learner protection, DASKEREL independence and accurate public-service boundaries.

No sponsor or partner receives ownership of DASKEREL, control over academic content, learner-data rights, recruitment authority or the right to imply an NEA affiliation.

Relationship type

Choose the right role before discussing funding or delivery.

Sponsor

Funds a defined learner-impact activity without receiving ownership, platform control, learner data rights or editorial authority.

Delivery partner

Contributes agreed local delivery, learner support, accessibility, employer liaison or operational capability under a written scope.

Academic or curriculum partner

Provides qualified local review of learning relevance and authorised references; it does not create an unsupported approval claim.

Employer partner

Shares verified opportunity requirements or feedback while retaining every recruitment and hiring decision.

Controlled agreement pathway

A partnership should be clear before it is visible to learners.

1

Confirm fit

Record the proposed purpose, location, role, expected learner benefit and named accountable contact.

2

Complete due diligence

Check identity, reputation, conflicts, safeguarding capability, data needs and authority to contract.

3

Agree the contract structure

Use a framework partnership agreement, a pilot statement of work, and a data schedule only where it is actually needed.

4

Deliver within boundaries

Keep learner data, academic standards, recruitment decisions and public-service claims under the appropriate controls.

5

Review before renewal

Assess agreed outcomes, risks, complaints, accessibility and financial delivery before extending or scaling the relationship.

Minimum agreement schedule

What a safe pilot agreement should cover.

  • Purpose, location, learner cohort, duration, deliverables and named owners.
  • Funding, invoices, permitted use of funds, expenses, reporting and unused funds.
  • Continuous learner pathways with planned progress reviews. An initial 90-day review must never be described as an automatic end to learning, certification preparation or employment support.
  • IP, confidentiality, brand use and limits on public statements.
  • Safeguarding, accessibility, complaints, escalation and termination rights.
  • Data roles and a separate data-sharing or processing schedule only if personal data is required.
  • Outcome measures that do not promise jobs, qualifications or public-service access.

Default boundaries

What stays protected.

  • DASKEREL retains ownership of its platform, existing content, brand and delivery methods.
  • Learners remain in control of their profile and evidence; no data is sold or used for unrelated marketing.
  • Academic quality and curriculum localisation remain evidence-led and subject to qualified local review.
  • Employers make their own hiring decisions; DASKEREL does not make automated eligibility, referral or recruitment decisions.
  • Any NEA, KLMIS or county-service link is presented only after the relevant approval and verification.

Kenya co-design boundary

Begin with evidence, not a live data connection.

Until DASKEREL and relevant Kenyan partners agree the scope, data protection, safeguarding, service boundaries and local roles in writing, the Kenya model remains a controlled co-design route. It does not create a live NEA, KLMIS, employer or curriculum-provider integration.