Mentoring Programme Plan Template for a Paid Engagement

What is this plan designed to do?

This template is for an independent mentor working with one paying client. It is not an employee-matching programme, a training curriculum or a promise to produce a particular commercial result. The plan makes the engagement specific enough to review while leaving room for the client to learn something that changes the direction.

The CIPD's 2025 coaching and mentoring factsheet describes mentoring as a developmental relationship involving experience-sharing as well as questioning and listening. That distinction matters in a paid engagement: say when you will offer advice and who decides whether to act on it. Advice is not the same as delegated execution.

The mentoring programme definition explains the broader concept. Your plan should answer the practical questions a definition cannot: what this client is buying, how their work fits between sessions and what happens if the original goal stops being useful.

A programme plan is an agreement about useful work, not a calendar filled with topics.

What fields should the mentoring programme plan contain?

Complete these fields together and record the version date. Use short, observable descriptions. Where a decision is still open, name who will resolve it and by when rather than leaving an ambiguous blank. The completed plan should be easy to read before a session without reopening the sales conversation.

Keep the coaching agreement alongside the plan. The 2025 ICF Code of Ethics calls for agreement about responsibilities, confidentiality and financial arrangements before coaching begins. This template borrows that contracting discipline without presenting itself as an ICF-approved mentoring contract.

Put fees, payment dates, cancellation terms and other contractual provisions in the appropriate agreement, then reference it here. Do not create a second, conflicting payment promise in the programme plan. Have contractual wording checked for your jurisdiction and service where needed.

Every promise in the plan should have an owner and a boundary.

What does a completed 12-week plan look like?

This is an illustrative plan, not a client case study. A marketing lead wants to run a weekly campaign review without relying on the mentor to interpret every report. The proposed engagement lasts 12 weeks, with 6 sessions of 60 minutes. Those durations are planning choices, not an evidence-based ideal for mentoring.

Purpose: independently lead a review that identifies a decision, explains the evidence and assigns the next test. Starting position: the client currently assembles numbers but cannot consistently explain which action they support. Success evidence: the client leads 2 reviews using the agreed criteria and explains a decision when the mentor challenges the evidence.

Mentor support is limited in this example to session preparation and feedback on one agreed document between sessions, within the response window in the contract. Campaign building, daily reporting and approval of advertising spend are excluded. If the client needs those services, discuss a separate consulting scope instead of quietly absorbing them into mentoring.

A good plan makes independence observable before the final session.

How should the plan connect activity with evidence?

Write a short explanation of why the work is expected to help. In the illustrative plan, repeated practice and feedback should help the client interpret reports and choose tests. That is a working hypothesis. Session attendance and completed documents show participation, but they do not establish independent judgement by themselves.

The UK government's 2026 Test and Learn guidance describes a theory of change as the expected steps from activity to outcomes, including assumptions. You can borrow that planning discipline without importing a government evaluation framework into a small engagement. State the assumptions in ordinary language and review them when evidence disagrees.

For example, this plan assumes the client can access the reports and has permission to run the review. If either assumption fails, more sessions on interpretation will not solve the constraint. Record the access issue and decide whether to pause, use a different example or change the goal.

Agree a coaching baseline before claiming improvement. For a qualitative capability, define what independent performance looks like and preserve an example from the starting point. For a numerical measure, keep the source, denominator and time window. Changes in business results can have several causes beyond the mentoring.

The evidence should test the plan's assumptions, not merely confirm that sessions happened.

What happens when the client needs a different plan?

Use the mid-programme review to ask what has changed, what remains worth doing and what no longer fits. A new role, unavailable data or a revised business priority can make the original programme less useful. Record the decision date and keep the earlier version so the final review does not pretend the goal was unchanged.

• Continue: the purpose remains useful and the next work is feasible.
• Narrow: keep the purpose but reduce the scope to match available time or authority.
• Revise: agree a different outcome and reset the relevant baseline.
• Pause: name the condition for restarting and settle outstanding responsibilities.
• Close: record the useful work completed and what the client will do independently.

Collect only information needed for these decisions. The ICO's data-minimisation guidance, checked in 2026, emphasises relevance and necessity. A plan can record that available time has changed without copying a detailed personal explanation into a sponsor-visible document.

At completion, compare the accepted goal with the evidence and the client's interpretation. Continuing is an option when there is new, useful work, not the default proof that the programme succeeded. A clear independent next step can be a satisfactory ending to a paid engagement.

MentPass can hold the sessions, accepted actions and progress record associated with the plan. The plan itself still needs human agreement; a populated portal does not establish shared expectations. Use the client onboarding checklist for initial setup, then return to this plan at substantive review points.

A revised goal is legitimate when the change is agreed and visible.