1. LandOffer
  2. Blog
  3. All articles
  4. Create a Mentoring Agreement That Makes the Relationship Useful

Career Growth

Create a Mentoring Agreement That Makes the Relationship Useful

A completed fictional mentoring agreement, month-long work record, and reasoned closure separate learning evidence from meetings, promotion, and guaranteed opportunities.

9 min readLandOffer team

Create a mentoring agreement by naming a realistic learning goal, the work each person will do between meetings, and the boundaries of the relationship. Agree how you will communicate, what confidentiality means within your employer's rules, when you will review progress, and how either person can change or end the arrangement. Use the agreement to guide learning work that both people can support, rather than promise opportunities or advancement.

This LandOffer guide is for an internal mentor and mentee who are already paired. It uses a completed fictional agreement and a month-end decision to close the relationship. We reviewed official program guidance on October 25, 2026. No mentoring session occurred, message was sent, employee record accessed, or career outcome verified for this article.

Two chairs share an agreement folder, learning compass, and clock within a clear relationship boundary.

Start with a learning goal both people can support

Describe what the mentee wants to learn in terms of a task or judgment they can practice. “Make a concise recommendation for a nontechnical decision-maker” is more usable than “become leadership-ready.” The mentor can review a concrete exercise while formal evaluation stays with the responsible manager or employer process.

Ask whether the mentor's experience fits the goal and whether they have time to help. A mentor can be a sounding board without being the right person to teach every technical, financial, or organizational skill. Start with a narrow goal and revisit its fit before expanding the relationship.

UC Davis's mentoring-agreement guidance identifies contact preferences, meeting arrangements, objectives, progress checks, and an ending date. It also emphasizes preparation by both parties. That is an employer's toolkit, not a required form or schedule for every workplace. Use your program's actual requirements alongside the agreement you make together.

Separate the learning goal from outcomes the mentor cannot control. A better draft, a clearer explanation, or a completed practice exercise can be reviewed. Promotion, a transfer, access to influential colleagues, or a favorable performance rating cannot be guaranteed by holding meetings. Discuss any interest in those outcomes honestly without making them the mentor's obligation.

Set boundaries before sensitive topics arise

Agree what can be discussed and what material each person is authorized to see. A mentor in another team does not automatically have access to confidential customer details, personnel information, or internal financial records. Use approved examples or minimized material where needed, and leave restricted information out of the mentoring notes.

Confidentiality needs an explicit conversation. Explain what will stay between the pair, what may be shared only with consent, what minimal participation information the program requires, and which employer obligations may require another route. Do not promise absolute secrecy that overrides applicable policy, reporting duties, or legal obligations. If the limits are unclear, ask the relevant program or HR contact before sharing sensitive detail.

The UK Government Communications mentoring guide discusses confidentiality alongside exceptional disclosure circumstances and agreed communication limits. Its specific Civil Service arrangements are not universal rules for another employer. The useful task is to clarify the boundaries that actually apply to your relationship.

Keep mentoring distinct from management and sponsorship. The mentor may challenge a draft or suggest a resource, but does not become the mentee's project approver, performance reviewer, or representative in a staffing decision. If an introduction might help, ask whether it is appropriate and permitted. Do not assume the relationship grants access to the mentor's network.

Completed agreement: practice a decision brief

All people, dates, work samples, and actions in this example are fictional. Mentee Jun is an engineer who tends to explain implementation details before stating what a planning meeting needs to decide. Mentor Selene has experience presenting technical choices to cross-functional groups. They agree on one month of focused mentoring rather than an open-ended career commitment.

Purpose and term. From February 1 through February 26, Jun will practice writing and explaining a one-page decision brief for a nontechnical internal planning audience. The learning goal is to make the recommendation, alternatives, material trade-offs, and requested decision identifiable. The agreement ends on February 26 unless both explicitly renew it.

Working material. Jun will use an invented internal-tool planning example approved for this mentoring exercise. It compares retaining a manual request queue with exploring a small intake form. It contains no real customer data, employee assessments, vendor quotations, or confidential budget figures. Selene is not asked to validate an actual spending proposal.

Meetings and preparation. They agree to three forty-five-minute sessions on February 1, 15, and 26. Jun sends an agenda and the relevant draft two working days before each session through their approved work channel. Selene limits advance reading to fifteen minutes per session. If a draft arrives late, they can use the meeting for a narrower question or reschedule by agreement; neither person owes an emergency review.

Mentee responsibilities. Jun owns session scheduling, both draft versions, independent practice, and the action record. After each meeting, he records what he will change, why, and what question remains. He may disagree with advice, but will explain his reasoning rather than treat every suggestion as an instruction. He remains responsible for his own work decisions within normal team authority.

Mentor responsibilities. Selene asks clarifying questions, identifies where the decision is difficult to follow, and offers feedback from her experience. She does not rewrite the brief for Jun, certify his readiness for a new level, or secure a presentation slot. Her feedback is learning input, not project approval or an endorsement for a promotion packet.

