Frequently Asked Questions

It combines the KeSCO Explorer (Kenya’s occupational classification structure) and the Career Navigator (assessment-driven career guidance) to support discovery, standardization, and career decision-making.

Learners, job seekers, counsellors, educators, employers, policymakers, researchers, and systems integrating standardized occupational codes.

Some features may work without login, while assessments, saved history, admin dashboards, and certain downloads may require authentication.

KeSCO is a national occupational classification that organizes occupations into a structured hierarchy for consistency in analysis, reporting, and labour market systems.

Yes. The Explorer can support compare flows (e.g., compare unit groups) to review codes, names, and related details side-by-side.

They represent the hierarchy from broad groups (Major) down to specific Unit Groups, enabling structured classification and drill-down navigation.

It processes your responses across multiple steps and maps your profile to relevant unit groups, returning prioritized recommendations and insights.

No. Recommendations are guidance outputs to support decision-making and should be used with counselling and real-world context.

If enabled for your account, you can access a “My Assessments” page to review history and results.

For governance, reporting, and security monitoring. Where a form is used, it helps track usage and prevent abuse.

Depending on configuration, downloads may include the full taxonomy, a selected subtree, or compare exports in structured formats.

API access may require registration/approval. Once approved, your organization is issued a client identifier and an API key for read-only access.

Keys should be rotated immediately. The platform may also suspend access if suspicious activity or abuse is detected.

No. Personal data is used to provide and protect the service, support analytics, and comply with lawful requirements.

Basic security and usage metadata (e.g., timestamps, IP where applicable, device/browser info, and event actions such as search/view/compare), plus API usage logs for integrations.

Use the feedback option (where available) and include the node type, code, and a short explanation of what needs correction.

That usually means the endpoint only accepts POST requests, but the browser is calling it with GET. Ensure your public feedback URL uses a view that supports GET for the form page, and POST for submissions.