What should be on my checklist in the four weeks before a mentoring cohort launches?

Four weeks out, your checklist has six real jobs on it: close and clean the application data, finish screening and confirm every mentor, run the match with time reserved for the pairs that will not behave, prepare orientation and a written pairing agreement, send introductions that ask for a specific first action, and schedule the day thirty check-in before you are too busy to think about it. Everything else is decoration.

The reason coordinators get caught out is almost never the matching. It is a mentor whose background check came back on launch morning, a mentee who typed her advisor's email instead of her own, or a pairing agreement nobody had cleared with the general counsel. Those are all discoverable in week four if you look for them.

What follows is a week by week list built around a cohort of roughly a hundred to two hundred pairs at an association or a university. Scale the hours down if you are smaller. The sequence does not change.

Week four: close applications and clean the data

Close applications on a date you announced, then leave the form open for exactly one more business day and tell nobody. You will get late mentors. Mentors are the scarce side, and one extra day of quiet collection is cheaper than recruiting in week two.

Then clean. Cleaning is not a metaphor here, it is a specific pass through the file looking for the things that break a match later.

• Duplicate applications from the same person, usually because the first submission timed out.
• Institutional email addresses that bounce, especially alumni who applied with an address they lost at graduation.
• Free text fields where you expected a controlled list. If your industry field allowed typing, you now have "fin tech", "FinTech" and "financial technology" as three separate values that will never match each other.
• Blank availability. A mentor who skipped the time zone question is a pair that will fail in month two.
• Mentors who applied as mentees or the reverse. It happens on every intake.

Budget four to six hours for a two hundred person file if your intake fields were open text, closer to ninety minutes if they were dropdowns. That difference is the entire argument for structured intake fields, and it is worth remembering when you build next year's form.

Keep reading: How many hours per pair should I budget when I plan a mentoring program's real cost?

Week three: screening, background checks and mentor confirmations

Screening has two independent clocks and they are the most common cause of a delayed launch.

The background check clock

If your program pairs adults with students under eighteen, or if your institution's policy treats mentoring as a position of trust, you are running criminal background checks through a consumer reporting agency and the Fair Credit Reporting Act applies. That means disclosure on a standalone document, written authorization, and, if anything in the report would cause you to decline the mentor, a pre adverse action notice with a copy of the report and a reasonable window to dispute before you finalize. Some states and cities add their own notice rules on top.

Practically: start checks the day applications close, not the day matching finishes. Most name based checks return in a few business days, but county level searches and anything requiring manual court retrieval can take longer, and fingerprint based checks routed through a state agency are on their own timetable entirely. Ask your vendor for their current turnaround in writing and add a week.

The confirmation clock

Separately, re-confirm every mentor. People apply in September with genuine enthusiasm and change jobs in October. A single email asking for a one click yes, with a Friday deadline, will surface your attrition while you can still do something about it. Expect to lose some share of mentors between application and launch. Whatever that share turns out to be in your program, write it down and recruit against it next cycle.

Week two: run matching and reserve time for exceptions

Run the match early in the week, not late. The match itself is quick. The exceptions are what take the time, and you want the rest of the week for them.

Sort your criteria into three tiers before you start, and write the tiers down so you can defend a pair later:

• Hard constraints. Things that make a pair invalid: same employer where the program forbids it, a direct reporting relationship, a conflict flagged by either party, an unresolved screening.
• Strong preferences. Field or discipline, career stage gap, time zone overlap.
• Nice to have. Shared alma mater, specific skill interests, personality notes.

Then work the leftovers. In any cohort you will have a handful of mentees whose requests are so specific that no mentor satisfies them, and one or two mentors nobody asked for. Those are human decisions. Give yourself two afternoons and a colleague to argue with.

MentorPairing generates the suggested pairings against your criteria so the bulk of the cohort is settled in an afternoon and your remaining time goes to the twelve pairs that need judgment.

Keep reading: What does mentor training look like when your volunteers have twenty minutes and no patience?

Week one: orientation, training materials and the pairing agreement

Finalize three documents this week, and treat the third as the important one.

The orientation deck can be short. The training materials can be a two page PDF. The pairing agreement is what protects the program: it states meeting frequency, the expected length of the commitment, what confidentiality means in your context, that mentors do not provide legal, medical, financial or therapeutic advice, and who to contact if a pair goes wrong. Have someone in your institution's legal or risk office read it once. That review takes days, not hours, which is why it belongs in week one and not launch week.

Also decide now what happens when a pair asks to be reassigned. If you have not written the rule, you will invent it under pressure at the worst moment.

Launch week: introduction emails and first meeting prompts

The introduction email is doing more work than any other message you send. Do not make it an announcement. Make it an assignment.

A version that works:

• Both names, both roles, one sentence each on why the pairing was made.
• A named owner for the first move. Say plainly that the mentee sends the first scheduling message, and give her a deadline.
• A date by which the first meeting should have happened.
• Three questions for that first meeting, attached, not linked.
• Your name and a direct line for problems.

Send mentor and mentee versions separately as well as the joint introduction. The mentor version can carry the boundaries reminder. The mentee version can carry permission to ask for what she actually wants, which is the thing most first meetings lack.

See how MentorPairing handles this for mentoring program administration

Day thirty: the check-in that catches stalled pairs

Thirty days is early enough to rescue a pair and late enough that a first meeting should have happened. Ask two questions, no more: have you met, and is anything not working. Two questions get answered. Ten do not.

Then act on the silence. Non response at day thirty is your signal, not your inconvenience. A pair where neither side replies is very likely a pair with no meeting on the calendar, and a phone call in week five saves a match that a survey in month four only documents as lost. Meeting logs make this visible without asking anyone: if a pair has no logged meeting by day thirty, it goes on the call list.

Documents to finalize before you announce anything

Document	Owner	Finish by
Application form and field list	Coordinator	Before intake opens
Background check disclosure and authorization	HR or risk office	Week four
Matching criteria and tier list	Coordinator	Week three
Pairing agreement	Legal review	Week one
Orientation materials	Coordinator	Week one
Introduction email templates	Coordinator	Week one
Escalation and reassignment policy	Program lead	Week one
Reporting plan for the board	Program lead	Launch week

Where to start

If you only fix one thing this cycle, fix the intake fields, because clean structured data in week four makes weeks three, two and one shorter. If you fix two, add the day thirty rule.

MentorPairing handles the parts of this list that should not need your attention: structured application intake with your matching criteria built in, suggested pairings you can review and override, meeting logs that show you which pairs have actually met, and reporting you can hand to a board without rebuilding a spreadsheet. It leaves you the exceptions, which are the part that needed you anyway.