Communication and time. Between sessions, Jun may send one consolidated clarification question. Selene responds when her workload permits; no same-day response is promised. Urgent delivery questions go to Jun's normal project owner. Jun's manager approves the development time and remains responsible for balancing it with current commitments.

Confidentiality and notes. The pair keep discussion notes within the approved work location and agreed audience. They share an example outside the pair only after checking permission and applicable policy. Program administration receives only the participation information required by the program. If a topic triggers an obligation outside mentoring, they use the appropriate employer process instead of relying on this agreement as a secrecy promise. Notes are handled under the employer's retention requirements.

Review and ending. At the final session, they compare the initial and revised brief, review Jun's explanation, and decide whether the goal still fits. Either may request a change or end earlier with a clear message through the agreed route. Where a formal program requires a closure notice, they follow that process. Neither person must continue merely because the meetings have been pleasant.

This agreement is filled with decisions both people can act on. It also leaves a legitimate boundary: Selene cannot determine whether the proposed form is financially worthwhile. If that becomes Jun's next question, they will identify an appropriate authorized resource rather than expanding Selene's role by default.

Record the work between meetings

A meeting count shows contact, not what the mentee learned. Keep a small record of the agreed action, the work attempted, the mentor's feedback, and any unresolved issue. Do not turn it into a transcript of sensitive conversation or a scorecard of the mentor's availability.

Here is the completed fictional month record:

Point in the month Jun's work and Selene's contribution Evidence of progress and limit
February 1, first session Jun brings a draft dominated by implementation detail; Selene asks what decision the reader must make Initial draft does not state the requested decision until its final paragraph
February 8, independent practice Jun rewrites the opening and practices explaining two alternatives Draft now names the decision first; practice alone does not establish audience comprehension
February 15, second session Selene reads the revised brief and asks Jun to distinguish a recommendation from an approval request They identify a remaining gap: the cost assumptions are unsupported in the invented example
February 26, review session Jun presents a version with recommendation, alternatives, limits, and an explicit request to authorize exploration only Selene can locate those elements in the exercise; real project adoption, savings, and career outcomes remain unmeasured

Jun's revised opening is concrete: “I recommend exploring a small intake form before changing the current manual queue. The decision today is whether to authorize a bounded discovery step, not approve implementation or spending. We need a reliable account of request volume and operating effort before choosing a delivery approach.”

Within this fictional exercise, the revised opening makes the requested exploration decision explicit. It does not prove the form is a good investment or that Jun can now lead every planning discussion. Selene's useful contribution is to make the missing decision and unsupported assumptions visible, while Jun does the rewriting and reasoning.

The pair also note a limitation in their process. Jun initially interpreted a clearer document as a complete business case. The February 15 discussion corrects that assumption. Their record retains the gap instead of presenting the mentoring month as uninterrupted success.

Completed revisit: close the original agreement deliberately

A reviewed learning folder reaches a clear ending marker while a separate unresolved question is directed toward an appropriate next resource.

At the final review, Jun and Selene consider three options: renew the same goal, agree a different goal within Selene's experience, or close the relationship and pursue the remaining question elsewhere. They compare the remaining learning need with the mentor's expertise and available time before choosing.

In this fictional case they close the February agreement. Jun has produced and explained the requested brief structure, which Selene can review. The next substantive gap is learning how to build supported cost assumptions, and Selene does not claim the relevant financial expertise. Continuing identical meetings would not address that gap reliably.

Their completed closure note reads: “We are ending the focused agreement on February 26. Jun practiced stating a recommendation, alternatives, limits, and the requested decision. The final exercise makes those elements identifiable, but its cost assumptions remain unsupported. We are not recording project approval, savings, promotion readiness, or a performance assessment. Jun will ask his manager which approved finance-learning resource fits the remaining question. No introduction or future session is promised.”

They agree that Jun may share the learning objective and closure summary with his manager. The agreed summary does not authorize forwarding the detailed discussion notes. Selene does not contact the manager to assess Jun's performance. If the employer's program requires different administration, the pair confirm that requirement and keep the disclosure within its stated purpose.

The DCPAS mentoring portal describes transition as a point to review goals and learning, and allows closure for positive or negative reasons. That is a specific government program's guidance. It supports treating ending as a normal part of the relationship rather than evidence that the pair failed.

Keep renewal as a fresh agreement

If your pair renews instead, identify the new or remaining goal, the mentor's fit, a realistic time commitment, and the next ending or review point. A useful first period does not imply unlimited availability. If the issue is workload, an unclear objective, or a mismatch of expertise, say which condition needs to change before continuing.

For an early ending, keep the explanation specific and respectful. Name the agreed goal and the practical reason the arrangement no longer fits. Follow any program process for rematching or closure. Avoid converting a scheduling problem into a judgment about the other person's commitment, or a learning gap into a request for unqualified advice.

Use the agreement as a reference when preparing each session and reviewing progress. LandOffer's career guides cover related workplace development tasks; the practical result here is a shared understanding of the learning work, its limits, and the decision to continue, change, or end it.

Sources and Further Reading