EngageMentorship Early access
The program, out of the spreadsheet. Intakes, applications, pairings, agreements and check-ins: the structure a program needs to survive its coordinator changing.
Four parts of Mentorship. Each with a page of its own.
- ApplicationsPrograms, intakes with caps, a shared question bank and two-sided conditional forms.
- MatchesPairings with a state, logged sessions with attendance, and goals with target dates.
- AgreementsVersioned codes of conduct, signed in the Hub, kept exactly as they were signed.
- Check-insA short report each side files on a rhythm you set, with a grace window and a list of who still owes you one.
Open the intake. Two sides, two forms, one queue.
Each program has its own application page on your Hub, an intake with dates and caps, and separate mentor and mentee forms built from one bank of questions.
- A public application page on your Hub, per program
- Intakes with their own windows, dates and caps
- Mentors and mentees capped separately
- Two forms from one question bank: nothing typed twice
- Approve an application and the roster updates itself
Run the year on records. Not on the coordinator’s memory.
A pairing is a record with a state; each meeting is logged with its attendance; each mentee’s goals carry a status, so handover is reading, not archaeology.
- Pairings with a state: forming, active, paused, finished
- Each meeting logged with its date, length and attendance
- Goals per mentee, with target dates and honest statuses
- A curriculum of readings and tasks, scoped by role
Somebody has to run the program. That is the part that usually falls over.
Pairings, made and recorded
Pair people from the applications you have, and keep the pairing as a thing with a state: forming, active, paused, finished.
Sessions that actually happened
Log each meeting with its date, how long it ran, and whether it happened, was moved, or nobody showed.
Goals, per mentee
What they set out to do and where it got to: not started, under way, achieved, or honestly dropped.
Check-ins that arrive by themselves
Set a rhythm (weekly through to quarterly, or one-off) and the questions go out on it, with a grace period before anything is late.
Give your program a backbone. The beta is open now.
Mentorship is built and in use with early customers. Join the beta and we will turn it on with you; there is no waitlist to join.
By you, from the applications in front of you. Engage can suggest candidates by looking at the tags two people already share on their contact records, but it never pairs anybody itself. The application forms are yours to design, so the criteria you care about are the ones you actually collect, and what the software keeps is the pairing and everything that happens inside it.
Yes. Attach agreements to a program: inline text or a hosted document, different ones for mentors and mentees, and versioned. What somebody accepted is captured as it stood then, with the time, the address they accepted from, and whether they accepted it themselves or somebody on your team recorded it for them.
You set how often check-ins happen, and each one appears for the right person when it is due, with a grace period before it counts as outstanding. The list of who is still outstanding is built for you, so it is never something you have to remember: though the following-up is still yours.