Updated 19 September 2026
Evidence and institutional capabilities
What this page establishes
The public CV builder and template gallery can be explored directly. Institutional tools require an account and configured services. The implementation descriptions below are not independent certification, proof of customer deployment or a guarantee of hiring outcomes.
Open the CV builder · View templates · Explore synthetic report examples
Reach and outcomes
No verified beneficiary count or employment-success rate is published here. Previous marketing figures should not be used as proposal evidence without a dated, deduplicated report and supporting records.
- Registered users: distinct verified accounts, excluding test and duplicate accounts, within a stated period.
- Active users: distinct accounts performing specified events within a stated period, with collection opt-outs disclosed.
- Documents: distinguish saved versions, completed documents and download events.
- Customers: distinguish individual paying users from institutional contracts.
- Outcomes: interviews or employment require consented follow-up, a denominator and verification; tool usage alone is insufficient.
University relationships
No evidence-backed register of formal university partners is currently published. Student attendance at an institution, individual affiliate activity, outreach and proposed programmes are distinct from an executed university agreement. Institutions will be named as formal partners only with supporting authorisation.
Explore an institutional arrangement. A signup or enquiry does not establish endorsement by a university or UNCDF.
Capability boundaries
| Capability | Status | Scope |
|---|---|---|
| Administration dashboard | Implemented; authenticated demonstration required | Student lists, account status and usage screens; public sample data is illustrative. |
| Bulk onboarding | Implemented; rollout validation required | Bulk invitation/import workflows need email-delivery, duplicate and error-handling checks for the target institution. |
| Role-based staff access | Not established as a complete staff role model | Institutional authentication is not evidence of counsellor/department permission levels. |
| Branding and templates | Partially implemented | CV templates and institution settings exist. Approved-template enforcement needs separate confirmation. |
| Student usage analytics | Implemented; metric reconciliation required | Recorded activity reflects collection settings and is not an employment outcome. |
| Document analytics | Implemented; definitions matter | Recorded events and counters are not necessarily distinct completed documents. |
| Skills-gap reports | Not established | AI CV feedback is advisory, not a validated competency assessment or cohort skills-gap report. |
| Interview preparation | Implemented; provider configuration required | Written preparation and text-answer feedback; no voice-analysis capability is promised here. |
| Institutional export | Implemented with limits | Aggregate usage export suppresses small nonzero cohorts. It is not a full student-data handover or anonymity guarantee. |
| Multi-university programme management | Requires agreed scope and validation | A programme-wide role model, reporting scope and isolation acceptance test are not established by a single-campus dashboard. |
| Staff training and support | Support contacts available; training proposed | Training materials and a delivery schedule must be agreed; no completed training history is claimed. |
| Archiving, deletion and handover | Partial controls; operational schedule required | Career export/deletion and privacy-request review exist; provider and backup erasure need operational handling. |
| Institutional pricing | Published annual seat tiers | Minimum 500 seats per institution; programme services require a separate written quotation. |
Institutional review pack
These are planning templates, not signed contracts or completed delivery records.