Run a mentorship programme

What this achieves

A mentorship programme is a named, time-bounded scheme that pairs people who can teach something with people who want to learn it. Humavera holds the pairs, the sessions they hold, and what each side said at the end.

Required role: Administrator to create a programme. An administrator or a manager can propose and manage matches.

Steps

Go to Career & Growth → Mentorship.
Select Create Program.
Enter the Name.

Example: Engineering Mentorship 2026.
Add a Description.
Set the Start date and End date.
Set Max pairs.
Save the programme, then select Activate while it is still a draft.
Open the programme with View Program and select Propose Match.
Choose the Mentor and the Mentee.
Enter the Match reason and the Goals, one per line.
Select Propose.

Programme settings

Option	Description
Name	What the programme is called.
Description	A brief overview of what it is for.
Start date	When it begins.
End date	When it ends.
Max pairs	The cap on how many pairs the programme carries. The programme shows its current count against this.

Max pairs is a capacity decision, not an aspiration. A programme with more pairs than anyone can support produces matches that meet once.

Example: HC Corp UK Ltd caps an engineering programme at eight pairs, because that is how many senior engineers can genuinely give an hour a fortnight.

Finding people to pair

The programme has three tabs.

Option	Description
Matches	The pairs in this programme.
Eligible Mentors	The people who currently qualify as mentors for it.
Eligible Mentees	The people who currently qualify as mentees for it.

Selecting somebody from an eligibility tab carries them into the match proposal. Where a tab is empty, the interface tells you to adjust the programme’s eligibility criteria or wait for more people to qualify.

A match can be marked AI Matched, meaning it was suggested rather than picked by a person. A suggested pairing is a candidate for you to consider — the two people involved are the ones who make it work, so read the suggestion and decide.

Logging a session

Select Log Session on a match.

Option	Description
Date	When the session happened.
Duration (min)	How long it ran.
Topics	What was covered, comma-separated.
Mentor notes	The mentor’s record of the session.
Mentee notes	The mentee’s record of the session.
Action items	What was agreed, one per line.

Each match shows its session count and how long ago the last one was. That pair of numbers is the health of the programme: matches with one session logged three months ago have quietly stopped, and nothing else on the screen will tell you.

Closing a match

Complete captures Mentor feedback and Mentee feedback before closing the match. Cancel ends a match without either, after a confirmation.

Take the feedback seriously as programme data rather than as a formality. Two sides of a finished relationship, gathered while it is fresh, is the only evidence you will get about whether the pairing worked.

What the mentor and mentee see

Each person sees their own match on this screen, labelled with their role in it — Mentor or Mentee — along with its session count. Someone in no match sees that they are not currently in one, and someone with no programmes available is told programmes will appear once an administrator sets them up.

What happens next

An active programme accumulates sessions against each pair, and the session count and last-session date are what you manage the programme by. Completed matches keep their feedback on record, which is what you read before deciding whether to run the programme again and at what size.